Lock & Unlock Workflows with Password

[caltang]

The idea behind encrypting or locking a workflow is good for users to maintain the workflow as designed. 

However, when a user reaches a level of maturity equivalent to that of the builder or more, or even when changes are required - the current practice is to keep a locked and unlocked version of the workflow so that it allows for a change in the future. 

It would be much simpler if we can have the power to lock and unlock workflows with a password. Users can then maintain and keep the passwords so that they can continue with the workflow. 

Not everybody is on Server yet so this feature is very helpful for control before Server migration. Otherwise it’s just password protecting a folder containing the workflow package, then re-locking a new save file each time a change is made or when someone new takes over on prem. 

[maryjdavies]

This would be great!

[TheCoffeeDude]

As much as I like this suggestion, I can also see this being used maliciously or with unintentional malice. What happens if the user is laid off or sacked without notice? And for those who suddenly die or become missing? What about hackers and ransomware? Sudden leave of absence? I'm scratching the surface of the dangers of this suggestion and why there needs to be a way for someone else to decrypt the file (which has similar issues).

[caltang]

@TheCoffeeDude sorry just saw your comment. 

The issues you mentioned can happen now without this idea as the workflows can be password protected and run via Analytic Apps only.

Just adding this functionality to help unlock these workflows would be helpful in scenarios where back ups or the unprotected versions were not made (for whatever reason). 

Not sure how malicious it could be if we unlock a workflow that is locked with email trails and approvals…? I mean, if someone changes a production level workflow right now (that is not password protected) is the same logic. It’ll be disastrous if not sanctioned internally.