Landmark/Config Console/HR Talent - Send Notification LPL Returns Error "Unexpected exception..."

I've never used "send notification" LPL before, but at the request of a user want to test. In the workflow a user triggers an action and we want to send a notification to a specific approver. The LPL seems correct to me, but it's returning the error "Unexpected exception validating: businessClass". Does anyone have an idea as to what could be causing this?

For context this is a User business class that we created. The navigation referenced in the send notification LPL is on the same User business class and the "to:" value is the desired user's Actor.

Any thoughts would be appreciated!

Find more posts tagged with

Accepted answers

All comments

cleverly

Just from looking at the screenshot, it appears you have a red squiggly of doom under the A in RollupPROMOApproverActor. Did you maybe intend that to be RollupPROMOApprover.Actor?

smodarressiyazdi

That pesky squiggly has been giving me headaches all day. Sometimes it takes quite some time to update. That field is an "actor" type, but I have also tried "RollUpPROMOApprover.EmployeeActor" and "RollUpPROMOApprover.agent(Employee).Agent" and have been getting the same error message. RollUpPROMOApprover is an Employee type

cleverly

If RollUpPROMOApprover's type is an actor, maybe try just to RollUpPROMOApprover?

smodarressiyazdi

Sorry i think I was unclear…I have two fields..one is Actor type and one is Employee type. I've tried both the Actor and Employee.

In a change of events, I just tried submitting the LPL and got a more specific error message that saving the send notification LPL (the only change to the BC I've made) will invalidate active User Relations I've built…I'm not really sure why…

cleverly

Since this is a User Business Class, the validity of your update hinges on it being able to parse everything correctly. Any error in any part of it will invalidate the whole. Since the editor has issues with the send notification stanza still going ahead and saving the UBC will mark it is invalid.

The screenshot shows that you have a user-defined relation named (or at least beginning with) AIRPromotionsApprov [then I suspect it is cut off] on the HROrganizationUnit business class. If your UBC is invalid then it follows that this relation would no longer be valid. Once that relation is invalidating, it's theoretically possible that other configured items might no longer be valid (hence the cascade warning).

I haven't ever tried using "send notification" though I've done "send email" a lot, and the syntax looks similar.

I might suggest hardcoding an actor to be notified and get that working before introducing your variables.

Copyright © 2025 Infor. All rights reserved.