Order Management task - Start Date, Due Date and Duration fields populated but not as expected

[bmedic]

Hi all,

Build name: Xanadu
Build date: 10-18-2024_1248

I have defined the decomposition for one product I have specified in the instance. There are several order management tasks that are being created. So far so good.

However, I cannot get the desired duration for which the task was populated.

In the design time, task durations are defined in the Order Task Duration Assignment Policy decision table, but in the runtime, it always sets the Duration field to 1Day. Also, the Start Date and Due Date fields are always set to the date that the OM task was created. 

Can someone direct me to the part I'm missing?

Thanks all in advance!

[bmedic]

Hi all,

Found the reason, so for all of you who might encounter the same issue, please read below:

For Non – jeopardy management enabled orders, the timeline view does not present an accurate duration and estimate.

For baseline date calculation, information about the previous and dependent tasks and their duration is required. It is possible only if jeopardy management is enabled for the order. Hence, for the non-jeopardy order, the timeline view is not accurate. Instead, I recommend using the order timeline grid view only and personalize the column data to be able to take advantage of viewing the hierarchy of order entities related to data selectable from the column fields.

[Satoshi Abe]

@bmedic 

Did you set the "Configure the Order Jeopardy Enablement Policy" in the decision table?

You need to set the Specification Category for for top-level product or service specifications.

https://docs.servicenow.com/bundle/vancouver-order-management/page/product/tmt-order-mgt/task/enable...

[bmedic]

Yes, I did.