AngryAppianPractice

4. lets you use logical expressions directly in the expression editor
7. this ensures that data is written to both tables at the same time, but is typically not recommended
8. information configuration for use with grids, queries, and todatasubset()
10. this is the very bottom-most and final word on the Appian Documentation page concerning the Show Sales By Region Recipe
12. determines if the field should display as potentially editable but grayed out
15. determines when the saveInto expression is evaluated
16. not a product owner
17. this object must be used when extracting data from a document
20. the final parameter after declaring any number of local variables
22. tells me who is supposed to be doing this work
23. XSD annotation for settiing a key to be automatically generated
24. drops all rows but not the table
25. a grid that prevents users from messing things up

1. for the working and the weary, whose data needs may vary, to uncover their journey's end they need but run a ____
2. parameters for this are: field, ascending
3. UPDATE TABLE users ____ name = 'Jabob' WHERE name = 'Jacob';
5. when these are used outside of an interface, all refresh properties configured using a!refreshVariable() are ignored
6. they are containers used to store and input data in an activity class
9. every object requires one of these upon creation
11. sending one of these can start a process
13. this acts as a virtual table, and you were probably asked about it even though we didn't talk about it
14. this cannot be used when the database table exceeds 2 million rows
18. this feature allows limiting visibility of incoming data, but only if data sync is turned off
19. when a product feature is slated for removal
21. the first value of a local variable