Can't close the harness when click cancel after post the value

User Experience
, ,
1

I have a field that must be post, then Run Data Transform to validate (img_1.png).

I have a button that action Cancel when clicked (img_2.png).

When i input the value to the field, then click button Cancel, the harness tab hasn’t closed (that is effected by dirty check)

How can i fix this?

ver up 8.2.2 → 8.8.1 (8.2.2 still ok)

2

HI @VanNH15: If I got this right, there is a dirty pop-up if when you click cancel after a post value action. If yes, this is expected behaviour. It it better to have the OOTB functionality to show users that the screen have some unsaved data. If you want to remove it, please see this for options.

Thanks.

3

Hi @ArulDevan

Thanks for response,

There is no dirty pop-up show on the screen, only loading screen, then i cant do any things.

To disable dirty check, i can set 「pega.u.d.gDirtyOverride = false;」in UserWorkForm. But, this is not what i expected

4

Hi @VanNH15: Thanks for clarifying. Were you able to trace and see if there are any errors in tracer?

Thanks.

5

Hi @ArulDevan,

On main screen I tried to trace when clicked the cancel button, but nothing out.

6

Hi @VanNH15: Have you checked the logs too? If you don’t see any errors in the tracer and if there is no error in logs and if you are using OOTB flow action buttons, then I suggest you to raise a support ticket in my support portal.

Thanks.

7

@ArulDevan I am also facing similar issue , after posting values from the input fields in UI , the cancel button is not working and I am unable to trace it as well.

8

@VanNH15 can you confirm if your issue is now resolved?

Also be aware of product changes as described in this post Dirty Check modal Save and Discard buttons don’t work as expected when Optional flow action launched

If your question is now solved could you mark your own reply as ‘Accept Solution’ so that it will help future forum users?

9

@KiranmaiK please have a look at the latest Dirty Dialog - Troubleshooting Support Document which may help you analyse your issue.

If this does not resolve it, please can you raise a support incident via the MSP?

10

@NikitaS16596315 I change the post → refesh this section, that worked.

11

Yes, thanks for helping, the dirty check post helped a lot.

12

I have the similar issue in my application now and this solution is also not helping me. Do we have any other approach to resolve this issue?