I have a task where screen level attributes are being used. I am writing a email policy when i want to fetch these screen level attributes. IS ti possible to fetch it in email policy if yes which type data element should I use?
Actually i was able to print the task level on screen attribute using the policy xpress of type UI and triggering on the Validate on Submit event for the particular task
Screen level attributes or Screen-defined logical attributes are a temporary attribute. There isn't a way to pull a Screen-defined logical attribute inside an email policy. Instead I would recommend using a Logical Attribute Handler that maps to a physical attribute or a regular user attribute to accomplish this.
For more information on LAG (Logical attribute handlers) please review the following documentation.
Logical Attribute Handlers - CA Identity Manager - 14.0 - CA Technologies Documentation
I am trying to do a Policy Xpress that get Screen Logical Attributes value, but I am not sure it is possible... I am using type UI and triggering on the Validate on Submit, but when I am going to get the value the screen logical attribute is not in the list of User Attributes... any suggestion?
Thanks a lot
As far as I remember , the screen logical attribute will not come in the list but you can manually enter the attribute as |attributeName| and set the value in the PX
Hi Gaura. I did your step by step and i can read the screen logical attribute to be printed in message defined on action rule. My question is How can i pass the to other PX that will execute with event task completed. I didn't jump between the PX's (the new defined UI PX and my task event PX) in action rule. These PX's rarely are relationship directly between them.
I wait our quickly response
You will need to make sure that the PX are executed in order.
If they are of the same type, and pointing to the same event, you can use priorities:
If they are of different types, then you need to make sure they are in order of execution.
The following diagram is the order of PX type execution
Hi Gil, i made that you suggest, maybe i didn't explain the problem correctly, i have a UI PX where i read screen logical attribute, that value is printing on screen if i set the action rule of UI PX right?, well i don't need to print the value, i need to save the value in something like variable to be read by another PX (event PX will send an email with value read). According to it i can't define a variable in UI PX to be read by the other PX because the UI PX and the event PX didn't execute in the same flow (i didn't set in action rule a jumping from UI PX to Event PX). I will upload an image to understand the logic
Question, whiy no the screen logic. It should survive for the entire lifetime of the event.
Another option is a dummy LAH, an LAH that does nothing, but the name itself is persistent. We have used it in some occasions when a screen logical was not sufficient
We used a dummy LAH as you suggested.
Retrieving data ...