This content has been marked as final. Show 1 reply
Hi, I am not aware of any expected duration linked to an order.
As to the process, there is an exected duration linked to each process.
You can then declare a jaopardy on the Order editor to be triggered when the process expected duration is exceeded.
The dowside of that is that the Design Studio does not let you configure this expected duration on the Order editor.
If you look at the xml resource, however, you can see it is there populated with a default value of 86400 seconds i.e. one day.
You might be able to modify this value in the xml file and test whether it is reflected in the DB metadata.
The truth is the old tool gave you the possibility to set and modify the process expected duration.
However, I wonder how this would be handled on Orchestration Orders where you do not have a single process assigned to the order (the way it happens with static order), but one assigned to each executable component. This might be the reason why the attribute is hidden in the DS GUI.
You might try an SR for this. You could argue with lost functionality, since in 6.3 the feature was there.
Hope that clarifies the matter.