01es
01es
Some of the implemented behaviour may need to be revisited. For example, removing trailing spaces where the intended search target is an entity description, may not be desirable.
@homedirectory Converted to draft pending additional changes to be discussed.
(The argument below was briefly discussed with @elvin-fms. Outlining it here for broader awareness/discussion by the team.) If entities were immutable then such functionality could indeed be very natural and...
@elvin-fms, for reference: During today's discussion, we hypothesised that enforcing a default constraint to prevent the assignment of `BigDecimal` and `Money` values with a higher scale than the property declaration,...
In light of the fact that, albeit less convenient that an intended streamlined password change facility, the "Forgot password" (issue #360) functionality can be used for the purpose of changing...
This issue dropped in priority due to the use of SSO in most cases.
At this stage it would appear that handling recursively defined entities at the model level provides a better alternative.
The core requirements have been implemented. However, before this issue can be considered completed, load testing needs to be performed to identify any potential bottlenecks.
Due to use of SSO as a general rule, the priority of this issue is low.
As SSO (e.g., Microsoft Entra ID) is generally used in TG-based applications, the priority of this issue is set to P5.