Appointment - View Location Resources for Ungrouped Resources

This feature provides you the option of viewing your Location Resources directly in Location Resource setups where you do not use any Grouped Resources.  Previously, in setups that did not take advantage of the Grouped Resources concept, your Location Resources would be grouped into Ungrouped Resource groups - to view the Location Resources you had to first select the group and then select the View Group Resources option to view the actual Location Resources.  With this feature, when running Scheduling Appointments - Show Options, you can view your Ungrouped Location Resources directly without having to first drill into the View Group Resources to see the Location Resources. 

In the example below, no Grouped Resources have been configured, and the property - glog.appointment.showOptions.displayLocationResources has been set to true - in this setup, as shown, you have visibility to the Location Resources without having to select a group and then select the View Group Resources option to view the Location Resources in the selected group.

Ungrouped Resources Location Resources shown

In the example below, the property is set to the default value of false - the previous behavior.  In this case, even though the Location Resources are not grouped, you must select a group and then select View Group Resources to see the Location Resources.

Previous behavior - View Group Resources required to see Location Resources

This feature eliminates navigation clicks in Appointment Management configurations where Resources Groups are not used.

Steps to Enable

To enable the new behavior, you will need to set the property - glog.appointment.showOptions.displayLocationResources - to true to take advantage of this feature - the default is false.

This page is accessed via Configuration and Administration > Property Management > Property Sets.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Tips And Considerations

Note, that the feature will not work in mixed grouped and ungrouped setups - if there are mixed grouped and ungrouped resources the previous behavior will remain.