We have already mechanisms implemented to control the change of appointments like dedicatd rights for
SCD_APPOINTMENT_UNBLOCK : Unblock appointments Right SCD_APPOINTMENT_BLOCK : Block appointments Right SCD_APPOINTMENT_GRID_ENTRY_OVERWRITE : Overwrite grid entries
In addition we offer the possibility to configure a mandatory entry if an appointment is changed.
So we have already a toolset in place that could be used. A PIN input (in which device?) won't fit into our existing privilege concept - it should be checked if same goal couldn't be realized by using blocking/unblocking appointments and definition of scheduler grids.
The customer was already informed by me in SF Case 06549083 about the existing mechanisms.
Thank you Nicole.
We have already mechanisms implemented to control the change of appointments like dedicatd rights for
SCD_APPOINTMENT_UNBLOCK : Unblock appointments Right SCD_APPOINTMENT_BLOCK : Block appointments Right
SCD_APPOINTMENT_GRID_ENTRY_OVERWRITE : Overwrite grid entries
In addition we offer the possibility to configure a mandatory entry if an appointment is changed.
So we have already a toolset in place that could be used. A PIN input (in which device?) won't fit into our existing privilege concept - it should be checked if same goal couldn't be realized by using blocking/unblocking appointments and definition of scheduler grids.
Can someone please give a short explanation why this FR is rejected, thank you.