Viewing Vault Java SDK Solutions
The Vault Java SDK is a powerful tool which allows developers to extend Vault and deliver custom capabilities. You can manage the Vault Java SDK solutions currently deployed in your vault from Admin > Configuration > Vault Java SDK. These pages are read-only.
Record Triggers execute custom code when a record Event occurs. This page shows various read-only information about the Record Triggers currently deployed to your vault.
Hovering over a Record Trigger will reveal an Actions menu in the Name column to download the trigger source code.
- Name: The name of the Record Trigger. Trigger names never appear in the UI.
- Object: The object this Record Trigger is associated to, for example,
- Events: The Events specifying when this Record Trigger executes. For example,
BEFORE_UPDATEmeans the trigger executes right before the record updates.
- Order: If multiple triggers exist on the same object, this specifies the order this Record Trigger will execute. Order 1 executes first and Order 10 executes last. UNSPECIFIED means this trigger will always execute last.
- Source: The source of this Record Trigger. Custom means this Record Trigger was developed with the Vault Java SDK.
- Status: The status of this Record Trigger, either Active or Inactive. Only Active triggers are currently executing in your vault.
This page shows various read-only information about Vault Actions. To download a Vault Action’s source code, use the Actions menu in the Label column.
- Label: The UI label for this Vault Action.
- Name: The name of the Vault Action.
- Type: The type of Vault Action, for example, Object.
- Object: The object this Vault Action is associated to, for example,
- Usage: Specifies where in Vault this action is available for configuration and execution. UNSPECIFIED means the action is available everywhere actions are supported.
- Source: The source of this Vault Action. Custom means this is a Custom Action developed with the Vault Java SDK.
- Status: The status of this Vault Action, either Active or Inactive. Only Active actions appear for execution in your vault.
User-Defined Classes allow you to put reusable logic in a class. For example, you can implement logic in a single User-Defined Class rather than repeating the same logic across multiple triggers on different objects. Unlike triggers and actions, which execute when a user or the System initiates an operation, User-Defined Classes only execute by calls from other classes.
To download User-Defined Class source code, use the Actions menu in the Name column.
- Name: The name of the User-Defined Class.
- Source: The source of this User-Defined Class. Custom means this User-Defined Class was developed with the Vault Java SDK.
- Status: The status of this User-Defined Class, either Active or Inactive. Only Active actions are available for use.