Referencing pyUserIdentifier in Cell Default
Hello,
I am trying to default a text entry field to the pyUserIdentifier value. However, when I do this, the text box appears with the actual text "pyUserIdentifier" in it, instead of the user's ID. What am I doing wrong?
In the Section, for the text box, the Cell Properties default I simply put in
pyUserIdentifier
What is the proper syntax for doing this, as a reference to that value, not the actual word "pyUserIdentifier"?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Updated: 25 Mar 2015 10:49 EDT
Pegasystems Inc.
GB
I think the value will be blank because pyUserIdentifier is not on pyWorkPage, and you need to get it from a different page on the clipboard.
E.g. I assume what you are trying to get is the property:
OperatorID.pyUserIdentifier
If so then you could use an expression to get the value... something like:
@(Pega-ProCom:RuleManagement).getPropertyValue(OperatorID, pyUserIdentifier)
Runtime...
Pegasystems
US
Hi Jim,
You might see if a pre-activity (see “actions” tab on flow action rule) would help you here. You may want your activity to see whether a value has already been given for your property, and if not, it could put the value of pyUserIdentifier in. Or . . . you could just try adding a dot to what you already have and see if that works. /Eric
Centene
US
Thanks Eric (btw, I can reply now, yay!)
Putting a dot in front of the cell default just put a . in the text that appears.
Adding an Activity to the Flow action has no impact. The box still shows up blank.
Pegasystems
US
Hmmm. If activity doesn’t make box show the data, check these things:
1) Use tracer to make sure activity is being run.
2) Look at the page contents in tracer to make sure you see no data before the property-set and yes-data after the property-set
3) Look at your design view for the cell and make sure it is really binding the same property to the cell as the property your activity is setting
If none of that pans out, turn on all event types in your tracer, and use binary-search to be able to narrow down “the data is present here” and “the data is gone here”. /Eric
Accepted Solution
Updated: 25 Mar 2015 10:49 EDT
Pegasystems Inc.
GB
I think the value will be blank because pyUserIdentifier is not on pyWorkPage, and you need to get it from a different page on the clipboard.
E.g. I assume what you are trying to get is the property:
OperatorID.pyUserIdentifier
If so then you could use an expression to get the value... something like:
@(Pega-ProCom:RuleManagement).getPropertyValue(OperatorID, pyUserIdentifier)
Runtime...
Updated: 25 Mar 2015 10:58 EDT
Pegasystems Inc.
GB
Actually, you can probably just reference OperatorID.pyUserIdentifier I thought I had tried this first and couldn't save the section, but seems to work now.
Pegasystems Inc.
CA
Marc Alderman have you tested the output of that? While the syntax saves, I'm curious if it shows up as the operator ID, or the literal text "OperatorID.pyUserIdentifier”. If not the literal text, that is a recent and welcome improvement from what I've experienced (curious if all controls work the same in this respect).
Pegasystems Inc.
US
It's been awhile, but I know that I used the OperatorID.pyUserIdentifier with no problem in some of the Pega 7 development I worked on a few months back.
Pegasystems Inc.
GB
Ben Baril yes I tested OperatorID.pyUserIdentifier in 7.1.7 and it worked (same result as the runtime screenshot in the previous reply).
Pegasystems
US
>>> When I click that "Tracer" link at the bottom of the screen in Designer Studio, absolutely nothing happens.
Perhaps your browser is blocking popups ? If that’s not it, check the pega log file for errors commensurate with your clicking the tracer link. /Eric