Configure Checkpoints for Oracle Fusion

The Interview object in Oracle Fusion stores checkpoint data for interviews where the global object is loaded and updated at the end of the interview. No additional configuration is required. Note that checkpoints are not supported in cases where the Global entity is mapped to an object created at the end of the interview.

To access the saved checkpoint data so that it can be loaded into the Oracle Policy Modeling Debugger for testing purposes, you need to:

1. Deploy a checkpoint enabled interview to a Fusion instance.

2. Launch the interview, ensuring that the interview proceeds past a checkpoint-configured screen.

3. Use the REST API for Sales and Fusion Service in Oracle Fusion Cloud Customer Experience to get the encoded interview draft data. You can use:

   • Get all interviews (https://docs.oracle.com/en/cloud/saas/sales/faaps/op-opportunities-optynumber-child-interviews-get.html), or

   • Get an interview (https://docs.oracle.com/en/cloud/saas/sales/faaps/op-opportunities-optynumber-child-interviews-opportunities_interviews_id-get.html).

4. For each Interview instance returned, check if there is a checkpoint which can be downloaded. To do this, look for the string field "InterviewStatus" with a value of "COMPLETED" or "INPROGRESS".

   • For an "InterviewStatus" of "INPROGRESS", look under "links" for one with "rel"="enclosure" and "name"="InterviewDraft"

   • For an "InterviewStatus" of "COMPLETED", look under "links" for one with "name"="InterviewData"

   If a link exists for the conditions above, there is a checkpoint which can be downloaded.

5. Decode the interview draft to byte array and save to a .cpz file. To do this:

   1. Access the "href" of that link. The response should be a Base64 string which will need to be decoded into byte[].

   2. Save the decoded bytes as a .cpz file (for example, "myCheckpoint.cpz"). Tip: In Windows, use the command: certutil -decode .\interviewdraft.txt debugfile.cpz.

6. Open the Debugger for the policy model and import the .cpz file. For more information, see Load Checkpoints Into a Debug Session.

Note: If your implementation was previously using the custom object (OPACheckpoints_c ) for checkpoint data (prior to 23A), the ORA_ZUP_IA_CONNECTOR_ENABLE_CHECKPOINT_INTERVIEW_OBJECT profile option in Oracle Fusion will be set to "N". When your implementation is ready to move to using the new standard Interview object, your sales administrator can manually switch this profile option to "Y" to enable the feature, and then the migration job (Migrate Intelligent Advisor Checkpoints) can be run. The migration job will move the data as a scheduled process from the custom object OPACheckpoints_c to the INTERVIEW_DATA table. Note that the Interview object shares checkpoints across agents so do not migrate if you do not want this behavior.