My Oracle Support Banner

Get Checkpoint Fails When The Current Interview Screen Relates To A Changed Entity Instance (Doc ID 2773209.1)

Last updated on DECEMBER 07, 2022

Applies to:

Oracle Policy Automation - Version 12.2.14 and later
Information in this document applies to any platform.


Checkpoints are implemented as part of save and refresh mechanism.
Get checkpoint fails when the current interview screen relates to a changed entity instance

The issue can be reproduced through the following steps:
1. Set a checkpoint on screen
2. Reload updated data from external systems
3. Get checkpoint to resume the interview with updated information.
4. If the checkpoint is set by the user on a non-global interview screen, and the current screen relates to a specific entity instance which itself either gets removed or updated (i.e. the entity ID changes) as part of the external data refresh.
5. Then web determinations is failing to re-load the interview on the get checkpoint, and a generic web determinations load error is shown - presumably as the screen they are intending to navigate back to no longer exists.

The requirement in this scenario would be that rather than the interview load failing completely, the user is instead returned to a different screen (for example, returning to the first screen in the interview).


This is new feature implementation.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.