How to collect error messages from previous forms

pieterk

A Score Level 1

over 8 years ago

I have an interesting requirement. We have an application process that stretches over more than 5 user tasks in a process model. Each form needs to be filled in with the information that the consultant has at hand at that point. We dont want to have "hard validations" that block form submission in these steps but we need to show the user that there are errors but still allows for submission in order to go to the next step. After the last form we would like to show the user a view of all the errors or missing fileds from the previous 5 screens. Is there a way to collect the error messages from each screen when it is submitted so that I can show all errors in one place at the end of the process. At this stage the user will need to go back in the process to complete the missing bits before he can pass the task on to the fullfillment team.

Discussion posts and replies are publicly visible

0 sparshs over 8 years ago

you can create a cdt for showing errors but do not use appian validation on your forms rather than that use richtext field whoich will show user error string every time it is encountered . Keep your error cdt as multiple type and keep appending error string in it on submission of forms(in your form a!save you have to save these strings in your cdt). Finally on your last screen you can show user the whole cdt in a readonly grid or paging grid.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sparshs over 8 years ago

For your requirement of going back you can loop back to your task if error cdt is not empty and let user correct the bits. You can put your logic here to play around with this. Let me know if there is anything else i can help with.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ravi Roshan over 8 years ago

In case if you don't want to use a CDT, use process variable as text and multiple type and pass to each form as ac! variable and append the error text to respective ri! variable.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 pieterk
A Score Level 1
over 8 years ago

thanks, I managed to get this to work
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sikhivahans over 8 years ago

I don't think the error messages needs to be stored in PV at all and updated every time. As long as there is a expression rule that drives error message contents based on the values inputted to it, you can provide the fields in your CDT as a input to it. In the final step, in the load(), trigger the expression rule and store the contents in the local variable and use the same in the interface whenever required.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel