Model Relationships to DomainUserManagement

[malcolm-silver-ice]

@foued-soft-queue

From a UX perspective, it’s not ideal that the error messages for empty customer or users (Owner, Assignee) appear at the top rather than next to the relevant dropdown fields. Additionally, the message “This issue cannot be fixed in the current form.” is very confusing. I highly doubt this won’t be criticized during the usability test.

This is where things get tricky. The id and username fields that are required of on a different document. In your CDM context, you can add new documents or edit them and you do this on a different Form. As the required Field that you need to fill is on a different Form you see:

@foued-soft-queue

“This issue cannot be fixed in the current form.”

So you need to change this message there is a workaround that involves moving the error field, for example the id on to the current screen of the Form and then hiding it. It looks a bit like this

Make relationship between models mandatory

For 2, there is a ticket (A12-13297) ready for planning, which would solve this. But currently this is only modelable with a workaround, which I could show you. The result would look like this: [image] For 3, yes. I created a ticket (A12-15411) to solve this issue on server-side. Currently this is not possible without custom code.

A12-13297 is still waiting to be planned but progress has been made with Message Display elements in the Content Model (A12-16272) which gives me hope that we could get these elements in the Form to display error messages with bindings.