cancel
Showing results for 
Search instead for 
Did you mean: 

Avoid Heap Error on PM WO Creation

Avoid Heap Error on PM WO Creation

Avoid Heap Error on PM WO Creation

Currently when the PM Process runs all Active PM Plans that have an End Date greater than today and meet the criteria set in the process are queried regardless of the PM Schedule.  This often results in too many records getting queried and causes errors in the process.

 

If we create a roll-up summary field on PM Plan to get the minimum Scheduled On date from the PM Schedule the field can be included in the initial query to get all Active PM Plans, that have an End Date greater than today and the Roll-up field is within the N Days specified on the PM Process.

 

This would limit the query to only look at Plans that should be generating a work order as opposed to all that meet the criteria.

What is the underlying problem do you intend to solve with this idea?
This would limit the query to only look at Plans that should be generating a work order as opposed to all that meet the criteria.
How is the problem being addressed today, if at all?
It is not
Product Area?
Preventive Maintenance
What version of ServiceMax are you on?
Winter 17
6 Comments
Grill Chef
Grill Chef

This should be "out-of-the-box" functionality.  We came upon this issue as we were rolling out new sites.  It was good we found this in small amounts, can't image what the impact would have been had we gone live with all of our branches and this problem appeared.  We shouldn't have to experience this issue at all, if this functionality can be build into the standard application instead of a "work around" that should be offered.

Staff Chef
Staff Chef

Hi @josh_trujillo , are there any plans to fix the product here so it works correctly?

Product Team
Product Team

Hi All,

@deirdre_yee - Here is another idea that somehow ended up in the discussion forums. Previously, this was Idea 1519

@richard_lewis - This issue will be resolved in the upcoming 19.1 release of SVMX package. We will be introducing enhancements to the PM Process engine that will ensure enterprise customers with large volumes of complex PM Plans do not encounter regex/heap errors or exceed query limits when processing PM Work Orders from their plans. While improving performance, the overall imprint of the PM Engine will also be reduced within the org, taking up less processing time and effort for the backend. 

CC @josh_trujillo / @amit_jain 

Community Manager
Community Manager

@lacy_cotton We were able to move the idea to the Idea Exchange and turn it back into an idea. Hopefully we didn't lose content.

Product Team
Product Team
Status changed to: On The Roadmap

Thanks for the move @deirdre_yee !!

Product Team
Product Team
Status changed to: Delivered

I'm happy to communicate that this idea was delivered as part of the enhancements for PM Process in 19.1 Release. These enhancements ensure enterprise customers with large volumes of complex PM Plans do not encounter regex/heap errors or exceed query limits when processing PM Work Orders from their plans. While improving performance, the overall imprint of the PM Engine will also be reduced within the org, taking up less processing time and effort for the backend.