[NAE-1970] Verification of Visual ID Generation to Prevent Duplicate IDs

[machacjozef]

Description

Fixes NAE-1970

Dependencies

Third party dependencies

No new dependencies were introduced

Blocking Pull requests

There are no dependencies on other PR

How Has Been This Tested?

• Test Duplication IDs testGenerateVisualIds()

Test Configuration

Name	Tested on
OS	macOS Ventura 14.5
Runtime	Java 11
Dependency Manager	Maven 3.8.4
Framework version	Spring Boot 2.7.8
Run parameters
Other configuration

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes have been checked, personally or remotely, with @tuplle
• I have commented my code, particularly in hard-to-understand areas
• I have resolved all conflicts with the target branch of the PR
• I have updated and synced my code with the target branch
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes:
  • Lint test
  • Unit tests
  • Integration tests
• I have checked my contribution with code analysis tools:
  • SonarCloud
  • Snyk
• I have made corresponding changes to the documentation:
  • Developer documentation
  • User Guides
  • Migration Guides

[minop]

I believed the point of a visual ID is to be short and contain no meaningful information about the individual cases. The new visual IDs are long (22 characters with 3 character process initials) and contain the case creation time, as well as, the count of existing cases. With such long IDs is it not better to simply use the case IDs themselves everywhere? These IDs are no longer 'visual' in my opinion. Is the request for non-duplicate visual IDs even meaningful? Visual IDs are ~hashes and implicitly contain duplicates as a tradeoff for bravity.

[tuplle]

I believed the point of a visual ID is to be short and contain no meaningful information about the individual cases. The new visual IDs are long (22 characters with 3 character process initials) and contain the case creation time, as well as, the count of existing cases. With such long IDs is it not better to simply use the case IDs themselves everywhere? These IDs are no longer 'visual' in my opinion. Is the request for non-duplicate visual IDs even meaningful? Visual IDs are ~hashes and implicitly contain duplicates as a tradeoff for bravity.

The purpose of a visual ID has changed based on a target project. We had several requests to format the visual ID as a unique numerical value. The process initial prefix is used for clarity. Visual ID is often used as a secondary ID as an ObjectID can be hard to understand to non-technical people. As for future releases visual ID is going to be deprecated in favour of generating own ID into a process data field.

[machacjozef]

⚠️ The new ID includes the shortID and contains additional information that would also be useful to include in the visualID. ⚠️