Rollup Full Refresh
Use the Rollup Full Refresh scheduled process to perform full refresh of rollup data.
When to Use
- You must enable the ZCA_ENABLE_ROLLUP_HARD_DELETE_REFRESH profile option before running this scheduled process to refresh hard delete of rollups.
- It is used process rollup calculations.
- You can schedule a Full Refresh for any regular or existing aging rollups that are available in Workspace.
- Verify that the required rollups are published before running this schedule process.
- All the rollup calculations will be impacted.
Privileges Required
Roles
- Sales admin
Privileges
- ZCA_MANAGE_ROLLUPS_PRIV
Before You Start
Review the following before scheduling this scheduled process:
- Recommended Frequency
- Ad-hoc, based on your requirements.
- Once per day.
- Compatibility
- No dependencies.
- We recommend that you run elastic refresh after running this scheduled process. It’s a Update Rollup in Configure Adaptive Search FSM task.
- There are no issues with business processes executing in parallel with this job.
- Multiple instances of this scheduled process can run in parallel.
Parameters
| Parameter | Optional or Mandatory | Description | Parameter Values |
|---|---|---|---|
| Number of Workers | Mandatory | The number of workers. | Any number |
| Commit Size | Mandatory | The size of the commit. | Any number |
| Number of Commits | Mandatory | The number of commits. | Any number |
| Refresh for Deleted Records | Optional | Used to refresh the hard deleted records from the application. | Y or N |
Troubleshooting Information
- Notification of job completion would be using the standard scheduled processes notification system.
- If the scheduled job does not run successfully, the next scheduled instance will process data from both jobs.
- This scheduled process idempotent, and no cleanup activity is required if the job fails.
- You can identify the error or refresh status on the Rollup Setup UI after navigating to the rollup.
- Review the logs to identify the error or failures.