Campaign: Keep Interim Data / Display Target shows blank data after upgrade
After an upgrade, some environments may show an issue where the Display target or Keep interim data view does not render the expected data in the workflow data preview when using newer client console builds. This behavior is tied to older customized workflow input forms and is not caused by a server-side defect.
Description description
In affected environments, users can execute a workflow and see targeting results, but the Data section in the target preview is blank or does not display the expected records when using newer client console versions.
This issue was observed only in environments where the xtk:workflow input form had been customized before June 2021 and that customized version did not include the newer xpathTargetDataSource definition introduced later in the out-of-the-box form.
As a result:
- The issue appears in newer client console versions.
- Older client console builds may still appear to work.
- The behavior is limited to environments with an older customized override of xtk:workflow.
- This is a client console / form customization compatibility issue, not a server-side product defect.
Resolution resolution
The resolution is to resolve the input form conflict in xtk:workflow so that the customized form includes the missing out-of-the-box change.
Specifically, in the “Records of the target” section of the xtk:workflow input form, ensure the following attribute is present:
xpathTargetDataSource=“/ignored/transitionExtensions/@targetDataSource”
Recommended approach
- Open the customized xtk:workflow input form.
- Review whether it predates the out-of-the-box changes introduced after June 2021.
- Resolve any form conflicts between the customized version and the newer out-of-the-box version.
- Confirm that the following line exists in the relevant section of the form: xpathTargetDataSource=“/ignored/transitionExtensions/@targetDataSource”
- Save the form changes and retest the workflow target preview in the current client console build.
If the issue started after an upgrade, review input form conflict resolution first.
The presence of custom changes in a form does not automatically bring in newer out-of-the-box changes; these must be merged during conflict resolution.
A temporary workaround may be to use an older client console build, but the proper fix is to update the customized form definition.
Engineering concluded this scenario is working as designed once the form conflict is correctly resolved.