I would like the option to have the ability to hide the data field name from a user, when collecting the data. This would be particularly useful for cases when the naming convention of a data field is generalized for internal workflow purposes. For example, I have a general Custom Action that can update a Ticket Attribute. Thus, the fields for this action are named “Ticket Attribute Name” and “Ticket Attribute Content”. By allowing the user to update the “Ticket Attribute Content” field, I can easily collect their information and store it inside my ticket attributes. However, this is not a good look on my company and makes the automation look unpolished.
In addition, we could see how this is useful for branching logic inside workflows based on data attributes that possess generalized names which can be used in several contexts. This will help to clean up my attributes in my workspace, reduce the number of Custom Actions I will have to create, and allow for companies to look more professional while maintaining tidy and efficient background logic.