Hi @Hashmit ,

From APP 10 the route work order concept is removed, and new function of PM group & merge concepts are brought in to group the PM actions. So, when you use grouping of PM action functionality the auto-generated work order for the grouped PM’s doesn’t have the reference of the object ID in the work order as work order can hod the reference of only one object but the reference to object ID will be seen against the work task as work tasks are created for each PM’s of that group. If you use merge functionality the object reference will be moved to work task step as only one work task is created with work steps for merged PM’s

But when work orders are autogenerated for the non-grouped PM’s, then you can see the object id refence in work orders. From APP 10 all the work execution are done against the work task and work orders hold the information of the work tasks.

Hope this helps!!

Regards,

Mithun K V

@Hashmit ,

Additional to what @EqeMithuV has mentioned:

What is the reason why Rule Id is filled. This field is meant for grouping Work tasks on one Work Order. So there can be multiple Work task for multiple objects for one work order. 

Maybe your customer is using this field for other reasons then grouping work tasks.

So if you leave the fields related to the group and merge functionality empty, the Object will be filled on the work order as well.

Good luck

Robert

Hi @EqeMithuV @EqeRobertK thank you so much for your explanations. It was helpful.