Confirmation Popup When Field Updates Reset or Clear Dependent Fields

Description
In Targetprocess, certain field updates can automatically reset or clear dependent fields in related entities. This happens most often with Configurable Dropdown Lists, which can be dependent on one or more parent fields.

Currently, when a parent field is updated and invalidates a child field’s value, the dependent dropdown is silently reset. Users are not notified, which can result in:

Incomplete or inconsistent records.

Unnoticed loss of important data.

Synchronization errors with integrated systems.

Example Scenario (Configurable Dropdowns)
We use a Configurable Dropdown for Submission Product Type at the Feature level, which is dependent on Project Class, Project Line of Business, and Line of Business at the Epic level. If a user changes one of the parent fields (e.g., Project Class), the Submission Product Type value is silently cleared.

Below is a simplified mashup configuration for this dropdown (Attached to the idea is the mashup Javascript):

tau.mashups .addDependency('tau/api/configurable-controls/controls/v1') .addMashup((controlsApiV1) => { controlsApiV1.addConfiguration('dropdown', { id: 'dd_conf_special_02', name: 'CDD M-M Submission Product Types of the assigned Project Class and assigned Project Line of Business via LOB Parent Hierarchy', label: 'Submission Product Type', supportedEntityTypes: ['Feature'], requiredEntityFields: ['SubmissionProductType'], field: 'submissionProductType', dropdownItemsSource: { type: 'interpolatedQuery', query: "SubmissionProductTypeLobParentHierarchy?where=(LobParentHierarchy.ParentProjectClass.id==${{ProjectClass.id}}$ and LobParentHierarchy.ProjectLineOfBusiness.id==${{ProjectLineOfBusiness.id}}$ and (LobParentHierarchy.LineOfBusiness.id==${{BMMLineOfBusiness.id}}$ or LobParentHierarchy.LineOfBusiness.id==null))&select=({SubmissionProductType.Id,SubmissionProductType.Name})&orderBy=SubmissionProductType.Name asc" } }); });

Proposed Solution
Introduce a confirmation popup whenever a field update will clear or reset dependent values in Configurable Dropdown Lists. The popup should:

Warn the user of the impact before the change is saved (e.g., “Changing Project Class will reset Submission Product Type, since it depends on Project Class”).

Be configurable by administrators, allowing them to target specific dropdown dependencies (e.g., Project Class, BMM Line of Business, or Project Line of Business).

Allow custom warning messages tailored to the specific dependency.

Require user confirmation before the update proceeds.

Business Value

Improves user awareness of silent system resets.

Prevents unnoticed data loss in Configurable Dropdown Lists, one of the most common dependency scenarios.

Reduces risk of incomplete or invalid records.

Enhances data integrity across Targetprocess and integrated systems.

Saves time by preventing errors that require manual correction.