The Await Status activity suspends a business process pending the status change of the currently processed app item. This feature is handy when working with documents. For example, you can configure the process to be paused when you sent the contract for signing to a contractor. Once the contractor has signed the contract, its status changes to Signed, and the process continues.
Drag the activity onto the process diagram and double click on it. The settings window opens.
In the Variable field, specify the app item whose status you need to get. Select one or more statuses in the Await Status field.
Now, the system will pause the process. It will continue only when the status of the app changes to the one specified above.
Waiting for statuses from an external system
To use waiting for an app status from an external system, you must map ELMA365 app statuses to the external system’s ones beforehand for Await Status activity to work correctly. In ELMA365, the Diadoc module is available at present that can use the Await status feature.
To configure it, go to Document mapping > Status mapping in the module settings.
- Specify the ELMA365 app statuses that reflect the same document lifecycle stages as the Diadoc statuses .For example, the Diadoc status “Signed” can match “Signed by a contractor” ELMA365 app status.
- In the Await Status field of the activity settings, select “Signed by a contractor” status from the drop-down list.
Now, the business process handling the document-type app pauses upon reaching the described activity until the app status in Diadoc is not changed. When the status changes, the ELMA365 process will continue.
Found a typo? Highlight the text, press ctrl + enter and notify us