At the current client they wanted to have various levels of approval (which may or may not be required based on the knowledge base category itself)
these also have timeouts so if not run within a specific time frame the record would return to draft, previous state or even retired.
Add some field annotations that are again unique per KB ad category.
They also wanted the process to be able to roll back to previous approvers depending on later approvals / rejections and the type of article.
Once published, there is to be an under review where the valid to date could be extended by the author (some people can do this to before the article is under review). If this happened, there is a justification and it then goes back to the KB Managers for approval.
In the end I created extra sections in the KB category so they could add their annotations and times for approvals - if blank skip the step
When the article is fired, it does fire off a number of workflows that are all trigger related
This means that as each flow finishes, it sets the trigger for the next flow
If I need to rollback it is easy enough to do so and when the valid to date is changed, I can kill the workflows I need to replace, reattach the workflows (so any new dates etc are now obtained too) and then I set the relevant trigger so that I now run the workflow I want,
I did consider rollback's, but there were a couple of issues there and making the flow get the latest valid to date is often interesting
