in one of the screen flow journey system behavior is unexpected. There are fields user has to fill on the screen, click on Next button click to go to next screen in the screen flow resetting to null/empty and UI validation is throwing error as they are mandatory fields. The values are setting to null in the clipboard.
- There is no specific logic for these fields to reset. Also no application code resetting them.
- In the tracer i could see an OOTB activity @baseclass pyDeleteDocumentPg is running when form submitted. Till the activity end there are value in the pyWorkPage. Work- FinishAssignment activity starts after finishing the pyDeleteDocumentPg activity. The properties are getting blank in the first step of this activity itself.
Is there any specific setting why properties are getting blank during the form submit? Can anyone come across this issues?
Thanks for replying. There are number of embedded sections in this screen. However i was debugging by removing one by one.
I found that there is a section having the visibility condition with client side validation checked which causing this weird behavior! I know this doesn't look like a related one, but it worked fine after deselect the client validation checkbox.
I am able to submit the flowaction without any issues.
I'm encountering the exact same issue as detailed by you, however even after clearing the client validation in two of the embedded sections, I'm still facing this issue. Was there any other actions you took to resolve this issue?
That is the only change i had done to resolve that issue. Worth to test removing the sections one by one (even the fields in case if it is a single section).
In my case there were two sections amoing 3 had client side visibility condition (an expression). Visibility condition was working fine but when the form filled (from one of those two section the otehr was hidden) andtry to submit it was clearing all the fields.
I am not sure in your case whether you have upgraded or you are facing this in an existing 7.x version. My application was in 6.3 and it has lot of custom/old controls which might also caused this issue.