https://academy.appian.com/learn/course/975/play/36425/create-a-query-rule
I watched this video but I can't find the "Query Rules" option under "New." What am I missing? Thanks
Discussion posts and replies are publicly visible
Prateek is correct. Anyway you wouldn't want to create a query rule anymore - Query Entity rules (created within an expression rule generally) can do anything Query Rules would do plus more - and are a ton more flexible all-around.
Okay, sounds good. I created my query rule for "status" (shown below). This seems to be working correctly. Do you guys know how to use this to create the filter? Thank you.
What "filter" are you trying to create & where?
I would like to be able to select from the three drop-downs show belown (Status, LMI, Structure Type) and have the form sent to the relevant applicants who are correlated with the values I select. I heard I may need to use the query entity I made to do this, but I'm not sure how.
Hi Mike,There is one case where Query Entity seems incompatible as compared to Query Rule and that is when @Transient annotation is used in XSD because queryEntity fails when an XSD has a field marked as @Transient as described in below KB article.
https://community.appian.com/support/w/kb/659/kb-1404-queryentity-fails-when-an-xsd-has-a-field-marked-as-transient
Thanks
Out of curiosity, what use case would require @Transient in the CDT? I've never run across this.
You would want to make your Query Entity rule accept inputs corresponding to all of those values, and preferably, query correctly whether or not each value is passed in (note that over-filtering may result in a returned list of zero people, depending on the particular data setup). Assuming that you can derive Appian usernames from the result of the query, you could probably have your form map an array of usernames to a Rule Input when a submit button is clicked - and then pass that array out to your process model, where you could then call a subprocess for each user and assign the task therein to that user. It's a complex use case and a lot depends on your particular implementation and requirements.
Suppose you have a CDT having a field with @Transient annotation and in the process flow you are doing some calculation to get a result and will save this result in this field so that that calculated data can remain inside CDT but you don't require this calculated data to be saved in database while storing CDT to database for some security reasons, in this case having @Transient annotation on a field will serve the purpose.
Hope this helps!!
Ah, easy as pie. Thank you, Mike
Thanks for the explanation - luckily as far as Appian is concerned it seems like there are various options for other implementations that would handle that; i've personally never needed this functionality myself though.
I have a related question - are you able to answer this?
I am not able to invoke the Expression Rule / Query Rule for my summary view.
1. I created the Expression Rule using the query editor and tested it (called TA_GetAircraftById)
=> tests fine using id "1"
2. I created the TA_AircraftSummaryView
3. I test the AircraftSummaryView and try to use the expression "rule!TA_GetAircraftById(1)" for the test data (SEE NULL RESULTS)
Any ideas??
I've tried looking at the summary view for the record and it doesn't work either.