Hi ,
I am new to Appian. I have a value in the form to be input by the user .After user enters the value ,I wanted to check if the same value in one of my table column.
I have used User Input Task for creating form and using Query Database as the smart services.I have specified the below query to retrieve the value from database in Query Database Smart Services.
I am using the below flow in my process model
Thanks in Advance.
Discussion posts and replies are publicly visible
What are you going to do if the value entered by the User DOES appear in your database column? If you want this to be a validation error and route back to the 'Verify PO form' as an error for the User to resolve, then you can do this all in the same form. If not, what is the objective here?
I think you should consider using a different approach, for instance make use of an expression rule with a query database entity instead of using an SQL statement on the process model directly.
then on the process model, use the script task to call your expression rule.
Hi,
If the value exists in the database and matches same as entered by the user ,then I have a next node as inserting an approval row in Database in Approval Tbl .If it doesn't matches then insert an exception row in exception table.So after validation and verification I need to add data into respective tables.
ManuelHTG said:make use of an expression rule with a query database entity
I assume by that you really mean "an expression rule using the a!queryEntity rule, querying a Data Store Entity", but otherwise I agree.
...and what happens with the exception row? (I guess I'm trying to establish if we should implement a 'prevent' pattern rather than a 'cure' pattern!) Is there any reason why we can't simply prevent the User from entering an invalid value in the very first User Interface so that any subsequent processing can guarantee that it'll only be working with valid data?
yes, thanks
Yes,Thank you for the suggestion trying out that way to implement
As per the requirement of the process if there is no matching Po then it goes to Exception table and if it matches it has lot more processes of approval after that.