Skip to main content

I have created a Checklist that has a Yes/No question. If the tech answers No, a comment is required.

Question #1 - mandatory - Yes/No question

Question #2 - If Question 1 = No, Text Comment is Mandatory

Question 1
Question 2 

On Mobile Edge, however, the Tech can answer No and save without adding the Comment. The status of the Checklist is Pass.

When the back office user tries to invoice or change the SV, an error blocks them saying “There is an Open Checklist on this order.”  At this point, the checklist cannot be edited in any way. It cannot be removed from the order either. 

I have reviewed my Checklist setup with my Astea Business Consultant to confirm that it is set up correctly. In my opinion, this is a bug in Mobile Edge that is not respecting the Mandatory comment.

I am on Alliance v14.

To resolve, I have to create a request for IFS Support to run a query to fix the order and invoice my customer. This causes significant delays in billing.

Have you seen this before? Any suggestions on how to correct without requiring IFS involvement to fix the SVs would be greatly appreciated. 

Tracey, I see that you opened a ticket in support, US0062236, and we will review the issue as both data and a possible bug.  Thanks for the details! 

Hi Tracy.


We have found similar issues, and a quick fix (not solution) is to navigate to the order via the Service Order or Order Locator module, then navigate to the Activity and zoom in. Remove the disposition, navigate to the checklist, fix it, then go back to the activity and add the disposition Resolved. then only Apply/Save.

Hi Tracey,

 

I will talk to a developer who is currently working on your ticket.

This appears as standard issue I was recently applied a fix to the source code for another customer on V15.

@Gene Maltepes  - We are still on v14. How soon can that fix be applied to my database? Do I need to request an install?

This is the best news ever. We have been wrestling with this issue for years now. Thank you!

Tracey

@Gene Maltepes  - We are still on v14. How soon can that fix be applied to my database? Do I need to request an install?

This is the best news ever. We have been wrestling with this issue for years now. Thank you!

Tracey

 

@Tracey Kilburn - the fix will be applied to a source code.

I’ve just reassigned the ticket to myself - I have verified the corresponding code fix from V15 should work for V14 as well. I see you are scheduled for the next consolidated release shipment on Dec 8th.

 

Speaking of a temp solution, can you specify please all problematic orders on the ticket US0062236 and I will apply a (mass) data fix in your Prod database if necessary.

Reply


Terms & ConditionsCookie settings