After submitting a ticket and being advised an improvement could only come with an enhancement, we've submitted #114387:. Please endorse if you believe this would help you, too!
The purpose of this enhancement is to augment the error messages commonly displayed throughout GHR to display more information when it's available. These errors can appear if something within the LPL is invalid, if there's a constraint that isn't being met, etc. While they're generally pretty each to understand like "Termination Date cannot be before Start Date", some of them can be really hard to troubleshoot.
In the request, I included the example of attaching an internal candidate to a job req. To do this, the system kicks off an action (AttachCandidate) which lives on the Candidate business class. That action has invoke settings to create a job application on the JobApplication business class. That Job Application further tries to pull in credentials from the internal candidate's linked employee profile on the EmployeeCredential business class. Since internal candidates have their credentials copy over to JobApplicationCredential, this can cause an error if it detects a duplicate. At that point, though, you're four business classes removed from whatever you were trying to do and it can take a long time to try to figure out what's actually wrong.
To improve upon this, we're suggesting the error messages in GHR be updated to include as much extra info as possible, such as the business class the error/constraint lives on, the line number within the LPL on that business class that cites the error, the initiating action that started the chain that got to this situation, etc. Not every error will be able to pull all of this information but, if the current code can display the error message directly from the LPL, I don't see why it couldn't also display this information.
Even if they just added it to the 'Show Details' button, this would save so much time with trying to track down what needs to be changed before the action can be successfully completed.
Example, you get an error like this:
You look around the business class LPL to try to find this messaging and see nothing. Determined, you spend an hour looking through all sorts of spaces until you eventually find a delivered constraint in a different business class:
If the error message could have told me any/all of the below, it would have been 50x faster to figure out the problem.
Error!
- [Error Text]
- Business Class: JobApplicationCredential
- Initiating Action: Candidate.AttachCandidate
- [Error Text] from LPL Line #773
- [Error Text] returned from constraint (DuplicateJobApplicationCredentialRel not exists)
