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; } } }

Add Option

Aghosh

Hi ,

We wish to add a new "End revert" option to the work flow decription,please refer the screen shot for the same for better understanding.

when we click on the same we get an appache error;

Please can some one suggest me how we can achive that :

Find more posts tagged with

Comments

Adam Stoller

I don't know that you can do this at the job level.
You can do it at the task level by supplying an optional transition to the task or tasks from which you want to allow this operation - perhaps that would suffice?

Aghosh

We want the follwing to happen when the user clicks on revert link :

1 ) Content Requester must have the ability to request termination of request at any point of the workflow by contacting DCM team
2) When a workflow is terminated the parent and child workflow must end.
3)When a workflow is ended ad hoc, content associated to the workflow must be rolled back to the last published date.

are these things possible using a link in the action list ?

Abhishek

Adam Stoller

We want the follwing to happen when the user clicks on revert link :

1 ) Content Requester must have the ability to request termination of request at any point of the workflow by contacting DCM team
2) When a workflow is terminated the parent and child workflow must end.
3)When a workflow is ended ad hoc, content associated to the workflow must be rolled back to the last published date.

are these things possible using a link in the action list ?

Abhishek

To start off with, I'm not sure how you would initiate a workflow on revert unless you add your own 'revert' custom menu option (and probably need to find a supported way to remove the existing 'revert' action link) - I've never tried to do that customization so I'm not sure if it can be done.

The other possibility would be an iwat trigger on the 'revert' event - but that assumes that there is such an event. Again, I've never tried to do this so I'm not sure if it can be done; even if it can be done, the iwat trigger is post-operative - so it would trigger something after the revert already took place - which might be okay for point requirement '3' which doesn't stipulate that reverting over a modified file puts back the original modified file, only that it puts back the last published version (presumably the latest version of the file which could be done by doing an iwupdate with overwrite enabled - essentially a Get Latest)

So - assuming that you add your own custom 'revert' option to initiate a workflow, or manage to capture a 'revert' event to initiate a workflow, requirement '1' can be achieved by providing a transition in all user-oriented tasks to "cancel revert". Whether this starts the process of canceling the operation programmatically or sends email to someone else to begin the process of canceling the operation is unclear from your specifications.

Requirement '2' indicates that there are nested workflows in play here - something which was not established before and for which there is no clear explanation. However, if you program the workflows correctly you should be able to accomplish that too.

Bottom line - the process may be possible. Have you determined yet whether you can replace the OOTB 'revert' action link (in a supported manner)? Or have you determined yet whether the OOTB 'revert' operation triggers an identifiable event? If you can do either of those, the rest is a question of workflow design. If you cannot do that, the rest is irrelevant as far as programatic processing.