Open Assignment Issue
Hello All,
i want to open a subcase in a new Tab. I have configured a button on parentcase with a click event and several actions!
Action 1:
First i run an activity (see screen) which calls "pxAddChildWork" and i also use an Obj-Browse for an AssignmentList where i am getting the ".pxRefObjectKey". Afterwards i am storing the data key "AssigmentList.pxResults(1).pzInsKey" into a normal property for example .Placeholder.
See Activity:
Action 2:
Refresh Current Harness
Action 3:
Open Assignment i want to use .Placeholder as Child Assignment Key.
If i am clicking the button the new tab will be initiated with the subcase but everytime it opens previous case!
Hello All,
i want to open a subcase in a new Tab. I have configured a button on parentcase with a click event and several actions!
Action 1:
First i run an activity (see screen) which calls "pxAddChildWork" and i also use an Obj-Browse for an AssignmentList where i am getting the ".pxRefObjectKey". Afterwards i am storing the data key "AssigmentList.pxResults(1).pzInsKey" into a normal property for example .Placeholder.
See Activity:
Action 2:
Refresh Current Harness
Action 3:
Open Assignment i want to use .Placeholder as Child Assignment Key.
If i am clicking the button the new tab will be initiated with the subcase but everytime it opens previous case!
For Example Current Subcase FC100, after pressing button the current subcase has to be FC101 but Open Assignment opens FC100 and so on...
I have tried to use a placeholder property for child assignment key where i remove their value at first step during processing the button action but without success.
maybe someboday has an advise?
thanks a lot (Pega 7.1.7)
***Updated by Moderator: Maryrita. Moved from Customer Service to Product Support***
Pegasystems Inc.
IN
Could you please run tracer or fiddler and verify the "key" value for "Open Assignment" action, whether its for FC101 or FC100(as per your example)
Pegasystems Inc.
IN
Did you check local.childCaseID is changing every time?
Can you send the screen shot of Data transform?
DB
DE
every run the key will be renewed with the new key. to be clear i set .pyNote, .Placeholder to "" that no former value is inside.
DB
DE
UPDATE:
So at starting point pyWorkPage holds the values from the previous run which will be updated within the Data transform.
curious is the refresh harness, which you can see above as action event betwenn data transform and open assignment. without it i get always the error message missing child assignment key but you can see that a new FC will be initiated in the background, strange...
it seems that "open assignment" will be executed even though the activity should be called first....(see attachment)
Pegasystems Inc.
US
Hello,
To confirm... if you remove the other steps, each of the three button actions works as you expect with a valid hardcoded value? I will assume yes. If that's the case, I would want to look at a Fiddler trace. My theory is that the activity doesn't finish running before the later actions are called. That's not my area of expertise, but I believe there is no guarantee that the actions will wait before calling the next in the list. Fiddler would confirm this. If the activity is what nulls out the properties used by the Refresh-CurrentHarness and Open Assignment actions, that could account for it. If that's not the case, the next thing I'd look at is what the client sends up to the server for the later actions. My guess is that it's the old value and not a property reference to that value. That could be because the underlying javascript is based on values that are set when the section is first loaded (i.e. before you ever clicked the button), so the changes that the activity does don't apply to those actions. Fiddler should help you see that as well. So basically, I'd fire up Fiddler and poke around.
Thanks,
Mike
DB
DE
Hi Thanks,
after investigating deeper into the logic i found out that there is some activity which is actually responsible for this strange behaviour. So i have to find a way to solve this internally.
thanks a lot for the support so far :)