Berto2002 Posted June 29, 2022 Share Posted June 29, 2022 I want to use workflow to log a new change. I am using the service manager > Entity > requests> log request> log new change option in an autotask. A new change appears to have been created with a reference number and a service and catalog item applied but the BPM workflow is applied and the autotask workflow does not move to the next node so it implies this 'create' node goes into error just before it finishes with the following error showing in the autotask pop-up: Xmlmc method invocation failed for BPM invocation node 's1/flowcode-a65eff70': 0200 apps updateReqTimeline FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqTimeline): nodeName: Customer Notification; nodeId: fac30e82-d816-4a59-af5b-1824229c13c3; At 228/1: "Uncaught TypeError: Cannot read property 'h_requesttype' of undefined" throw(e); _fc_node_exec_fac30e82_d816_4a59_af5b_1824229c13c3 The rest of the configurations on the node is as follows: My suspicion is that the "log new change" operation is not successfully setting the request type to change in the background. That is not one of the configurable items in the options menu. Is anyone else either seen that error or know way to avoid it or workaround please? Link to comment Share on other sites More sharing options...
Steve Giller Posted June 29, 2022 Share Posted June 29, 2022 Can you post the "top half" of the node configuration, please? Link to comment Share on other sites More sharing options...
Berto2002 Posted June 29, 2022 Author Share Posted June 29, 2022 Link to comment Share on other sites More sharing options...
Victor Posted June 29, 2022 Share Posted June 29, 2022 1 hour ago, Berto2002 said: updateReqTimeline FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqTimeline): nodeName: Customer Notification What is this node configured to do? Is it what the name implies, updating the request timeline? Or some other operation that will (also) update the timeline? Link to comment Share on other sites More sharing options...
Berto2002 Posted June 30, 2022 Author Share Posted June 30, 2022 The idea of this workflow is to initiate a Change Request off the back of a Service Request or Incident to save my Agents needing to do this manually. It's in the early stages of development as an idea at the moment but this error is a blocker. I do not know where that nodeName of "Customer Notification" comes from. These are the names of the Nodes I have in the AutoTask and none have that name. The one that appears to not complete is highlighted (the one I showed the details for in the above posts) Link to comment Share on other sites More sharing options...
Victor Posted June 30, 2022 Share Posted June 30, 2022 9 minutes ago, Berto2002 said: These are the names of the Nodes I have in the AutoTask and none have that name What about the workflow associated with the request? Link to comment Share on other sites More sharing options...
Berto2002 Posted June 30, 2022 Author Share Posted June 30, 2022 There is a typo in my first post. I said "but the BPM workflow is applied" but I should have said "but the BPM workflow is NOT applied". In other words, the ticket does not get a workflow; it's not getting that far. I do not have a node with that name in the workflow to the best of my knowledge because it's a Change flow I don't have a Customer Notification as it's all our internal ICT agents. Weird one that message Link to comment Share on other sites More sharing options...
Victor Posted June 30, 2022 Share Posted June 30, 2022 @Berto2002 difficult to say why with this info... you probably know what I am going to say... https://www.hornbill.com/support/ ... Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now