LeanData Reporting Managed Package - CC Inserted Object (CCIO) Follow
Contents:
- Purpose
- Building the Report
- CC Inserted Objects Details
- LeanData CCIO: Hold Until / Time-Based Details
- CC Inserted Objects Error Processing Details
Purpose
The LeanData Continuous Clean Inserted Object (CCIO) custom object is used to track LeanData Continuous Batch Apex processing which is used to process records in batch through LeanData routing flows and tagging.
Note that CCIOs will only be visible in reports while pending or currently processing. After a CCIO has completed processing, the CCIO will no longer be visible within the report.
Note: Real-Time-Routing (RTR) records are processed in your Salesforce triggers rather than in asynchronous batches, therefore CCIOs are NOT created for RTR records. However, if a RTR record hits a Hold Until node, a CCIO will be created for tracking purposes. For more information please review our document Real-Time Routing vs CCIO Batch Processing.
Building the Report
Each Report is built on top of a custom Report Type that is created when the Reports Managed Package is downloaded. The custom Report Types are not editable, however the Reports themselves are. If you would like to build your own reports utilizing different fields, our recommendation is to clone the Report Type and pull the additional fields/objects you would like to reference.
NOTE: If a Report Type is cloned, this report will not be automatically updated when new managed package versions are released. In order to upgrade existing reports that have been edited, you will need to uninstall the Reports Managed package, delete the Managed Package field(s), and reinstall the Reports Managed Package.
To clone the managed package report types for customization, navigate to Setup > Report Types. Click the report type you would like to clone. Within the Report Type Setup page, you will see a "Clone" button to clone the report type.
To create a new custom report type, navigate to Setup > Report Types. Select the New Custom Report Type button. From here, select the primary object of the report, for example, LeanData Logs. After selecting the primary object, you can then customize the layout of the report type, and add additional fields to the layout via Lookup. More guidance on creating report types can be found on the Object Reporting Guide.
CC Inserted Objects Details
Report Name: CC Inserted Objects
Object(s): LeanData__CC_Inserted_Object__c
Description: The LeanData CC Inserted Objects Report
By design, LeanData will only route or tag records that contain relevant updated or inserted data via the configurations provided by the customer. In order to identify these relevant records, these configurations need to be evaluated at trigger time when the records are updated/inserted. Once the records are identified, LeanData captures these changes and required actions into a custom object called CC_Inserted_Object__c (CCIO) which will be picked up and processed later in the Apex Job method.
When the LeanDataContinuousBatch is run, it will pick up 400 records at a time and process 1 CCIO per scope of the execution (This is important for LeanData's Fuzzy Matching algorithm). The LeanDataContinuousBatch will continue processing until there's no more CCIOs in the database.
Report Purpose: This report can be used to monitor the CCIOs that have been queued and are pending processing. It is grouped by object type and the trigger edge which initiates routing. See full description of the default fields below.
Additional information on CCIO processing outlined in our LeanData Scheduled Jobs document.
Fields & Definitions
| Field Name | Description |
| Trigger Edge Label | (Text) The label name of the edge that triggered routing of this record in LeanData. The condition of the edge are set by the customer in the respective object routing flows. |
| Object Type | (Text) The object type that triggered routing in LeanData. |
| CC Inserted Object Name | (Text) The Text(80) |
| Created Date | (Date/Time) Date and time that CCIO was created. This indicates the time that the inserted/updated record met the conditions in the trigger nodes. |
| Created By: Full Name | (Lookup (User)) Triggering User, typically the LeanData Integration User |
| Update Status |
(Text) Indicates the action being taken by this CCIO. Common statues include:
|
| # Processing Attempts | (Number) Indicates the number of times LeanData has attempted to process the CCIO |
LeanData CCIO: Hold Until/Time-Based Details
Report Name: LeanData CCIO: Hold Until/Time-Based
Object(s): LeanData__CC_Inserted_Object__c
Description: When the LeanDataContinuousBatch is run, it will pick up 400 records at a time and process 1 CCIO per scope of the execution (This is important for LeanData's Fuzzy Matching algorithm). The LeanDataContinuousBatch will continue processing until there's no more CCIOs in the database.
During the routing path, if a record hits a Hold Until node, that record may “pause” it’s routing until a given point in time. During this hold period, the CCIO will persist, and maintain a “holding” status. Once the trigger conditions in the hold are met, or the time expires, the CCIO then exits the hold to continue it’s routing path. For more information on the Hold Until node functionality, please refer to Hold Until Node & Time to Action Tracker
Report Purpose: This report can be used to monitor the CCIOs that are pending routing in a Hold Until or Time-Based node. Note that any CCIOs in a holding state will not affect the processing of other CCIOs in the LeanDataContinuousCleanBatch.
Additional information on CCIO processing outlined in our LeanData Scheduled Jobs document.
Fields & Definitions
| Field Name | Description |
| Trigger Edge Label | The label name of the edge that triggered routing of this record in LeanData. The condition of the edge are set by the customer in the respective object routing flows. Data Type: Text(255) |
| Object Type | The object type that triggered routing in LeanData. Data Type: Text(255) |
| CC Inserted Object Name | The Text(80) |
| Created Date | Date and time that CCIO was created. This indicates the time that the inserted/updated record met the conditions in the trigger nodes. Data Type: Date/Time |
| Created By: Full Name | Triggering user, typically the LeanData Integration User. Data Type: Lookup (User) |
| Update Status | Indicates the action being taken by this CCIO. Data Type: Text Area(255) Common statues include:
|
| # Processing Attempts | The number of times LeanData has attempted to process the CCIO. Data Type: Number(18,0) |
| Scheduled Processing Time | This time this record is scheduled to exit the hold, if the trigger conditions set within the hold until node are not met before this time. Data Type: Date/Time |
CC Inserted Objects Error Processing Details
Report Name: CC Inserted Objects
Object(s): LeanData__CC_Inserted_Object__c
Description: By design, LeanData will only route or tag records that contain relevant updated or inserted data via the configurations provided by the customer. In order to identify these relevant records, these configurations need to be evaluated at trigger time when the records are updated/inserted. Once the records are identified, LeanData captures these changes and required actions into a custom object called CC_Inserted_Object__c (CCIO) which will be picked up and processed later in the Apex Job method.
When the LeanDataContinuousBatch is run, it will pick up 400 records at a time and process 1 CCIO per scope of the execution (This is important for LeanData's Fuzzy Matching algorithm). The LeanDataContinuousBatch will continue processing until there's no more CCIOs in the database.
If a CCIO hits an error in Apex, which prevents the record from being processed, the Processing Attempts field will be incremented by 1. If three attempts have been made, and all ended in error, LeanData will cease attempting to process this record. A LeanData or Salesforce administrator will need to address the error in Apex, and then navigate to the Audit Logs page in the LeanData tab to manually select the “Retry Processing” button at the top of the page.
Report Purpose: This report can be used to monitor the CCIOs that have hit an error in processing. Only CCIOs with 1 or more processing attempts will show in this report. The reason for the error will not be captured on the CCIO record itself, a Salesforce admin will need to navigate to the Apex Jobs page in Salesforce Setup to see the error in the LeanDataContinuousCleanBatch.
Additional information on common errors, please refer to the LeanData Admin FAQ page
Fields & Definitions
| Field Name | Description |
| Trigger Edge Label | The label name of the edge that triggered routing of this record in LeanData. The condition of the edge are set by the customer in the respective object routing flows. Data Type: Text(255) |
| Object Type | The object type that triggered routing in LeanData. Data Type: Text(255) |
| CC Inserted Object Name | The Text(80) |
| Created Date | Date and time that CCIO was created. This indicates the time that the inserted/updated record met the conditions in the trigger nodes. Data Type: Date/Time |
| Created By: Full Name | Triggering user, typically the LeanData Integration User. Data Type: Lookup (User) |
| Update Status | Indicates the action being taken by this CCIO. Data Type: Text Area(255) Common statues include:
|
| # Processing Attempts | The number of times LeanData has attempted to process the CCIO. Date Type: Number(18,0) |