[Unique Fields] : Avoid validation when Unique Field values have not changed

[jcastro-dotcms]

Parent Issue

• Duplicate IDs in a Content Type Despite Unique Field Constraint #29459

Task

When updating a Contentlet with one or more Unique Fields, we're always triggering the recalculation process on their values, even when they've not changed at all. This is not a big deal when using the Elasticsearch Strategy; however, it might not be a great idea when using the Database Strategy.

We need to be able to detect whether those values have changed or not, so we don't kick off the re-generation process when is not required.

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

Acceptance Criteria

The recalculation process must not be kicked off when Unique Fields haven't been updated.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

Unless we log a message, the only way for QA to figure out when the recalculation process was not triggered is to notice that updating a Contentlet with an unchanged Unique Field takes less time compared to the moment it was created.

Sub-Tasks & Estimates

No response