New Simple Temporal Query mode (WEBCLIENT-237)

[WEBCLIENT-244] Clear doesn't reset the tutorial in the new temporal query UI Created: 29/Mar/18  Updated: 10/Apr/18  Resolved: 10/Apr/18

Status: Resolved
Project: i2b2 Web Client
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7.10

Type: Sub-Task Priority: Major
Reporter: Janice Donahoe Assignee: Janice Donahoe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Developer Notes: These files are changed to fix this issue
1. CRC_view_QryTool.js
2. CRC_ctrlr_QryTool.js

Web Client File/s Modified:
js-i2b2 \ Cells \ CRC
Participant/s:

 Description   
Temporal queries are clearing correctly when you click on the Clear button except for the tutorial in the new simple temporal query UI. If you have the tutorial open when you clear the query and then go back to start a new one the tutorial will be open at the point where you left off.

When clicking on Clear, the entire Query Tool view should reset to the default, this includes any tutorials that may be open.

STEPS TO REPRODUCE:

1. In Query Tool view at Query Timing select Temporal Query: Define sequence of Events
2. Select Turn On Tutorial
3. Go through the first few steps of the tutorial. Adding concepts.
4. Click on Clear.
5. Your query will be cleared and the Query Tool view will be reset to the default settings. (Timing = Non-Temporal Query: Treat Independently)
6. Change Query Timing back to Temporal Query: Define sequence of Events
7. Notice the Tutorial is already turned on and is at the same step you were at when you clicked on Clear.


 Comments   
Comment by Taowei David Wang [ 29/Mar/18 ]
The changes make sure that when user "clears" the query while the Simple Temporal Query Tutorial is in progress, the tutorial resets correctly.

The reset includes the tutorial states, and tutorial UI, and any other UI artifacts that impact the both the traditional and the simple query UI.
Comment by Janice Donahoe [ 10/Apr/18 ]
Tested and the issue has been fixed.
Generated at Thu Sep 19 02:00:45 UTC 2024 using Jira 8.20.11#820011-sha1:0629dd8d260e3954ece49053e565d01dabe11609.