The Process Scheduler is a utility within Veeva CRM that can process incremental integration jobs with other Veeva Platforms. The utility engine resides outside of Salesforce.com and does not rely on any Salesforce.com Apex or Scheduled Jobs. It can be used to schedule jobs at an hourly, daily, or weekly interval and it includes detailed logging.
The following Veeva integration job types are supported:
- Vault Integration Processes
- Approved Email - runs the Approved Email content subscription with Vault
- CLM Processes - schedules the CLM content subscription from Vault
- Engage Processes - schedules the Engage for Portals content subscription from Vault
- Network Integration Processes
- Network Subscription Process - schedules the delta data subscription process from Network
- Network DCR Update (Inbound) Process - schedules the DCR update process from Network. This process checks for updates on currently submitted DCRs.
- Network DCR Retry (Outbound) Process - schedules the DCR re-send process to Network. This process re-sends any DCR that has not previously been successfully sent to Network.
To set-up the Process Scheduler:
- Create a new Visualforce Tab named 'Veeva Process Scheduler' that points to the VF page 'Scheduler_Administration_vod."
- Assign the tab to a System Administrator profile.
- Open the Veeva Process Scheduler and define an integration task for the modules that apply to your Org.
- After testing to ensure the Processes are executing properly, navigate to Monitor/Jobs/Apex Jobs and delete the existing Apex Job that is scheduled for the 'VEEVA_MULTICHANNEL_SCHEDULED_TASKS' Apex class.
If the "Every N hour/day/week" value is 0, the next scheduled job does not run.
The StartTime Timezone is listed in the Running User's timezone. The job always runs in this timezone.
Alerting Users after Integration
Email alerts are now sent to integration administrators for Approved Email, Network, and CLM, after a scheduled integration process completes. Each process generates up to two types of emails:
- Production Status Report
- Production Failure
The Production Status Report is sent after every process runs and includes summary statistics for that process. The Production Failure Alert is only sent if issues were encountered during the process run.
No reports/alerts are sent out for Sandbox-type environments.
Emails contain the CRM and Vault User name, ID, CRM and Vault login results, and summary statistics for the process itself.
By default, emails are sent to the Integration User. Additional email recipients are configurable in the section below the Process Scheduler section. Select Edit from the Action column to add or delete recipients.
A section on the Veeva Process Scheduled page, Alerts/Status Report Administration, allows customers to enter custom email addresses for each process listed above.
To add recipient emails to receive alerts, click the Edit link next to the Process Name on the Veeva Process Administration page.
Veeva recommends the following for MC scheduled processes:
- Production orgs schedule hourly. (Approved Email is most important as there is a safety net process. CLM is less critical since it can be published from Vault, but scheduling is also OK)
- Sandboxes schedule ad-hoc when needed. If there is a CLM sandbox with a lot of activity, the process can be scheduled, but do not have all sandboxes run scheduled
- Development boxes always run ad-hoc, and should never be scheduled
Wherever possible, offset schedules by 5-10 minutes to prevent many processes from running concurrently.
The 'Publish to CRM' Vault functionality should be used to trigger sandbox refresh jobs, instead of relying on schedules. This is more convenient for content admins, and pushes content to CRM more rapidly than waiting for a schedule to run.
Configuration is not needed for this feature.