This query is simple enoughtselect noteId , miscMattersMainId , createdOn, createdBy , note from PLSM_note
Those are the only fields in the table and only two records in PLSM_note,
This is being executed against the pre-defined data source that comes with Appian with almost no load on the server.For reference, when I run this same query in the loud Database/MyPHPAdmin I get
Showing rows 0 - 2 (3 total, Query took 0.0003 seconds.)So what's going on as it's taking more than five minutes to complete the execution?
Discussion posts and replies are publicly visible
There is a common misconception about Appian process performance. This is mixing up low level code execution time vs. node duration time. Appian is made to scale horizontally and can run millions of process instances at the same time. An individual process or node will not be run any faster.
Keep in mind, this is about implementing a business process and assigning tasks to people. People do not know that they will get a task assigned, so they do not wait for it.
Umm, so this is the assignmentI'm not too sure how your previous comment helps solve the issue
I think the longer time is due to the assignment, the node will not stop executing until the form has been submitted.
OK. Then this node has failed. Please check the tomcat-stdout log file for any details.
Is there a specific reason to not use Appian's normal way of accessing the database?
I don't see how the system would have gotten to the "Script Task" had I not clicked the button for submit it.
I need to:A) select X items from a read only gridB) pass those values to the process modelC) delete selected items
I'm talking about the Form that you may have configured in the Query Database node as you are providing assignment for this node.
Solution to original question:
Select below highlighted option on the assignment tab
On the form, collect the records to be deleted. Pass these to the process and use the deleteRecords node to delete them.
And as I discussed in at least one other thread already with this user, there's no need to use the Query Database node in this manner at all. Query Record or Query Entity should be being called in a Script Task (or, as you suggest, on the start form) and saving their output into the process.
This solved the initial problem
Cool. But as Stefan and Mike also mentioned there is no ultimate need to use Query Database node for your use case.