2024_06: White glove Test the Sim UI interface

lzim / teampsd

Team PSD is using GitHub, R and RMarkdown as part of our free and open science workflow.

GNU General Public License v3.0

9 stars 23 forks source link

2024_06: White glove Test the Sim UI interface #3165

Open jamesmrollins opened 1 month ago

jamesmrollins commented 1 month ago

Context

Sim UI is updated in Test Slow and declared "ready" by DEV team.

Acceptance Criteria

[x] System Stories (Causal Loop Diagrams) are screen resolution issues resolved.
[x] Decision Meters retain values after window close.
[ ] Directives Table up to date.
[x] Team dropdowns working properly
[x] MTL Reports Icon hidden
[ ] SME setup functionality (7/1)
[ ] Directives Dashboard and functionality (6/21)
[x] Dynamic Dashboard alignment issues resolved

Notes

Supported Screen Sizes for responsive sizing: 3200,2560,1920,1800,1780,1700,1600,1560,1400,1360,1280,1200,1180,1100,1024

jamesmrollins commented 1 month ago

Hide MTL Reports icons

tejaspesquare commented 1 month ago

@jamesmrollins - This is resolved & available to test on Dev environment.

jamesmrollins commented 4 weeks ago

@tejaspesquare - the above was not migrated to Test environment:

jamesmrollins commented 4 weeks ago

@tejaspesquare

MM Model Calling Variables that do not exist in the model.

MM_PROD.ctx Context File needs to be updated

jamesmrollins commented 4 weeks ago

@tejaspesquare

Psychotherapy Causal Loop Diagram opens incorrectly

The lower sizing icon is hidden below browser window, so user cannot grab it.
Text is too small.
Display size 1920 X 1080

Expand viewable area of Team Care Story

Increase font size and improve text centering (see highlights) in Team Flow Story

@lijenn @ljmoody do these dropdowns need to be relabeled "Causal Stories" or "Stories?"

lzim commented 4 weeks ago

wk5 2024_05 #systems_sme_workflow @lzim @dlkibbe

@jamesmrollins - Unclear about the only 2 of 8 requirements tested. Some seem to say 05/31. Our understanding was that we would have the MTL 3.7 Blue Live Consults ready to set up this week for scheduling. Please advise on timeline to completion.

FYI: @dlounsbu

jamesmrollins commented 4 weeks ago

@lzim

White Glove Testing scheduled today. I am slowing working my way through (started it yesterday, actually).
5/31 dates for Directives dashboard maintenance panel and SME maintenance feature. (this should not affect blue team setup)
Once complete, Directives Dashboard complete, we can populate with content.
Regarding the "Feedback Loops" label in the dropdown above, do you want that renamed "Stories" or "Causal Stories" or something else?

lzim commented 4 weeks ago

@jamesmrollins - Unfortunately, I'm understanding this response re: _MTL Blue 3.7 Live Consult_ prep planned for this week. Are you saying we will not be done with testing until end of week?

Please keep all of #systems_sme_worklow in the loop.

FYI: @dlkibbe @dlounsbu

jamesmrollins commented 4 weeks ago

FYI: @lijenn @ljmoody @dlkibbe @dlounsbu @lzim

Regarding Testing

[ ] We have some set up we have to perform by-hand once PROD is brought fully to 3.7. This includes the creation of group folders for all team data files, and moving legacy team data to the folders. This will not affect any work setting up new groups.
[ ] We are attempting to clear remaining bugs so we can start that work tomorrow (5/28) in prod. We will also start updating the consult manual.

jamesmrollins commented 4 weeks ago

@tejaspesquare

Please modify the following popup as shown.

[ ] Extend popup size at the bottom to include the lower part of the Month 4, 5 and 6 tables in Medication Management.

tejaspesquare commented 4 weeks ago

Hello @jamesmrollins - Episodes of Care -Extend popup size: This is resolved & available to test on Test-Slow.

ljmoody commented 3 weeks ago

@jamesmrollins, just saw your comment today re:

@lijenn @ljmoody do these dropdowns need to be relabeled "Causal Stories" or "Stories?"

To my knowledge, no, these do not need to be renamed. However, I've seen/heard the following different references for same, and wondered if there are correct/incorrect ways in which we refer to them. We may need clarification from @lzim if there is one (or more) specific ways for she'd like to refer to them via Sim UI drop-downs, documentation, blue bar headings, etc.

Here's a list of possibilities - I've bolded the ones that are currently used in Sim UI menus, blue bar headings, and Consult Manual documentation:

[ ] causal loops
[ ] feedback loops
[ ] causal loop diagrams
[ ] system stories
[ ] causal stories
[ ] stories

fyi @lijenn

lzim commented 2 weeks ago

@ljmoody - I believe we have used "feedback stories" and "systems stories" and "causal feedback." Let's leave this standardization card as lower priority until we are sure MTL 3.7 Blue consults are prepared in PROD without issues.