Split For Each Issue in constellation

General
, , ,
1

Hi,

Facing issue with updating the case from split for each shape.

As part of POC application build on Constellation UI , Used split for each shape to get approval /reject from two different users, while approving, User select the approve status and comments, then click on submit, but values are not updating into case of current page index in the page list .

Steps to followed:

1.Created Case Type and populated routing information to Page list

  1. Used Split for each on Page list.

  2. Created Flow and views in the data class (Page list inherited from Data class)

Flow action and View created manually.

  1. Case created and flow split in to two subprocess and waiting for approval.

  2. Approval (1), Subprocess opened and approved by user, while approving, user selected approve status and comments,

  3. Subprocess completed but the user entered values not saved in the respective page list were spun off the case.(No locking issue observed , maintained optimistic lock)

Observation:

On Submit or Save, Update case DX API is getting triggered, which has page instructions and required values that selected by user.

During the save, the patch Api was triggered

DXAPI PATCH: /application/v2/assignments/{assignmentID}/actions/{actionID}/save

Request from Service monitor-

{“content”:{},“pageInstructions”:[{“content”:{“ApproveStatus”:“Approve”},“target”:“.Approvals”,“listIndex”:1,“instruction”:“UPDATE”}]}

DX API Logs

{“pageInstructions”: [{“pxObjClass”:“Code-MergeInstructions”,“listIndex”:“1”,“instruction”:“UPDATE”,“content”: {“ApproveStatus”:“Approve”},“target”:”.Approvals”}],“additionalContent”:{},“content”:{}}

Respsonse Body –

Approvals Embedded object in response body json doesn’t have latest values.

Note : Did tested in the theme cosmos (tradition UI) based application, with same steps everything looks good .

Looking forward help if something missing in constellation-based application

Pega Version –

Pega 23.1

2

@Bomma Srinivas

I’m also facing the same issue with the approval process in the lab instance. I think it could be a product issue. Can you please create a INC ticket?

3

@RameshSangili

Hi Ramesh , thanks for your reply ,

I don’t have privilege to raise INC incident as it is found in the practice/personal vm instance .

is there anyway to get a help ?

4

@Bomma Srinivas @RameshSangili can you check if the below Support Document might be relevant to your scenarios?

SLA failures in Split-for-Each flow due to assignments incorrectly marked as corrupt

5

@MarijeSchillern

the above mentioned article is not relaxant and use case was not related to SLA , its issue with processing of sub process assignments and data is not updating to case .

6

@Bomma Srinivas we will need you to raise this as an INC (unless @RameshSangili already has a ticket open? If so, can you please reply with the INC id here so we can link it?)

I did not understand your comment that you “… don’t have privilege to raise INC incident as it is found in the practice/personal vm instance”

Your organization has several Support Admins who can grant you the necessary General Support Role as per Managing support contacts processes How to get support.

Are you saying that you are unable to replicate the problem on an Enterprise Edition Pega application?

7

Below Root cause analysis might help:

When trace the Pega DXI API, found the svcoutput Page error after Click on Save /Submit the flow action.

The flow and flow action created in the data class to spin off the flow by using split-For-Each.

When Save/Submit, the DXAPI is trying to find at the Flow action name at the work class. so, the API is set the pystatus of svcoutput is set to **“FlowAction- Not found “**hence the Page instructions request not performed.

No error thrown by Pega on user screen.

Work around:

Create a Flow action in work class with same name used in the sub process.

It is working as expected.

8

@Bomma Srinivas we will need you to raise this as an INC (unless @RameshSangili already has a ticket open? If so, can you please reply with the INC id here so we can link it?)

I did not understand your comment that you “… don’t have privilege to raise INC incident as it is found in the practice/personal vm instance”

Your organization has several Support Admins who can grant you the necessary General Support Role as per Managing support contacts processes How to get support.

Are you saying that you are unable to replicate the problem on an Enterprise Edition Pega application?