Details mismatch after "Save for Later" in Pega Infinity 25.1.2 Constellation

General
1

Scenario

  • I have an User Lookup component to select a user.
  • On selecting a user, I populate the Details page using a Data Transform by fetching data from the Data Page.
  • The selected user’s ID is stored in .Userid.
  • The details section is bound to Details.*.

Current behavior

  1. Select User A → Details populate correctly.
  2. Select User B → Details update correctly.
  3. Click Save → Details remain correct.
  4. Click Save for Later and reopen the case:
    • The lookup displays the correct selected user (User B).
    • However, the Details section displays the previous user’s details (User A).
      The issue occurs only after reopening a case saved using Save for Later

Has anyone encountered a similar issue in Constellation where a Page property shows stale data after Save for Later, while the lookup property is correct?

Is there any recommended approach to refresh or rebuild Details from .Userid when the assignment is reopened?

Any suggestions would be appreciated. Thanks!

2

This could be related to the fact that read-only fields are not always persisted when an assignment is reopened using Save for Later.
A common approach is to use a Pre-Data Transform to repopulate the Details page from the Data Page using the persisted .Userid value. This ensures the displayed details are always synchronized with the selected user whenever the assignment is reopened.

3

Which Infinity '26 has introduced a feature for. Preserving Read-Only, Hidden, and Background Values During Refresh and Submit

4

Scenario

  • I have an User Lookup component to select a user.
  • On selecting a user, I populate the Details page using a Data Transform by fetching data from the Data Page.
  • The selected user’s ID is stored in .Userid.
  • The details section is bound to Details.*.

Current behavior

  1. Select User A → Details populate correctly.
  2. Select User B → Details update correctly.
  3. Click Save → Details remain correct.
  4. Click Save for Later and reopen the case:
    • The lookup displays the correct selected user (User B).
    • However, the Details section displays the previous user’s details (User A).
      The issue occurs only after reopening a case saved using Save for Later

Has anyone encountered a similar issue in Constellation where a Page property shows stale data after Save for Later, while the lookup property is correct?

Is there any recommended approach to refresh or rebuild Details from .Userid when the assignment is reopened?

Any suggestions would be appreciated. Thanks!

Clearing cached data by using an activity