Engagement Roll Forward Analysis
Roll a completed analysis forward into an existing engagement. This will create a new analysis within the target engagement using the source analysis’ data as prior period data for the new analysis.
For analyses using a non-periodic time frame, this will create a new current analysis period, with the existing data being added as prior period data. This new current period can be configured to either be a full period, or an interim period.
Analyses that use the periodic time frame will be rolled forward into a new periodic time frame, and will not have a new period added.
Rolling forward is subject to the following restrictions:
- The target engagement must not be the same as the analysis’ current engagement.
- Only completed analyses can be rolled forward.
- Interim analyses cannot be rolled forward. This does not apply to interim analyses that have been converted to full-period analyses.
- The library of the target engagement must support the analysis type of the analysis.
Permissions
api.analyses.write
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Response
Accepted
The unique object identifier.
Indicates the data integrity version to ensure data consistency.
The date that the object was originally created.
The date that the object was last updated or modified.
Details about the user who created the object.
Details about the user who last modified or updated the object.
Indicates the type of job being run.
ANALYSIS_RUN, ANALYSIS_SOURCE_INGESTION, ADMIN_REPORT, DATA_TABLE_EXPORT, ANALYSIS_ROLL_FORWARD, GDPDU_UNPACK_JOB, ACCOUNT_GROUPING_EXPORT, ACCOUNT_MAPPING_EXPORT, DATA_TRANSFORMATION_JOB, CONNECTION_TEST, CONNECTION_TABLES, DATA_TABLE Indicates the current state of the job.
IN_PROGRESS, COMPLETE, ERROR Identifies the entity used in the job.
Identifies the entity type used in the job.
ORGANIZATION, ENGAGEMENT, ANALYSIS, ANALYSIS_RESULT, ANALYSIS_SOURCE, FILE_RESULT, GDPDU_UNPACK_JOB, ACCOUNT_GROUPING, ENGAGEMENT_ACCOUNT_GROUPING, FILE_MANAGER_FILE, CONNECTION_TEST_RESULT, CONNECTION_TABLES_RESULT, DATA_TABLE The reason why the async job failed.

