Prevent Stale Meta Data Values from Mapping to AEM from Workfront via Native Connector

Description: When Workfront forms are filled out based on dependency rules and subsequently changed, the entries are retained unless manually cleared by the user before making any modifications. Otherwise, the data is retained and will carry over to AEM via metadata mapping when transferred.

How would you like the feature to work: Workfront should not retain and send stale values to the DAM. Only currently selected/saved project information should map over to AEM.

Current Behavior Example & Why It Matters: In our instance, we use custom fields to denote business group and business category. Our logic shows the user the applicable category field based on their choice of business group. Sometimes users click through the different business group and category options to review which options are available before they make a selection and save it on the project. If the user doesn't fully clear a category option that they clicked on, before switching to a different business group, the category option is stored and sent to AEM. As a result, Workfront sends all of the actual saved project selections for assets sent to the DAM, along with whatever stale values might have been selected and not cleared at project setup. This leads to incorrect categorizations (junk) showing up in the DAM. This will impact the accuracy of reporting and searchability in our brand new AEM DAM. We are clarifying our field options for users, but cannot reasonably enforce that they 'clear values' whenever they select something and then switch to something else.