Berto2002 Posted October 18, 2021 Share Posted October 18, 2021 I see a need to have a kind of trigger process acting on some Requests that "watches" a Request through it's workflow and fires-off an AutoTask if certain criteria are met. The key difference between this suggestion and any existing "decision" node is that it is 'floating' and can fire at any time. Hornbill Service Manager has a great strength in the workflow approach but it has a weakness in that it does not provide for those circumstances which cannot be predicted. Use case: We have set-up our Major Incident process to perform a number of actions for an MI that don't happen for normal Incidents such as: Set-up a Teams Channel for collaboration Email the Ops Management team for immediate awareness Prefix the Summary Create a Problem record (later used for Tracking causes) But the above flow is configured to follow-on from the initial logging of an Incident with Priority Major. Once that point is passed, changing the Priority to Major has no effect and we rely on manual efforts again. It is quite often that an Incident comes-in quite innocuously from a user as a Medium or High Priority and we then need to move it up AFTER triage. I am working on an AutoTask that we can use for these four actions but it will still need someone to press the button. My suggestion is that a new Feature of, say, "Triggers" could be added (in a similar way to Custom Button functionality) and the criteria in Triggers would not show a button but would fire the AutoTask directly if the criteria were met. I would configure it to fire on: Request Type = Incident Status = NOT Resolved, Closed, Cancelled Priority CHANGED TO Major Other use cases: How about having one that looks-out for various user responses like "escalate", "not happy", "supervisor" and have that Trigger notify the Service Desk Manager that something could be going wrong with the customer interactions on that ticket? If a Change is raised on a certain Service or is linked to a certain Service during it's lifecycle, certain notifications can be made to stakeholders I agree it is potentially possible to think through when these AutoTask processes might be run and to duplicate elements of the workflow in the core BPM on a "what if" basis. But that requires a lot of work and duplication. Interestingly, it would be easier if it were possible to move back to other stages of a BP because we could configure have regular "loop-back and check" cycles which would only act if certain criteria had been met since the last check. I would be interested if other users can also see usefulness in this feature idea or would have other ideas for how/where it would be most useful. Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now