We released conditional signature request outcomes when using the Box Sign outcome in Box Relay. When using the 'A Sign Event' trigger in Box Relay, Enterprise Advanced users can configure a number of different outcomes based on whether a signature request is completed, cancelled, expired, or declined. This includes applying metadata templates, classifying signed documents with corresponding Box Shield policies, assigning a task or notification, applying a watermarks signature request documents, and more. However, these outcomes were automatically triggered the moment a signature request is finalized regardless of the final signature request status.
With this new capability, Enterprise Advanced users can configure separate, additional outcomes that are dependent on whether a signature request is completed, cancelled, expired, or declined. For example, if a signature request is completed, a user may want the workflow to move to the next outcome, like automatically applying a Box Shield security policy to the completed signature request file(s) and signing log. However, if the signature request is cancelled or declined, that user may want to end the workflow at that point instead of automatically applying a Box Shield security policy to a cancelled or declined signature request file(s) or signing log.
With conditional signature request outcomes, users get more flexibility on what happens after a signature request ends, enabling them to apply additional outcomes or complete the workflow depending on the status of the signature request.
To learn more about this release, see Understanding Triggers and Outcomes in Box Relay and Generating Documents with Box Doc Gen and Box Relay.