Issue Summary: When a SIMS entry error occurs in ServiceLink, the system-generated warning message fails to indicate the specific segment where the error resides. Enhance the error messaging logic to include the segment identifier associated with the errant SIMS entry. This will allow users to quickly pinpoint and address issues without exhaustive manual review.
How often would this idea be used? | Daily |
How much time would you save when the idea is implemented? | It would save hours of work |
How many people at your company would benefit from this idea? | Most people (25 + ) |
What problem is your idea trying to solve?
resolving SIMS errors in a faster and more effective way by having the SIMS error message highlight what segment the sims error sits |
Hi Mark,
Please see the attached document. The error message indicates the number of SIMS error occurrences but does not specify which segments they relate to. In cases such as a machine rebuild, where there may be up to 200 segments, identifying the specific segment with the SIMS error becomes a very time-consuming and frustrating task.
Travis can you give a screenshot showing an example