Currently, attribute rule constraints that are configured against an EGDB in ArcGIS Pro do not display the error message (if it hits a constraint) in the Portal map viewer. It just displays a generic error message as shown below.
While the constraint error message can be found in the ArcGIS Server Manager logs, that just adds overhead to people's workflows by having to open a new tab and querying the server logs to figure out what the constraint error is. And that's assuming they have the knowledge to access Server Manager to begin with (basic users shouldn't even need to use Server Manager at all). When this happens, the end user ends up having to contact an administrator to figure out the issue, which is unnecessarily occupying multiple people's time when the constraint error could just be displayed in the Portal map viewer to begin with.
When end users encounter this message, there is no way for them to understand if this is an attribute constraint rule, or if it is a bigger error/problem that needs to be troubleshooted. This turns what should be a simple attribute constraint rule into a time sink that occupies multiple people's time.
Attribute constraint rules are pretty powerful, but they don't really do us a lot of good when an end user hits a constraint and they just receive a generic error message that requires further troubleshooting.
My idea is that the Portal map viewer actually display the error message configured with the constraint rule in ArcGIS Pro so end users can quickly understand the issue when they encounter a constraint.
