Additions/Removals to Workflows

Curtis Cecil

I wanted to put an idea that I posted in the idea bank out there to see if anyone else has encountered the same thing. I just started working with workflows in NXT and in testing it out I discovered that you can add names to the list/query that you use and it will drop them in the workflow and all steps take place as scheduled based on when you put the constituent in the list/query. However, we tested to see if you could remove someone from the workflow and it removed the name from the list/query…but it didn't remove them from the upcoming steps of the workflow? I asked BB chat about it and they said that I would have to cancel the original workflow, then I would have to set up two new workflows (one for the individual that I was trying to remove, and one for the other folks that were in the original workflow). This seems like an a large amount of work when I just want to remove a name from the workflow so they don't receive the remaining steps. Not to mention that I would have to create the new workflow for the original list to begin where it left off so that it doesn't duplicate workflow steps for those constituents.

So I'm looking to see if anyone has advice on how to navigate this without all the additional steps/workflows having to be created? If not, I would love to have support on my idea for the developers to make changes so that the removal of a constituent from a workflow is simplified. Thanks!

I'm not sure how to link my idea post here, but hopefully if you would like to vote for it you can find it by searching for my name, the idea name ("Update workflow list based on adjustments to the list itself"), or it looks like the idea number is 5017.

Faith Murray

Curtis, this same dynamic exists in database view, when adding Action Tracks. Once an Action Track has been catalyzed, RE enters individual action records into constituent records. To understand whey they cannot easily be removed through Action Tracks/Workflows, it is because only the actions are unique records. Workflows and Action Tracks basically operate as conditional “bulk add” functions in this case, and the created actions are not relationally linked to them because the workflows are not a table record.

That being said, we all share your dream for a perfect database and will happily vote for your idea if we can find it!

To remove unwanted actions from an individual, you will therefore need to use the Bulk Delete tool (which presently only exists in database view).

• If you have psychic foresight and coded all of your Workflow Actions with a distinct Action Type (example: Workflow 1: Cultivation, Workflow 1: Solicitation) you can pull an Action Query of all actions in that workflow that were entered on a specific record. Otherwise, query all actions on the record that were created on a specific date.
• With that Action Query, perform a Global Delete in database view.