Skip to main content

We have created a new checklist which is valid for both UM/PM service orders.  The checklist is tied to a specific activity.

We have created a process flow to add the activity to open service orders where the status is less than resolved.  The issue is that on some service orders the checklist is added correctly, and on others the checklist is missing.

We believe it may be related to the “Effective Date” on the checklist vs the “ETA date” on the service order.  The orders that have the checklist all have an ETA date after the Effective date of the checklist.

We tried to backdate the Effective Date directly in the DB (could not do it through the UI) to see if this would resolve the issue but no luck.

Is this a known issue and is there a way to work around this?  We are running v15.4 SU5

Thanks!

Hi Nick,
If you retrieve one of the orders where this is not working directly in the Service Order module in Alliance, and then manually add the same activity record via the Alliance UI...does the checklist get added automatically in that case?  (if it’s not getting added through the UI then it’s probably not going to work through the process flow).  If it doesn’t get added automatically then drill down into the Activity record and click on the Checklist tab and try to add the same checklist manually by clicking on the Add Checklist button...see if it shows as an option on that screen or if it’s filtered out:
 


Thanks,
Reid

Hi Reid,

Yes, manually adding the activity also has the same issue with the checklist not getting pulled in, so we also ruled out the process flow being the issue.  We can zoom into the activity and then manually select the checklist and it will save properly.  We have roughly 700 service orders which would need to be manually added, so we’re hoping for a better way of accomplishing this.  

Thanks,

-Nick

Hi Nick,
I would suggest logging a support ticket for it at this time, please include an example of a service order and activity code where the checklist is not getting added automatically in the Alliance UI layer (we would need to research that further to determine whether it’s a bug or if it’s being excluded intentionally by design...there may be some other fields that it’s checking to see if the checklist is applicable other than the ETA date).
Thanks,
Reid

Update:  It appears the comparison is being done between the checklist “Effective Date” and the service order “Open Date”.  When the open date is before the effective date, the checklist will pull in correctly.  We are working to confirm this.

Reply


Terms & ConditionsCookie settings