Question
Pegasystems Inc.
US
Last activity: 13 Dec 2021 7:41 EST
SLA omits only 1 of many properties from correspondence. Works in email shape.
I have set a templated email with inserted property references. One property, OperatorID.pyFirstName, is not populated when correspondence is sent. This is set in pages and classes as OperatorID Data-Admin-Operator-ID. The other properties on same correspondence work fine. If I use it elsewhere in an email step/shape all properties work.
I have tried with other correspondence rules and it seems it is any correspondence, only this property, only when called from SLA.
Are there any ideas why this behaves this way or where to look or test?
Lventur
IN
@AlexanderNelson
When SLA is processing request in back-end, OperatorID page context will not be there. SLA session will have only pxRequestor page context with system information.
Because of this only value is coming blank when mail is getting triggered from SLA.
OperatorID page will be avail only for browser requestor sessions alone.
Pegasystems Inc.
US
This makes sense. I noticed the property was not available on the clipboard. So the SLA runs in separate context. Also, reversing the issue, the property I used within the context of the case is unavailable when viewing it in the template.
Knowing this just running a case with a suitable property that is in case context and triggering the SLA sends the message perfectly. Just can't see it in both template and received email at the same time.
Here's the property I used in the case context for future reference- .pyWorkParty(Owner).pyFirstName Data-Party-Operator
Thanks!