Posted: 15 Nov 2016 23:51 EST Last activity: 18 Jul 2017 20:38 EDT
Is this a bug in PEGA?
CMIIW: First I need to explain my problem/bug.
In my case, I make a rules condition to return true/false depends on, if there's already exist same CreateOperatorName. (ex: if I login as user@pega and start a new case, but there's already exist data with the same operatorID from D_ListPage. It will return false and vice-versa).
Next, when it was return as true then I can go to next stage and save the data with my current operatorID.
If I start a new case again, then I can't proceed to the next stage because of the rules condition. (But because of the bug, it can continue to next stage)
So, the bug is:
The D_ListPage isn't updated (I already check it from repeating grid, the last data that should've been inserted is not there)
But when I run another browser and login as admin/developer, open the data explorer and check the last records. The last data is exist.
After that, I re-loginuser@pega, run a new case. The data is updated.
I wonder if this occured because of the operator ID? Portal? Access Group?
The portal for user is customized, but after this bug I've tried to change to default. Unfortunately, it still doesn't work. (FYI: there's no problem of the validation rules condition)
Please let me know if there's any solution for this.
Well I don't understand your requirement and the implementation clearly. But this looks like you have to configure the Refresh strategy of the said Data Page to suit your requirement.
To check if this really is the issue, enable 'Refresh per interaction' in the Data Page and run your functionality. If everything is fine, you can choose to leave this enabled (not encouraged though) or to configure the data page as appropriate.
I need the validation works correctly without having the user re-login like that and thanks for your suggestion, I've enabled my D_PageList refresh strategy to reload once per interaction and it works. "Not encouraged though", could you enlighten me what do you mean by that?
Enabling "Reload once per interaction" essentially means that the other Reload configurations will be ignored. Say, you configured the data page to reload every hour. Now if you have "Reload once per interaction" enabled, it'll be reloaded on your next interaction i.e., irrespective of whether your Data Page is stale or not.
Ideally this is not recommended unless the content in your data page changes frequently.