Yes/No Trigger Task for Service Catalog Workflows

Idea created by Chad Brown on May 1, 2017
    Long term plan
    Score25
    • Nathan Evenson
    • Jamie Milks
    • Chad Brown
    • Gustavo Trujillo
    • Bryan Sherman

    We are looking to have a New Decision Trigger in the Service Catalog workflow that is not "Approve/Decline". We have Scheduled Catalog Items that have a trigger question, and Approve/Decline in no way fits the decision matrix.

     

    For example

     

    US - Cert Bulletin Review

     

    Instead of needing to phrase everything around the "Approve/Decline" it would be great if we could define that Binary Decision Variable... For example you could have a Binary Decision variable of "Yes (investigation)" and "No (end process)", or "High or Critical vulnerability (create incident)" and "Medium or Lower only (end process)."

     

    Something Like This

     

    This would be especially valuable when working with other applications or other departments beyond IT.

     

    For example, if a workflow task requires someone in Finance set up a person's expense account. They could be given a binary value of "Set up Manager Account (continue workflow)" or "Set up non-Manager Account (continue workflow)".

    What problem will this feature solve?:
    See the description above for embedded scenarios and cases.