Asynchronous Workflows

Asynchronous workflows allow all users – even those with limited license capabilities – to participate in the approval, rejection, or delegation of an approval request. This expands the number of users who can advance the approval process without the need for additional full licenses. There are asynchronous workflows for the following processes:

Certify Routing/Routing Version
Certify Production BOM/Production BOM Version

The asynchronous workflows have the same functionality as the base workflows. The names are the same except the asynchronous workflows contain the word "Async" in the name, e.g., Routing Certify Async Approval Workflow. After creating the workflows, assign the approval users, set authentication requirements, and then enable the workflow(s).

The general process of using any of the asynchronous workflows is:

A user with full license rights changes the Status to Certified on a Routing, Routing Version, Production BOM, or Production BOM Version.
- The Status changes to Pending Approval and an approval request is sent to the approval users.
- A Job Queue Entry is created with a Status of On Hold.

Any of the approval users can approve the request but the result is different based on whether the user has a full license or a limited license:

License	Result
Full	The user can approve the request directly from the documents or the Requests to Approve page. The approval is processed and the Status of the Routing, Routing Version, Production BOM, or Production BOM Version is immediately changed to Certified.
Limited	The user can only approve the request from the Requests to Approve page. The approval is processed but the Status of the Routing, Routing Version, Production BOM, or Production BOM Version remains at Pending Approval because the user is not authorized to make changes to the record. However, the Status is set to Approved in the Approval Entries FactBox. The Status of the related Job Queue Entry changes to Ready. Once an authorized user (full license) logs in, the job queue process is triggered and will execute the codeunit. If the approval takes too long, for whatever reason, any authorized user can open the Job Queue Entries page and run the Restart or Run once (foreground) action for the "CCS RA JQ [..]" codeunit created for the approval request. NOTE: The Rerun Delay (sec.)* field in the Regulatory Affairs Setup page determines how long to wait (in seconds) before attempting to rerun the codeunit in case of any failures.* Once successfully executed, the Status of the Routing, Routing Version, Production BOM, or Production BOM Version is changed to Certified.

License

Result

Full

The user can approve the request directly from the documents or the Requests to Approve page.

The approval is processed and the Status of the Routing, Routing Version, Production BOM, or Production BOM Version is immediately changed to Certified.

Limited

The user can only approve the request from the Requests to Approve page.

The approval is processed but the Status of the Routing, Routing Version, Production BOM, or Production BOM Version remains at Pending Approval because the user is not authorized to make changes to the record. However, the Status is set to Approved in the Approval Entries FactBox.

The Status of the related Job Queue Entry changes to Ready.

Once an authorized user (full license) logs in, the job queue process is triggered and will execute the codeunit.

If the approval takes too long, for whatever reason, any authorized user can open the Job Queue Entries page and run the Restart or Run once (foreground) action for the "CCS RA JQ [..]" codeunit created for the approval request. NOTE: The Rerun Delay (sec.) field in the Regulatory Affairs Setup page determines how long to wait (in seconds) before attempting to rerun the codeunit in case of any failures.

Once successfully executed, the Status of the Routing, Routing Version, Production BOM, or Production BOM Version is changed to Certified.

Asynchronous Workflows

See Also