Edit CLM Agreement Attributes should accept variables as an input type.

Currently, for many of the built-in attributes (Default Document Attributes) the only way to update with a non-hardcoded (configurable) value is Expression.

 

This incurs a +/- 500ms round trip delay and places (often unnecessary) load on the expression value - only to evaluate an expression that is is usually as simple as:

GetVariableValue("RenewalUnits");

Allowing the use of variables, via:

• Selection and/or
• Variable Expansion (e.g. ‘<%#Variable.RenewalUnits%>

Would place less load on the system, be simpler to configure/debug and run ‘MUCH’ faster.