We have a form running in Forms 11.0.2311.50553, that has a User Task that's name contains a variable.

In Forms, that step is properly named utilizing the actual case # variable's value.

However when this Form's process triggers a Workflow (version 11.0.2102.235) after this step, that Workflow sees that same step's name with the variable name instead of the variable value.

This was working fine up until recently when Forms was upgraded (minor upgrade).  I do not see that as a bug that is fixed with Workflow 11 Update 3 or a known issue for Forms Update 5.  Has anyone else noticed this issue with Forms 11 Update 5?  I've updated the Workflow logic to replace that variable name with the retrieved variable value as a work-around but am hoping this is fixed in the next version.