Hi, I have searched in the forum and answers however not been able to find anything that could help me. I am a newbie and your help will be greatly appreciated. I have implemented Nuxeo 5.5 Document Management. Within the DM, the document life cyle has been modified, shortened it to 3 states Project, Approved and Client. Project -> Approved -> Client ^ | | | | | ---------------------- Once the document has reached a certain maturity, it is sent off for an approval where it changes to amajor version. In certain cases, only approved documents are sent off to Client and this change of state is activated by running a single task workflow by the user before downloading and mailing the document. If there are changes after the document is approved or sent to Client, the user edits and the document state automatically gets changed to project and the earlier version is preserved in history. The current version carries on with the last assigned version number -> changing version only after an approval lifecyle again. I have 2 needs * When the state is "Client", it does not change back to initial project. This does happen with the "Approved" state though. An approved document automatically changes into project on editing. I want the same to happen with the "Client" document. I have compared the versioning rules and transistions within the plugin that I have deployed and there is no difference between the Approved and Client How can I make this happen? * In some very special cases, documents in certain folders only, when sent to "Client", a form has to be filled up (a checklist and validation custom form) before the state changes. If the form is not filled, the state does not change or the task is rejected. I am aware of automation chains and events in Studio however cannot seem to find how to create a custom form and attach it as a compulsary action within the workflow for certain conditions. Is there a reference for this or a method I can achieve this? Thank you very much in advance for your responses. I have tried searching without any success and any answers or references will help me greatly regards

* For the first question if I well understand, you would like to automatically change the state of your document from Client to Project each time the document is modified, right? Your lifecycle is good, now you have to create the treatment that will be triggered when the document is modified and when state is Client. In Studio this easy: * Create an event handler attached to the Before document modification for document in the Client state lifecycle * Attach the Event Handler to this following operation chain: fetch context > Follow Lifecycle Transition (with the name you gave for the transition That's all * The second point will need a bit more work and I'm not sure to understand what you want to do.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fill up a form when the document state is to be changed within a workflow

Ramprasad_

Hi,

I have searched in the forum and answers however not been able to find anything that could help me. I am a newbie and your help will be greatly appreciated.

I have implemented Nuxeo 5.5 Document Management. Within the DM, the document life cyle has been modified, shortened it to 3 states Project, Approved and Client.

Project -> Approved -> Client

   ^          |          |

   |          |          |

   ----------------------

Once the document has reached a certain maturity, it is sent off for an approval where it changes to amajor version. In certain cases, only approved documents are sent off to Client and this change of state is activated by running a single task workflow by the user before downloading and mailing the document.

If there are changes after the document is approved or sent to Client, the user edits and the document state automatically gets changed to project and the earlier version is preserved in history. The current version carries on with the last assigned version number -> changing version only after an approval lifecyle again.

I have 2 needs

When the state is "Client", it does not change back to initial project. This does happen with the "Approved" state though. An approved document automatically changes into project on editing. I want the same to happen with the "Client" document. I have compared the versioning rules and transistions within the plugin that I have deployed and there is no difference between the Approved and Client

How can I make this happen?

In some very special cases, documents in certain folders only, when sent to "Client", a form has to be filled up (a checklist and validation custom form) before the state changes. If the form is not filled, the state does not change or the task is rejected.

I am aware of automation chains and events in Studio however cannot seem to find how to create a custom form and attach it as a compulsary action within the workflow for certain conditions.

Is there a reference for this or a method I can achieve this?

Thank you very much in advance for your responses. I have tried searching without any success and any answers or references will help me greatly

regards

Find more posts tagged with

Accepted answers

Benjamin_Jalon1

For the first question if I well understand, you would like to automatically change the state of your document from Client to Project each time the document is modified, right?

Your lifecycle is good, now you have to create the treatment that will be triggered when the document is modified and when state is Client. In Studio this easy:

Create an event handler attached to the Before document modification for document in the Client state lifecycle
Attach the Event Handler to this following operation chain: fetch context > Follow Lifecycle Transition (with the name you gave for the transition

That's all

The second point will need a bit more work and I'm not sure to understand what you want to do.

All comments

Ramprasad_

anyone? Any reference would be really appreciated. thanks

Benjamin_Jalon1

For the first question if I well understand, you would like to automatically change the state of your document from Client to Project each time the document is modified, right?

Your lifecycle is good, now you have to create the treatment that will be triggered when the document is modified and when state is Client. In Studio this easy:

Create an event handler attached to the Before document modification for document in the Client state lifecycle
Attach the Event Handler to this following operation chain: fetch context > Follow Lifecycle Transition (with the name you gave for the transition

That's all

The second point will need a bit more work and I'm not sure to understand what you want to do.

Benjamin_Jalon1

For the second question Nuxeo Studio will implement a tab designer that will give you the possibility to create tabs against you document.

Ramprasad_

Hi Bjalon,

Ramprasad_

hey thanks. You answered as I was adding more explanation. Thanks a ton. I will try to work with what you have suggested. If any issues I will put a new question as suggested but perhaps with a secondary issue and more directed within the explanation you have given.