9. GO LIVE - Deployment on PROD

Prerequisites

Contract Signature

This process must be performed only after the customer has accepted the solution and signed the contract.

1. Check Job Schedules and Run Jobs

Review the scheduling of the Calculation Flow CustomerInsights_Sequencer to ensure that:

• It runs immediately after the Transactions Datamart is loaded.

• Its timing and dependencies are consistent with the overall orchestration process.

2. Raise Merge Request

Once the Agents Accelerator testing has been successfully validated by the customer, initiate a Merge Request to merge the pfxagents branch into the branch corresponding to the partition from which the Agents partition was cloned (typically the master branch).

The partner should validate this request, focusing primarily on any changes to the Datamarts or Custom Logics, and then perform the following merges in order:

1. pfxagents → master

2. master → QA
   This merge should include only changes from the pfxagents branch. If it includes other modifications, the partner repository is inconsistent and requires correction.

3. QA → DEV
   This merge should also contain only the changes from pfxagents. If other changes appear, the repository must be reviewed for consistency.

3. Deployment

Before deployment, follow the instructions provided in 7. Enable Auto-Deployment of Component Folders.

• If auto-deployment is enabled, the deployment process will be largely automated.

• If auto-deployment is not enabled, all changes must be deployed manually to the target partition.

4. Run Required Jobs

Execute all scheduled or on-demand jobs that were necessary during the implementation phase to ensure that data and configurations are fully synchronized post-deployment.