Announcement: (3/5/24) Updated behavior of workflow sessions generated via API

Background:
Previously, there had been an issue in Non-Employee Risk Management with workflow sessions that are initiated from the API. If the workflow session started with a POST request to /api/workflow_sessions, and the initial action of the workflow was a form-type action it was being skipped over.

What was changed?
With this fix, the initial form-type actions of a workflow will no longer be skipped over when launched via API. These include:

• Approval Form
• Fulfillment Form
• Review Form
• Request Form
• Duplication Prevention

Screenshot showing the initial Duplication Prevention action after opening a workflow session launched from API in the NERM interface:

Are there other changes to expected behavior?
Possibly. Prior to this fix, initiating workflow session via API and passing in attributes would automatically submit the form, so the user would not need to click ‘Submit’ on the request form action.

With this change, initiating a workflow session via API and passing in attributes will no longer submit the request form automatically. The workflow session will be in the state of “Waiting for form submission by…“, opening up to a request form with attribute values sent from the API visible. The user will then need to submit the request form in order for the workflow to proceed.

While this update provides the correct behavior for workflow sessions, we recognize that it may be a departure from expectations. If you have any concerns or would like more information, please contact your Customer Success Representative.

When is this change going into effect?

These changes will be rolled out to customer tenants starting on 3/5/24

Will the enablement of this change cause any disruptions or actions that need to be taken by customers?

No. There will be no downtime, re-authentication, or actions required on the part of users or administrators.

Thank you,

Jeff Lakey

Sr. Product Manager

Non-Employee Risk Management