Security attribute name: “Allow appointment creation when shcedule is blocked”
After upgrading to Version 11, we have noticed that one of the appointment block-related security attributes control behavior has changed.
In Version 10, users were allowed to make modifications (ex. update visit status) to existing appointments behind a block. Users were not allowed to make any new appointments when the there is a block unless the attribute mentioned above is given.
In Version 11, users are no longer allowed to make modifications to existing appointments behind a block unless the attribute above is given, which then also gives them the ability to make new appointments when there is a block.
This problem was discovered when one of our doctors called out and the office manager placed a block to prevent any new appointments being created. She instructed one of her call center staff to reach the patients on the schedule to cancel/reschedule their appointments - the call center staff was not able to make updates to the visit status (Appointment conflicts with a block //blockname//. Permission denied.) after speaking with the patient.
The new control behavior is identical in EXE and browser. Has anyone in an enterprise environment encounter this? How did you work around it?