Clarity is updated from Chronicles nightly through the ETL process, which stands for extract, transform and load. Each night, data is extracted from Chronicles, transformed into relational form and loaded into the Clarity tables, so that when staff arrive the next day the database reflects the previous day ' s activity. This is the first option. Updates every minute in real time would require continuous extraction and would burden the operational system, and that is not the design. A monthly update would be far too infrequent for operational reporting. An hourly schedule configurable by users is not how the extract works, because the process is managed by the Clarity administrator and not by report users. The consequence is that Clarity cannot be used for same-day reporting, and when users need current information they should use Chronicles-based tools. The load frequency of an individual table, shown in the Data Dictionary, indicates how often it is refreshed, and the Clarity Console is used to schedule and monitor the nightly jobs and to investigate failures.
[Reference: Cogito Fundamentals – Epic Data Architecture: Clarity Extract Schedule, ===============, ]
Submit