Async Submit to Gateway

Learn how to update your vault's configuration to enable the Async Submit to Gateway feature.

Note Beginning with 24R1 in April 2024 and for all subsequent releases, Vault Safety General Release Help content is moving to a new site. Test the new site using Limited Release content.

About the Feature

The Async Submit to Gateway feature is for Vaults that use Auto-Submissions to multiple destinations that are triggered automatically as part of a workflow. When configured, a user can initiate an Async Submit to Gateway action and then continue working in Vault without first having to wait for the action to complete.

Vault Administrators must perform the following configuration changes to enable this feature.

Create a Queued State for the Transmission Lifecycle

On the Admin side, go to Object Lifecycles > Transmission Lifecycle and create a new State with the following properties:

  • Label: Queued for Submission

Associate the New State with Queued State Type for the Transmission Lifecycle

On the Admin side, go to Object Lifecycles > Transmission Lifecycle and create a new State Type with the following properties:

  • State Type: Queued State
  • State: Queued for Submission

Create an Async Submit to Gateway Action

Go to Objects > Case > Actions and create a new Async Submit to Gateway action.

Create a User Action

Go to Object Lifecycles > Case Lifecycle and select the Approved state. Edit the User Actions section and add the Async to Gateway action (use the same name for the Action Label).

alt-text
Async Submit to Gateway User Action

Enable Auto-Submit for Transmission Profile

Finally, on the Business Admin side, go Transmission Profiles and set the Auto-Submit field to Yes for all the Transmission Profiles you want to use the Async Submit to Gateway feature.


Feedback?