Table Show details - Expand all creates transaction ID error

General
, , , ,
1

Hi All,

We have a weird error with the following configuration:

There is a section with a table where in the Operations tab the Show details option is selected (see screenshot). The requirement is to have all rows expanded therefore the Expand all was checked.

However, in this situation if the case is closed (either closing the window or navigating back to the homepage), when the assignment is relaunched, the case is not opening. There are no errors in the tracer only in the logs “ERROR: posted transaction id ‘xxx’ for frame ‘pyWorkPage’ DOES NOT match record ‘yyy’”

If the Expand all is unchecked everything works fine.

The flow action called in show details does not have any pre or post processing actions, no validations just the default settings.

For the time being we solved the expanding by setting the pyExpanded in a pre DT.

The question is if this is a known issue or are we doing something wrong?

table setting.png
table setting.png677×639 28.9 KB

Error message.png

PS.: Using Pega 24.1 with Theme Cosmos

2

@Romero Borze To resolve the error ‘posted transaction id for frame ‘pyWorkPage’ DOES NOT match record’, you can try the following steps. Please note that these are general solutions and the exact solution may depend on the specific configuration of your Pega application. It is recommended to log a support incident if you need this looked at by the Global Client Support team. Additionally, you may want to refer to the support document on troubleshooting stale work, validation errors, and work processing failures caused by Transaction ID mismatch for a more in-depth analysis of your issue.

ERROR: posted transaction id for frame ‘pyWorkPage’ DOES NOT match record

Troubleshooting stale work, validation errors, and work processing failures caused by Transaction ID mismatch

When you log the support incident can you please provide a reply here with the INC id so that we can help track it?