1.7 Alpha - misleading data on Schedule & Worklist View edit screen
When you edit a schedule view and press the Test button to get to the expression test window, you get a cheat sheet of the what can go in the expression. Some of the description entries are unhelpful. Can I suggest the following replacements:
| act.description | Appointment Notes |
| act.status | Status code (eg PENDING) |
| act.statusName | Status (eg Pending) |
| act.reason | Reason code (eg HIT_BY_CAR) |
| act.reasonName | Reason (eg Hit by Car) |
| customer.name | Name of Customer (eg Smith,Fred) |
| patient.name | Name of Patient |
| clinician.name | Name of Clinician |
| schedule.name | Name of the schedule |
| scheduleType.name | Appointment Type |
| arrivalTime |
Time arrived, ie check-in time (eg Sat Jul 27 10:15:47 EST 2013) empty string if not checked-in yet use date:format functions to format, eg date:formatDateTime(openvpms:get(.,'arrivalTime'),'short') yields 27/7/13 10:16 AM |
| waiting | Time as '(h:mm)' since check-in, empty string if not checked-in yet |
For the Work List view, the table is as follows:
| act.description | Task Notes |
| act.status | Status code (eg PENDING) |
| act.statusName | Status (eg Pending) |
| act.reason | [can be used but always empty] |
| act.reasonName | [can be used but always empty] |
| customer.name | Name of Customer (eg Smith,Fred) |
| patient.name | Name of Patient |
| clinician.name | Name of Clinician |
| schedule.name | Name of the work list |
| scheduleType.name | Task Type |
| waiting | [can be used but always empty] |
regards, Tim G
Re: 1.7 Alpha - misleading data on Schedule & Worklist View ...
The expression properties are values you can use to test the expression against rather than a cheat sheet. That said, a cheat sheet might be useful.
Can you stick this in a JIRA so it doesn't get lost?
Thanks,
-Tim
Re: 1.7 Alpha - misleading data on Schedule & Worklist View ...
Tim A - before I create the Jira, a question: if at the time you built the Test window facility, if you had a good help system as we do now, would you have done it the way you did?
If I ruled the world, given that we now have a good help facility, I would make the test button on the Edit screen run a test and display OK or 'Expansion Failed', and dispense with the Test window.
Hence, I am suggesting that the Jira says 'delete the test window since we don't need its advisory information because this is available via the CSH, and just have the test button check the expansion with an OK/Failed message [or perhaps OK/Failed - Press F1 for help] '
rather than the Jira saying 'adjust the advisory information ....'.
Regards, Tim G
Re: 1.7 Alpha - misleading data on Schedule & Worklist View ...
One advantage of the Test button is that it displays what the expression will render.
So you don't need to switch back to the schedule view to see if the expression works.
So I'm happy to get rid of the Test dialog popup, but I think the Test button needs to be retained, but display the result of the expression.
So there will need to be sensible defaults to test against.
-Tim A