What happens to my flow if a step is assigned to a template for user, role or email address and that template resolves to null or empty string at runtime?
In flows created in v8.x and prior, if a template assignment resolves to null or empty string the flow will morph into a screenflow.
For example, a Sales Rep performs the first step in a Sales Order Workflow to enter the customer's information, which includes a control for an email address. The second step has an email task assignment to a template for the customer's email address control in the first step. If the template resolves to null because the customer's email address was not entered, then when the Sales Rep submits the first step she will automatically see the second step (meant for the customer) as a screenflow. Another example is if a tenant admin set up a user without a Reports To, it could cause an Expense Report to morph to a screenflow.
In v9.0, a new feature has been introduced that will improve this workflow behavior. For workflows created in v9.0 and later, when a task that is routed to a templatized user, role, or email that resolves to null or empty string, the task will be assigned to the "invalid-task-assignment" userId and a notification with be sent to flow admin users (or the tenant admin user if no flow admin is configured.) This will enable flow admin users to easily search mis-routed tasks assigned to the "invalid-task-assignment" userId and re-assign to valid user. At this time, this feature is only available to flows created in v9.0 or later. For more information about task assignment and task boundaries click here.
A future release will provide the option for the designer user to migrate a flow created in a prior version to take on the new v9.0 Invalid Task Assignment notification behavior (Enhancement Ticket TIP-26372.) Please be sure to subscribe to our Release Announcements so you will get an email when new features become available.
frevvo Customer Success Team