STEPS FOR TESTING
1. Run a query to completion.
2. Make note of the <query_master_id>.
3. Verify the query appears correctly in previous queries.
4. Run a second query, only click on the cancel button once the query starts running.
5. Make note of the <query_master_id> for the cancelled query.
6. Go to Previous Queries and verify the first query still appears in the list of queries.
7. Open the XML messages in Previous Queries.
7. Find the 'deleteQueryMasterId' message.
8. Verify the <query_master_id> for the cancelled query is sent in the request message.
+++++++++++++++++++++++++++
Tested latest change and cancel queries is now working correctly.
STEPS FOR TESTING
1. Run a query to completion.
2. Make note of the <query_master_id>.
3. Verify the query appears correctly in previous queries.
4. Run a second query, only click on the cancel button once the query starts running.
5. Make note of the <query_master_id> for the cancelled query.
6. Go to Previous Queries and verify the first query still appears in the list of queries.
7. Open the XML messages in Previous Queries.
7. Find the 'deleteQueryMasterId' message.
8. Verify the <query_master_id> for the cancelled query is sent in the request message.
+++++++++++++++++++++++++++
Tested latest change and cancel queries is now working correctly.
Description
Run a query to completion. (Circulatory system)
Then run a longer query (20 sec or so) and cancel it quickly. (Digestive system)
The Circulatory system query will be deleted from the PQ.
This issue was marked resolved too soon. It is not working correctly. If you run two queries and cancel the second query then the first query is marked as deleted. This only happens if you stay logged in, in other words, do not log out of the Web Client in between queries.
Steps to Reproduce:
1. Run two queries, let the first query finish and verify it appears in previous queries correctly (make note of the QUERY_MASTER_ID).
2. Run a second query and as soon as it starts to run click on cancel.
3. Make note of the QUERY_MASTER_ID that is returned in the response message.
4. If Previous Queries did not refresh automatically then refresh the list.
5. Notice the 1st query you ran is no longer in the list and the one you just ran is appearing.
6. In the QT_QUERY_MASTER table you will notice the 1st query has the DELETE_FLAG set to 'Y' and has a DELETE_DATE that is after the END_DATE in the QT_QUERY_INSTANCE table.
The DELETE_FLAG and DELETE_DATE should be for the second query not the first query.
Not sure if it matters but the second query was run & cancelled within a minute of the first query finishing.
Janice Donahoe
added a comment - This issue was marked resolved too soon. It is not working correctly. If you run two queries and cancel the second query then the first query is marked as deleted. This only happens if you stay logged in, in other words, do not log out of the Web Client in between queries.
Steps to Reproduce:
1. Run two queries, let the first query finish and verify it appears in previous queries correctly (make note of the QUERY_MASTER_ID).
2. Run a second query and as soon as it starts to run click on cancel.
3. Make note of the QUERY_MASTER_ID that is returned in the response message.
4. If Previous Queries did not refresh automatically then refresh the list.
5. Notice the 1st query you ran is no longer in the list and the one you just ran is appearing.
6. In the QT_QUERY_MASTER table you will notice the 1st query has the DELETE_FLAG set to 'Y' and has a DELETE_DATE that is after the END_DATE in the QT_QUERY_INSTANCE table.
The DELETE_FLAG and DELETE_DATE should be for the second query not the first query.
Not sure if it matters but the second query was run & cancelled within a minute of the first query finishing.
Bug
Major