Data maintenance subscriptions
Job validation rules
Job validation rules can now be applied to selected data maintenance subscriptions to ensure that critical updates occur as expected. Use the rules to check if a job is unintentionally inactivating or deleting a lot of records. This is particularly helpful if you have automated the process for unsubscribing or soft-deleting records.
Validation rules can be applied to the following data maintenance subscriptions:
Delete Locally Managed HCP/HCO
Delete Custom Object Records
Unsubscribe OpenData Records
Tip: Unsubscribe from Third Party Records jobs already support job validation rules because these jobs are run using NEX rules in source subscriptions.
This enhancement is on by default in your Network instance.
Job validation rules
A set of default validation rules are provided for Veeva standard objects (System Interfaces > Job Validation Rules). These rules are on by default.
For data maintenance subscriptions, the applicable default job validation rules are the rules that check for records being deleted. For example, if job validation rules are applied, the HCPIsDeleted rule will fail a Delete Locally Managed HCP/HCO job if the job tries to delete 100 or more HCP records.
Rules can be added for Veeva objects and for custom objects that are enabled in your Network instance.
Apply job validation rules
The supported data maintenance subscriptions contain a new setting called Apply All Enabled Data Validation Rules. Select the setting to apply job validation rules to the job.
If a job validation rule threshold is met, the data maintenance job fails and no changes are made to the data. Open the Job Details page to see an error and the rule name in the Job Error Log.
When job validation rules are applied to data maintenance subscriptions, log files are created. View the log files in the outbound > job_validation_rules directory in File Explorer. A .zip file is created for each job.
Open the .zip file to review the .csv file for the job.
The .zip file and .csv file have the following naming convention: <subscription_name>-<timestamp>-job-<job ID>.
Example job log
In the file, you can review the changes that the job tried to make and the rule that was used to detect the change.