Error Messages are getting cleared on submit of assignment (7.1.8)
system is displaying the error messages to the users on change of field ,but still user is able to move on to the next assignment with out correcting the messages .
In tracer , i see the messages on work page are cleared at step#4 in work-.FinishAssignment OOTB Rule as 4th condition is being failed (@determineDeferErrors(newAssignPage, myStepPage)).
Please suggest me if any configuration is required to satisfy the condition . For meanwhile we kept the same validation on post action which is duplicate effort of validating the field.
Areteans Technologies
AU
Is it a screenflow, if so please check the Start shape where there is a checkbox to validate the items only at last step of screenflow. If that is enabled, uncheck it.
Blue Rose Technologies GmbH
DE
Basically we had to start with the fresh page every time on the server side before processing the flow action submission. This way we will be able to distinguish the new errors (if any) happened during the post processing time. Without this there is no way to differentiate between the error messages set during previous submission.
Ideally server side validations has to be done once during the submission through a validation rule in the Flow action rule form (for all the input fields).
Skandiabanken
SE
Pleas elaboarate it more.
Before submitting the flow action if work page has errors then it shouldn't allow the users to proceed futther untill errors are corrected.
now it's more like duplicate efforts of calling validate rule at field level and post submission of action.
Incessant Technologies
GB
I dont think you can stop the user with the error message unless you create a validate rule on flow action or you can stop the user by making the field as required in the property form.
Blue Rose Technologies GmbH
DE
I am not able to understand your statement.
Basically if there is any error message during post processing, we don't allow the user to proceed further. This can be achieved even without a validate rule.
hexaware
IN
we are also facing similar issue , we have done all validations on click of a checkbox and displayed error messages on screen , but once we submit , as specified in above posts in step 4 of finishassignment it is clearing all the error messages , To display error messages again we have to do the same validations again in validate rule , which is duplicate.
any suggestion or resolution?
PEG
US
You can create a private checkout of the RUF determineDeferErrors; this is the RUF which is returning false when you want it to return true.
Open the XML for the RUF and find the pzInsKey. Then find and run the rule pzPrivateCheckout, supplying the pzInsKey of determineDeferErrors. Once you get the private checkout, compile the RUF but do not return it to the Library, and do not rebuild the Library.
Now you can add oLog.infoForce statements throughout the RUF, and through those you can determine exactly why the code is returning false instead of true. (You will need to recompile the RUF after every change.)