Hi, The NEW_CHANGEORDER process does not accept container attributes and it is not meant to be executed via the API. It is meant to be used via the UI. Currently there is no standard change process that supports the addition of a sub item to an exi...

Hi Mukhtar, The CHANGE_PRICE process was built to support changes to price conditions in a Subscription Contract via API. This process is not available for execution via UI. If you are working with the UI then during the execution of any ISTA ch...

Hi Indraneel,In general ISTH processes will be available on an inactive Contract if the preceding document is in ‘Completed’ state.In your case I presume the preceding Order that created the Contract should still be open for changes as the Contract i...

Hi Vijay,In case of scale down (say from quantity 2 to 1) you would have to pass in the TR_TYPE and TR_SLOT with the TR_OBJ_ID as blank.TR_TYPE1 EQ (just an example)TR_SLOT1 2TR_OBJ_ID1 (Empty)TR_OBJ_KEY1When TR_OBJ_ID is blank then it will consid...

Hi Vijay,In the standard delivered scenario there is coupling between the Equipment IDs in Object List and the Technical Resource IDs.Hence the Scale Equipment process expects the process container to be filled similar to how you would for the Change...