Make dropdown (configurable-enum) fields usable in Entity title (toStringAttributes)

[sleidig]

Entity Types have configuration how a linked record of this type is displayed. The fields supported for currently have to be of dataType "string". For this, also fields of type "configurable-enum" (i.e. dropdown category fields) should be supported.

e.g. here that the "name" is used when showing a referenced "Child" record:

this is configured in the Admin UI:

User Story / Scenario:

1. Edit Entity Type by navigating to the Children List; opening "Edit Data Structure"
2. In the "General Settings" section of Admin UI, I can see and check "Gender" in the "Generated Title of Record" field (to make the gender part of the displayed title)
3. After saving these changes, I see in the Children list in the "Name" column that in addition to the icon and name there is also the "gender" of that child written out (e.g. "[i] Adikavi Malik male")

---

Implementation steps & considerations:

• the fields used for this representation are stored in the Entity Type's toStringAttributes
• in the Admin UI we only allow the fields with supported dataType to be selected (once new types are supported, the filter there has to be adapted)
• other components (like the EntityBlockComponent) use the Entity class' toString() method (which builds a "title" for that record based on the toStringAttributes array. The logic in this method needs to be adjusted to handle ConfigurableEnumValue values (because those are objects and we need to use their .label property to get the correct string representation for users)
• as usual: Test-Driven-Development --> write unit tests for the Entity.toString method first and then implement logic changes only

[Abhinegi2]

After reviewing the requirements, my proposed approach is as follows -

1. Modify the toString() method in the test EntityClass to support configurableDataType.
2. Add test cases for the updated toString() method.
3. Update initToStringAttributesOptions to include configurableDataType in the options list.
4. Verify the overall functionality

Let me know if this approach looks good or if you have any suggestions

[sleidig]

This sounds good. Please go ahead and raise questions or doubts if any come up during implementation.

[aam-digital-ci]

🎉 This issue has been resolved in version 3.46.3-master.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[aam-digital-ci]

🎉 This issue has been resolved in version 3.47.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀