We have a variety of processes which share common steps, and in an effort to avoid updating multiple places when one of these steps changes, have built out a system that saves the user’s spot when they navigate away from the primary SOP to one of these common / shared processes (usually in a different App), and then return them to the appropriate place in the original SOP when ready.
Modular SOPs visualized:
In our current solution, we save the users step and app in a table before navigating to one of these common steps, and then set up triggers in our “next” buttons to see if the user needs to jump back to the appropriate step in the primary (original) SOP or if they should continue to the next step in the current app. This requires quite a bit of trigger maintenance and can get complicated quickly, so I’m looking for ideas, either architectural or tactical, to build out a system that supports common steps more easily. We don’t have a ton of content, so a major overhaul is OK if it simplifies things long term.
One smaller item that would help is the ability to go to an app or step by loading the name from a variable or table (instead of selecting from the drop down list). I understand this would require valid and unique names, but would allow us to simplify the logic quite a bit. Instead of saying “if this then go here” over and over, we could just say “go to whatever is saved as the user’s next step”