Hello. I am new to programming. I have created a form (shown below) that I want sent to applicants. I have three drop-down lists: Status, LMI, and Structure Type. I want to design the form so that these lists will automatically filter a set of applicants according to their Status, LMI, and Structure Type. What are the steps I need to take to have my drop-down menus filter applicants by these three types? Thank you.
Discussion posts and replies are publicly visible
Is not the table that BS_MS_STATUS_DSE is pointing to the source of your Test Applicants? If so, then when you run this expression rule it should return the subset of Applicants that correlate wit the values you've set for 'status', 'lmi' and 'struictureType'
I don't believe it is. Below is the BS_MS_STATUS_DSE constant, as well as the list of test users I have made. How can I have the constant point to these test users? Thanks.
Ah! Ok, so there's a definite disconnect here. the Constant is acting as a "pointer" to a Data Store Entity: that is, a TABLE (or a VIEW) is a DATABASE. So your Query Entity is essentially assembling (behind the scenes) a SQL statement to select data from that tbale. SO: you need your Applicants to have entries in that table.
It looks like you're thinking you can query the User objects in Appian (this sort of is possible but I strongly recommend you DON'T do it that way). SO: for every Applicant in the list in your second screenshot you'll need a row in the database table, with the UserId as they correlating value (the value that is the same in the DB as it is in Appian). In effect the UserId in the database is acting as a virtual "foreign key" to the User Object in Appian. Each row in your table - an individual Applicant - should have values for 'status', 'lmi' and 'struictureType'. Your query entity will then return all qualifying rows, you can then extract the UserId and use THAT value to get the User's email address or assign a Task or however you decide to communicate with the User as an Applicant.
Okay, thank you, Stewart. I appreciate your help
Hi, Stewart. It worked as you suggested. Thank you
You're welcome. Note: this is the beginning of the journey. I guess you'' now need to design and implement a solution for managing the content of the table in the database and aligning that with the User accounts in Appian that represent the role of 'Applicant'. Good luck!