When we are developing Workflows where we use metadata field, then within Workflow, this is using token names that do follow the exact name of the field.

When there needs to be a change in some fields name, then this has a direct effect on the Workflow configuration and running because WF using these fields will not be able anymore to link with them, because the token name is the field name.

We are developping for bigger organization, creating more complex workflows and that effect is not desirable.

Right now, if an organization needs to rename a field (or many), this will take the Workflow configuration team many hours analysing the impact, make modifications, tests in multiple workflows and then push these new WF versions back to production.

Can Laserfiche consider modifying the Workflow engine internal programming (where using fields tokens) where that WF token would be tied in to an internal field ID instead of the field exact name?  Fields configuration screen (in the admin console) could be having another parameter called (Field HardCoded Name that WF would be using), and refering to a User Friendly name for all UI.