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

'Completing' a workflow in an event script

Philip Forshaw

We have a requirement to complete and archive a workflow if one of a parallel list of user steps chooses reject as the disposition. At present we have to wait on all users to accept/reject before we stop the workflow.

With an event script that runs WapiPkg.SetWFStatus I can change the status based on a disposition, perhaps to WAPI.WORK_STATUS_STOPPED (..COMPLETED is not handled in that script). Does this damage the integrity of the Workflow, or is this a valid thing to do?

Find more posts tagged with

Comments

There are no comments yet