Allow Seeded Data to Be Refreshed

Note: This feature is only available in Latest Version Interviews and only for projects using a connector framework web service connection (including Oracle Fusion connections).

Mapped in seed data can be refreshed at specified points during the interview. When a seed data refresh occurs it triggers the same seed data process as happens at the beginning of the interview. That is, it issues a request to the connector to get the data specified by the input mapping and then loads that data into the session. Any seed data loaded via this mechanism overrides data currently held in the session irrespective of whether that data was user set or inferred. This overriding also extends to mapped entities. This means that when seed data is reloaded:

  • any instance that currently exists in the session but not in the seed data will be deleted,
  • any instance that exists in the seed data but not the session will be created in the session, and
  • any instance that exists in both the session and the seed data will be left alone.

If the current screen becomes hidden or no longer exists due to the refreshed data, the interview will return to the first visible screen of the interview.

To allow seed data to be refreshed:

  1. Ensure that the project allows interview data to be re-submitted.
  2. On the Interview tab, click the Refresh Data button.

    The Refresh Data button on the Interview tab in Oracle Policy Modeling
  3. In the drop-down window, there are four options available:

    The Refresh Data drop-down on the Interview tab in Oracle Policy Modeling
    • None - select this option to not have the seed data refreshed on any screen
    • All submit screens - select this option to have the seed data refreshed on entering any screen that has a submit button
    • Chosen screens - select this option to have seed data refreshed on entering the selected screens. Use the check boxes to select which screens.
    • On resuming a checkpoint - select this check box, in combination with any of the options above, to have seed data refreshed when an interview is resumed from a checkpoint. Note that if this option is turned on, the query parameters provided to the action to resume the session must include all those required to seed data into the session in addition to the parameters required to resume the interview.

Tip: A seed data refresh can alternatively be triggered using an interview extension. For more information, see the Interview.saveData() method.

Related Topics