Attribute Rules and Licensing Levels?

[Vinzafy]

Hey all,

Reaching out regarding attribute rules and licensing levels as I can't seem to find a solid answer. 

For context, this is in relation to attribute rules that will be created on an enterprise geodatabase and accessed by editors via feature services published on a Portal. Data editors will utilize either ArcGIS Pro to edit data, or in some instances, a solution built in Experience Builder and hosted on a Portal. 

My understanding is that creation and management of attribute rules requires a Standard or Advanced license. However what isn't clear is if execution of attribute rules will occur regardless of user license level, and function for both ArcPro and Portal solutions. 

Thus my question is, if a user has a Basic ArcPro License and a data editor role in the role respective Portal where the feature services were published to, when they make edits to a dataset with attribute rules applied to it, will those attribute rules be executed?

I hope the answer is yes as the attribute rules exist on the database level, but I couldn't find a source that confirms this. 

Thanks in advance all,

Vince

[AyanPalit]

@Vinzafy There are multiple factors to consider:

• Rule type (constraint, calculation, validation)
• Execution location (client or server)
• Evaluation type (immediate or deferred)

Based on the ArcGIS Pro license levels and ArcGIS Enterprise Functionality Matrix , a Standard Pro license will be needed to update data using client-side attribute rules. Certain attribute rules  can be triggered if they are server-side and the dataset is accessed via a feature service. The Ready to Use Rules  provides access to a gallery of configurable checks that support creation of constraint and validation rules. This is available with an ArcGIS Data Reviewer extension license extension with Pro Basic. The Attribute Rules view is read-only when accessed from an ArcGIS Pro basic license, web feature layer, or database connection as a user who is not the data owner.

Given the variables, your situation may be unique so test the compatibility before rolling out the desired attribute rules.

[Vinzafy]

Thanks for your response @AyanPalit! So to confirm, a workaround for data editors with a Basic Pro license is to create the attribute rules on the enterprise geodatabase, publish it as a feature service on the respective portal, and then have the data editors add the feature services to their workspace?

For example, if an attribute rule was created that automatically populated a value in field X based on a domain value chosen in field Y, that attribute rule would still execute for an editor with a Basic License if that layer is published and accessed as a feature service in Portal? 

Also, you mentioned that, "certain attribute rules can be triggered server-side...". Is there a definitive list for what type of rules can or cannot be triggered server-side?