Attribute Rule equivilent to "Last_Value" method in ArcMap Attribute Assistant

[JoeBryant1]

Add the ability to create an Attribute Rule in ArcGIS Pro that is equivilent to the "Last Value" method that was available in the Attribute Assistance Add-In in ArcMap.

Example: if digitizing many features from a plan set, it saves time to have certain fields like "Install Date", "Location Source", "Plan Set Number", etc. be automatically populated with the last value you entered in an edit session. Once you switch to a new plan set, you enter the new values, and the Last Value is updated to the new value and populates going forward.

This is different from setting default attributes in the Create Feature Template, although editing your default attributes in the feature template is the way to achieve this, currently. However, this can be cumbersome if you have A LOT of different templates for different feature types, subtypes, sizes, etc.

*Bonus points if we can click easily review, clear and/or update the value stored in the Last Value variable, like we could when using the Attribute Assistant toolbar.

This may not need to be an Attribute Rule, if something more equivilent could be achieved by adding functionality to the Create Feature Template properties, like being able to enter a variable instead of a value (i.e.: %LastValue%).

[AndrewMurphy3]

This is also something that we would need to maintain a datasource across all edits in the Utility Network rather than having to paste it in for each edit.

[Scott_Harris]

@JoeBryant1

Regarding your idea for bringing the Last Value method to Attribute Rules, did you see this blog that shows how to simulate the Last Value method?:
https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/simulate-session-attributes-wit...

And just an FYI regarding feature templates: you mention setting up default values for templates can be cumbersome with a lot of templates, which is true, but did you ever try using the Active Template pane for setting temporary default attributes while creating new features:

For example, this value of '88' will be remembered as long as this template remains active:

You can also revert to the default values or save the attributes to a new feature template, if needed: