Martyn Houghton Posted August 2, 2016 Share Posted August 2, 2016 At the moment the Business Process nodes all realte only to the request entity and it related objects, however there is no ability at the moment to determine the 'current context' i.e. who is undertaking the action or operaiton which is completing a step or tiggering the end of suspend operation. In Support Works you had the field last updated by on the primary table which allowed you do ascertain some form of context, but there is no equivlany field in the Requet Entity. The reason for wanting this is to be able to branch within a workflow depeding on 'who' completed the last action. For example within our workflow we have a Wait for Request Off Hold suspend node, which when it comes off hold immedialty creates a follow on human task agasint the request owner. However there are a number of reasons why the request may come off hold, one of these could be that it is being chased by our 1st Tier as we have not had a response from the customer and need to put it back on hold. Inorder for them to send a chasing email to the customer they have take it off hold, which creates an activity for the request owner not the person taking it off hold. Similarly if it has come off hold automatically (i.e. like the old Support Works Off-Hold status) we may want to automate the chasign process in the workflow. Therefore it would be good if the BPM nodes, in particular the Supped Nodes had Outcomes specified to determine 'what' the outcome was, i.e. Hold Time expired, Manually taken off Hold, and 'who' undertook the operation, i.e. 'System', analystid etc. This way you could follow the suspend node with a decision branch to automate what happens if the request comes off hold after it expires or if it is taken off hold manually by someone other than the owner we could create a human activity for the analyst who took it off hold rather than for the owner. In short have the BPM being aware of the 'context' of the update allows a much wider dimension for controlling and routing the workflow, compared to the current request entity only standpoint. Is there any plans to add on this context type of information into the BPM? Cheers Martyn 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