Hi Jamie -
The way the built-in validation works is that whatever the commit action is at the end of your script, in your case the screen at the very end with the "BU" action, it does everything up until that very last screen with the "BU". If you are getting that little warning pop-up that means within your last screen where the "BU" action is, you are also updating fields at the same time. Because the validation essentially doesn't perform that last screen, any of the fields being updated on that same screen will not get checked by the validation, but all of the previous fields will. So the validation will work, but if there are issues with the fields within that last screen where the "BU" also happens, those will not be checked by the validation.
What I usually make sure I do to avoid this little warning is that I make sure the save "BU" action is completely by itself and that I'm not updating any fields at the same time. So in your MM01 type of example, whatever last view you are on and whatever last field you change, instead of hitting Save on that view, I would go to another view, for example a previous view, and then hit Save by itself.
Thank you!
------------------------------
JENNIFER HWANG | SE
Winshuttle North America
------------------------------
Original Message:
Sent: 02-12-2020 12:41
From: Jamie Borja
Subject: Script Validate Message "Will not work as expected..."
When I validate a script, whereby the last command is "BU" save for MM01-Create Material Master Record, I get a message "Validation will not work as expected because the last screen in the script contains upload fields. Do you want to continue?". When I click YES, the validation satisfies the check of the input fields alright, so I was curious if there's a line I could add to the bottom of the mapping to avoid this pop-up message, so when I click 'validate' it simply starts validating?
------------------------------
Jamie Borja | Sr. Project Manager
Refresco Beverages North America, Inc. | 8133131846
------------------------------