Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Assignment Option for Manual Approval for Customer Order

Aneesh-D
Tera Guru
Tera Guru

In case of Customer Order Manual Approval process, currently there is no provision to assign the approval task to an agent or to a group. What's the recommendation for handling this use case?

2 ACCEPTED SOLUTIONS

Satoshi Abe
Mega Sage

@Aneesh-D 

I have the same question as you.
The current function of the Approve button in Customer Order is in effect a trigger for Decomposition, and the approval itself needs to be confirmed by a person.
One way to handle this in the current OOB is to generate an approval task in the Order Enrichment process and assign an approver in this task.

https://www.servicenow.com/docs/bundle/xanadu-order-management/page/product/tmt-order-mgt/concept/or...

 

However, this is not the original intent of the Order Enrichment process, so I think it would be desirable to enhance this functionality.

View solution in original post

@Aneesh-D You could trigger a Flow against a Customer Order record when the state changes from "Submitted" to "New" and the flow can have an Approval process related tasks.

View solution in original post

3 REPLIES 3

Satoshi Abe
Mega Sage

@Aneesh-D 

I have the same question as you.
The current function of the Approve button in Customer Order is in effect a trigger for Decomposition, and the approval itself needs to be confirmed by a person.
One way to handle this in the current OOB is to generate an approval task in the Order Enrichment process and assign an approver in this task.

https://www.servicenow.com/docs/bundle/xanadu-order-management/page/product/tmt-order-mgt/concept/or...

 

However, this is not the original intent of the Order Enrichment process, so I think it would be desirable to enhance this functionality.

@Aneesh-D You could trigger a Flow against a Customer Order record when the state changes from "Submitted" to "New" and the flow can have an Approval process related tasks.

@ShashankInamdar - How do we get the Order to Submitted in the first place when created using TMF622 API?
As i can see the state is set to New in TMFProductOrderUtil script include in

createOrderHelper function as below:
this.updateOrdTypeAndPriceAndStateOnCustOrd(orderGr, orderObject.orderType, TMFOrderAPIConstants.ORDER_STATE_NEW, custOdrPriceObj);

can you please guide on the best way to move state from draft -> submitted ?