Sections in This Article
Prerequisites
You must enable sending Cases to Signal before performing the steps on this page.
Send Individual Cases to Signal
Vault Safety will automatically copy a Case or an Imported Case to Signal once that Case enters a specific lifecycle state or state type. To enable this, perform the following steps:
- Go to Business Admin > Objects > Sources > PV Database.
- In the Source Sponsors, select the Enable Send to Signal checkbox for the respective sponsor.
Note If you are a CRO, you must create a Source Sponsor record for each Sponsor you are enabling the copy for.
- Save the page.
Once you save this change, the API Key field is automatically populated by the system. If the API Key is not populated, Cases cannot be copied.
Enable Send to Signal Checkbox and API Key
Result
Once a Case or Imported Case enters the Closed, Voided, Nullified, or Deleted State Type state, and meets the copying criteria, Vault Safety automatically copies it to Signal. Only Cases for the Sponsor enabled for Signal are copied.
Send Cases in Bulk to Signal
Tip Sending Cases in bulk is useful when you are first setting up Vault Signal and copying Vault Safety Cases to the Signal database.
You can copy Cases or Imported Cases in bulk to Signal. To enable this, perform the following steps:
- Go to Business Admin > Objects > Sources > PV Database.
- In the Source Sponsors, select the Enable Send to Signal checkbox for the respective sponsor.
Note If you are a CRO, you must create a Source Sponsor record for each Sponsor you are enabling the copy for.
- Save the page.
Once you save this change, the API Key field is automatically populated by the system. If the API Key is not populated, Cases cannot be copied. - Select Send to Signal from the All Actions menu next to the Sponsor.
This action only appears if the Enable Send to Signal checkbox is selected and if a valid API Key exists for this Sponsor in the Source Sponsors section.
Result
All Cases in the Closed, Superseded, Voided, Nullified, or Deleted State Type state that meet the copying criteria are copied to Signal. Only cases for the Sponsor enabled for Signal are copied.
Update Previously Sent Cases to Signal
Individual Cases that were previously copied to Signal can be updated with new information. For example, an individual Case enters the Closed state and is automatically copied to Signal. A user then updates this same Case version in Vault Safety and moves it to the Closed state again. Vault Safety automatically updates the Case with these user changes in Signal.
You can trigger the Send to Signal action multiple times to update previously copied Cases with any new information. Triggering this action again also copies any new Cases associated with the Sponsor.
Send Unsuccessful Copies to Signal
If there are Cases that were not copied to Signal after triggering the Send to Signal action, you can use the Send Unsuccessful Copies to Signal action to resend these Cases, after addressing the errors.
You can identify the Cases that were not copied using the Signal Case Sync Log. These Cases will display an “Error” status under the Sync Status column. You can address these errors using the Log Message column.
Note Note that in some occurrences, a Case that is unsuccessfully copied to Signal may not be logged in the Signal Case Sync Log. The system will notify you the Case copy failed with errors and that not all errors were logged. For these Cases, you must trigger the Send to Signal action again instead of the Send Unsuccessful Copies to Signal action.
The Signal Case Sync Log also allows you to monitor the progress and copy status of copied Cases. See Monitor Case Copy for more information.
Monitor Case Copy
You can view the copy status of a Case in the Signal Case Sync Log section of data source.
The following table describes the fields on the Signal Case Sync Log Object:
| Field | Description |
|---|---|
| Sponsor | The referenced Sponsor of the Case being copied to Signal. |
| Sync Status | The current copy status of the case. The status states are:
|
| Log Message | The current status details of the Case copy, including success and error messages. |
| Case | The current Case being copied to Signal. |
| Sync Date | The date and time that the last copy action was initiated. |
| Copy ID | The unique ID of the bulk transfer action. This value is automatically set by the system. |
Deleting and Re-enabling Source Sponsors
Deleting a sponsor (from the All Actions menu beside it) also deletes all Product-Event data related to this sponsor, including records in the Signal Case Sync Log. However, tracked Product-Events and Product Profile records will remain in your Vault.
If you re-create the deleted sponsor, the API key is re-generated and the tracked Product-Events and Signal Product Profiles will be linked to the newly created sponsor.
Additional Resources
See How Vault Safety Copies Cases to Signal to learn more about the considerations for successful Case copying and the Case data that can be copied to Signal.
