Develop a Connection to Save, Store and Retrieve Checkpoint Data

The first step in implementing interview checkpoints is to develop a web service connector that can receive, store and retrieve checkpoint data. The Intelligent Advisor connector framework has two web service connector actions for checkpoints:

• SetCheckpoint - called whenever an interview passes a checkpoint screen. Checkpoint screens are defined in the project in Policy Modeling. For more information, see Select the Screens That Will Create Checkpoints.
• GetCheckpoint - called whenever an interview is resumed. It must return a valid interview session state data blob. Note that generated forms are not attached to checkpoints. For more information, see Resume Saved Interview Checkpoints.

Both are passed the URL parameters from the interview start and resume URL. For more information, see Launch an Interview From a URL.

SetCheckpoint is passed the current interview session state as a blob of data.

The developer of SetCheckpoint must overwrite or create new checkpoints as required. For example:

• Keep one checkpoint per interview session, or
• Keep one checkpoint only per policy model, per user. The user can be identified by OAuth, or using URL parameters.

The developer of SetCheckpoint must also decide:

• Where to store checkpoint data
• How to identify checkpoints