6 posts tagged with "Entity Data"

This release delivers two targeted enhancements to the Conflict Resolution Task to improve reviewer efficiency and transparency.

First, categories and tabs with no field-level differences between in-flight and verified data can be optionally hidden by default through the Journey Schema, reducing information overload and helping reviewers focus only on what requires a decision. This behaviour applies to journeys triggered after deployment and can be toggled via task properties.

Second, fields whose values are controlled by conditional value rules can be optionally classified and badged as "Calculated" directly on the task and made read only so the user cannot change their value, ensuring greater transparency and trust in the review process. This behaviour applies to fields at the entity level only currently.

For user clarification, the entity data validation error that appears when field validation fails, has been updated to reference the fields label name as it appears in the task, rather than the underlying datakey identifier.

Conflict Resolution was previously updated to retain resolved conflicts for review as a completed task. We've enhanced this to also retain resolved conflicts for Managed Relationships. No configuration or enablement is required. When the Conflict Resolution task is completed with MR conflicts, they will be available for review in the completed task.

The Conflict Resolution task can now be reviewed after the task has been completed. This provides users with a view of the data conflicts that were displayed within the task and the selections/decisions made by the user when resolving those conflicts.

The Change Management process has been uplifted for improved validation and to include changes and conflicts for in scope fields only.

Related Party Entity Data can now be included in the Conflict Resolution task. This provides users with visibility of data changes that are made and published in parallel journeys that conflict with changes made in the current journey, and allows the user to accept the latest data or retain the current journey's data.