Skip to main content

We are using V14.5

When using Mobile (Mobile Edge V15.3.2.0 1) in the “History” tab, when doing a “ADVANCED SERVER SEARCH” we are finding that not all service orders are appearing, even some that were previously sent to Mobile.  So I was wondering what the rules/criteria are for what is included in the search results?  Is there a setting somewhere that affects this?

MOE-99100 is enabled, MOE-10301 is set to Y, MOE-600 set to 45 days (the missing one has a date of 28 Feb 2022, so is within that time span.  It is resolved, not excluded from Mobile, Request Type is PM, status 500.Resolved).

Can you suggest why this Service Order might not be included?

Thanks

Chris

Hi Chris,

Hopefully I looked at the right query definition, if not @Reid Gilbert will correct me and give the proper information.

Your order is RESOLVED which means it is not yet moved to history.  The DAL query I found was fx_service_order_history_query.query and has these joins and criteria:

FROM c_order_line, 
       c_service_call,
       c_service_call_env 
WHERE c_order_line.order_id=c_service_call.order_id AND 
      c_order_line.order_id=c_service_call_env.order_id AND 
      (c_order_line.order_type_id = 'service_order') AND 
      ('where_cond'=:where_cond) AND        
      ('a_search_name'=:a_search_name)

This query is only searching orders actually moved to history and would not pick up Resolved orders.

 


Hi Phil,

There is an option in the search, to include Open Orders, so how does that get factored in?…

 

 


Then I think it executes a 2nd query called fx_open_orders_by_site.query.

Here, the query is for orders at status less than Resolved:

 

Where (order_line.order_stat_uniq_id < 500)


Thank you Phil.  Do you think that is a mistake?  It seems odd for this query to bring in everything, including history, except status 500, which is really still an active status.  I would have thought that should be less than or equal to status 500.  In fact, I would have thought it should be:

Where (order_line.order_stat_uniq_id < 900)


Hi Chris, you mentioned the request type on the order that is not showing is PM, so can you run the same server search from mobile one more time and check the PM checkbox?  (this is an either/or setting, we add this condition to the where clause prior to execution at the DB level so this may be the reason why this order is getting excluded...this should still pull orders with Resolved status).
 

 


Thanks, Reid. 

 

Chris,

I don’t think it makes sense to bring down orders with a status higher than Resolved as all the work on them will be done in the backend… this includes Completed (700), Needs Audit (800) and Pending Invoice (850).  Invoiced is status 900 and is in history.

Also Node security is involved but this should not be an issue if your field engineer is already getting work orders for the site anyways.


Hi Both,

Thanks, we are able to see the missing orders now, with the PM box ticked.  Useful to know it is an either/or selection too.

Thanks

Chris


Reply