Hi ​@SimonP 

Can you select 1 step and check whether this status option is available for you? If yes, you can set the task to work done or cancel it.

However, if you have a large number of steps, then what you can do is, first filter them by the status.

For example, 1st filter with status = Not Done and then select all the records under that search criteria and set to Work Done.

Then move on to other status - for example Pending.

Fore Done and Cancelled statuses, you don’t need to do anything.

Hope this helps.

Best Regards,

Thilini

Hi ​@Thilini Kumarasinghe,

Yes I can do that.

So it’s impossible to by pass the completion control when the status is changing ? 

HI ​@SimonP
when you are using merge on a PM Action it will create steps. It is necessary to get information back to the PM Action that this Maintenace Plan line is completed, otherwise the next Maintenance Plan line might not be generated. Leaving the step in it orginal state will not trigger the PM Action Maintenance Line to be completed.

If you have a PM Action, it is something that should be completed no matter if it is generated as a Work Task or a Work Step.

best regards

How does one use merge on a PM Action? What screen/button is used to initiate this?

Asking for research purposes, the behavior here of mandatory steps is exactly what I want.

Thanks!

Hi ​@benjsherman 

You can find the setting in PM Action - General tab. Please note that for merging, both PM Group and Merge button needs to be defined.

 Merge

• Used by adding a value in 'PM Group ID' and the 'Merge' flag set.
• The 'Merge' concept is only to be used for simpler actions that you want to perform as a part of a list together with other similar simpler tasks as a checklist. As example for simpler inspections or lubrication rounds etc. where you not need instructions down on step level. This is also a reason for why a lot of criteria need to be met to fulfill a merge.
• All Work List lines from one or more PM Actions (max one WL per PM) will in this case become a Work Task Step underneath same 'merge' Work Task on the generated Work Order. This 'merge' Work Task will be created just by the purpose to be a holder for the Work Task Steps created.
• The execution will be done on Work Task step level.

• Same PM Group ID
• Merge flag set
• Fall due at same time
• PM Action just contain one Work List line.
• For the things planned, they also need to have same planning for resources, material, planning, customer, contract and work type.

Hope this helps.

Best Regards,

Thilini