FEATURE: Refresh stale data element references across entire property

[Spencer-Smith]

Changed Packages

• core
• reactor-extension

Description

Added a button (with a new accordion section as it did not fit in any of the existing ones) to the extension configuration page that allows users to scan all rules within a property with action settings referring to data elements outside of itself. When found, attempts repair:

1. If the settings contain a dataElementName and a DE with that name is in the repo, sets the dataElementId to that DE
2. If no DE matching dataElementName is in the repo or no dataElementName exists, it performs a global lookup on the dataElementId (ie, outside of the property) and if one is found, compares that DE's name to DEs within the repo and sets the dataElementId to that DE
3. If no approach finds a reliable match (or multiple matches are found), skips repair. In any case, all results are reported to the user in detail

Related Issue

N/A

Motivation and Context

References to data elements in extension settings do not have those references updated when a property or rule is copied and instead continue pointing to DEs in the original property. These actions will not work as intended when the property is compiled because of the broken references. Currently a workaround exists where if a user opens the action in question, the extension view attempts to find and repair these broken references. However, this requires users to open each action on a copied property and re-save them.

These new changes add functionality at the property-level to scan and repair all actions with the push of a button (as described above).

Screenshots (if appropriate):

Repair panel view

Confirmation dialog

Repair panel view after repair failure

Repair panel view after successful repair

Dialog with report after successful repair

Documentation

TODO: Add doc ticket

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change which does not add functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have added a Changeset file with a consumer-facing description of my changes.
• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4282de7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
reactor-extension-alloy	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR