Evaluate Rules GP Tool: Version Targeting for Branch Versioned Layers

[Ofir_Mazor]

The documentation for the Evaluate Rules geoprocessing tool states that it operates on the sde.DEFAULT version of the input workspace.

However, when the input is a feature server URL (instead of a direct enterprise geodatabase path), testing suggests that it is possible to target a specific branch version by appending a version identifier to the URL, using the following conventions:
 https://...my-feature-server;version=my-version-name

Questions:

1. Documentation Clarity: Why is this method for targeting a specific branch version not explicitly documented alongside the feature server URL input parameter? This is a critical capability for users working within a branch versioning environment.

2. Usability Enhancement: Since this version-targeting functionality exists, would it not be significantly more user-friendly to add an optional, dedicatedversion_name or version_guidparameter to the Evaluate Rules tool itself? This would eliminate the need for users to manually append a convention to the input URL string.

[HusseinNasser2]

Thanks Ofir for the feedback. We will update the documentation to include the version= option its a valid request. 

While you can do all of this today through error inspector, we will work on a better user experience in gp tool to allow users to select the version name and expose version specific properties such as evaluating features modified in version.