In their quest to improve overall performance, security and versatility, TrackVia engineering identified a change that needed to be made to the way that Flows are configured and provisioned to Roles within the application.
This fix ensures that users have explicit permission to all View-Form combinations utilized in Flows and enforces that Add Tasks in Flows must be followed immediately by a View Task before the Flow proceeds to an Edit Task.
In the Flow Builder, if you attempt to build a Flow that navigates from an Add Task to an Edit Task, you will be alerted that you need to insert the appropriate View Task:
In order to save the Flow successfully, a View Task must be inserted between the Add Task and Edit Task, which can easily be searched using the Record ID of the record associated with your Add Task so that users automatically proceed to the next step of the Flow:
Article is closed for comments.