Success Step and Rejection Step
What is Success Step & Rejection Step?
User may set up success step and rejection step which can be triggered after the completion of approval. In general, the mechanism and the steps that can be used are the same, with only a difference in when the steps will be executed.
Available action types - Webhook, Automation
Should Success step and Rejection step be set?
Success step and Rejection step is an optional step and not required to be set, it will however enable automation for when an approval is approved or rejected.
How to set up?
Navigate to Global Setting of Approval Path - requires Global admin permissions, or
Navigate to Project Settings of Approval Path - requires project admin permissionsSelect ‘Definitions’
Either create a new approval definition or edit an existing one
Ensure an approval step is set before adding any outcome step
Click on the “Add success step” or “Add rejection step” button
How to set success or rejection step by Automation?
After selecting “Add success step” or “Add rejection step”, click ‘Automation’
Action (using Change page status as an example) - Select ‘Change page status’ and put the status name that you want to apply in Change page status blank. You can also find Automation set up details in our Confluence documentation: https://warsaw-dynamics.atlassian.net/wiki/spaces/APFC/pages/436895747
How to set success or rejection step by Webhook?
After selecting “Add success step” or “Add rejection step”, click ‘Webhook’ button.
Webhook step can be configured to respond to any custom call backs. If you wish to add Confluence automation rule, here is documentation for webhook step.
If you have successfully set up the success step and the rejection step, you will see below view in your approval definition. You can define the steps as needed and use webhooks or automation, or both.