Release Date

July 11th 2023

Important

Lumary Compatibility: This version of the AU Healthcare Package is compatible with the following Lumary packages. These Lumary packages must be installed prior to updating the AU Healthcare Package.

Contact Lumary for the following package upgrades.

• Lumary: 20.3.9 or greater 

• Enrite Services: 1.307

Skedulo Compatibility: This version of the AU Healthcare Package is compatible with the following Skedulo packages. This version of the Skedulo Package must be installed prior to updating the AU Healthcare Package. Any features relating to the job allocation process will not be applicable to the Job Allocation Screens used with any Award Integration.

• Skedulo: 102.56 or greater

What’s New 

Time of the day suggestion

• Based on the day and time defined on the service item, the matching Services or related Service Agreement Items will be suggested to the schedulers:
  • The matching Services or related Service Agreement Items will be grouped and positioned on the top with a prefix green icon.
  • The Services or related Service Agreement Items that do not match the time will be grouped and descended to the bottom with a prefix red icon.

• When the system identifies more than one time of the day segment (e.g: when a scheduling job duration covers both a Weekday Daytime and Weekday Evening), a message will appear suggesting the schedulers to select the most compliant service or breakdown the line item.

 

• As this is a soft suggestion feature, schedulers can still select any option, ignoring what is being suggested. Current time of the day check upon creation remains unchanged and does not interfere with this new feature.
• To enable this:
  • Custom Setting / Skedulo Config / Enable_Suggesting_Warning_TimeOfDay = True

Resource auto deallocation when overlapping approved unavailability

• When jobs are created as recurring or via the replication process and allocated to a resource which has an approved unavailability that overlaps with the job allocation’s time, these jobs will automatically deallocate the resource and change the job’s status to “pending allocation”.
• Feature scope:
  • The trigger is functional on Scheduling Console, Resource Roster and Roster Management when new jobs are created or replicated, and have a resource selected for allocation by the time of job creation. (assumably, most schedulers would be unaware of the resources' unavailability in this scenario) 
  • The trigger is NOT functional when jobs are updated from edit/allocate screen. (assumably, schedulers should have been presented with the unavailable resources and the reasons, hence the allocation was intentional in this scenario)
• Note:
  • This feature is always activated as soon as installing this new version of the package.

Resource allocation message

• A warning message is displayed on the job creation window to advise the scheduler of the selected resource will bypass allocation checks for availability.
• The message is visible when the allocated resource is predetermined prior to hitting create job on Scheduling Console, Resource Roster, Roster Management, Resource Calendar.

Allocated Resources showing indicators and availability information

• On the Allocated Resources section of the job edit / allocation window, the resources that have been allocated to the jobs will now show:
  • Account inclusion indicator (yellow star)
  • Unavailable reasons

Notes:

• This new feature might not be available in case the client’s org is integrated with an Award Interpreter package and is using its custom job allocation. This gap will be addressed in the upcoming Award Interpreter roadmap.

Job Allocation respects location inclusions and exclusions

• Location Exclusion:
  • Available Resources: in order for a resource to be considered available for the job, they now must not be excluded by the location.
  • Unavailable Resources: “Location excluded” is appended as a new unavailable reason.
• Location Inclusion:
  • When a resource is included by the location, regardless whether they are appearing on available or unavailable resource list, a new indicator (yellow pin) will help highlight this info.

Notes:

• This new feature might not be available in case the client’s org is integrated with an Award Interpreter package and is using its custom job allocation. This gap will be addressed in the upcoming Award Interpreter roadmap.

Balance check on validation and replication email notification enhancement

• Balance check at category level is now performed when validating or replicating a base template from Scheduling Console.
• The alerts are visible on the email notification, alongside with the alerts that have already been performed on service agreement and service agreement line item.

Ability to add case notes from the Resource Calendar

• To streamline the desktop experience for resources, the Resource Calendar’s users can now add new case notes directly from the console.
• A new Case Note can be added anytime by right-clicking on the job.
• On a Group Event job, resources will be initially required to select one client linked to the Group Event to add the case note to.
• Resource will select a record type which will populate the form layout. (Salesforce permissions for Client Details will drive what active record types and page layouts)
• The Job ID and Client Name will auto populate on the form.
• Upon save, the case note will be associated with the Client and the Job.

 

Job_Hover_Fields setting to support unallocated jobs

• The same Job_Hover_Fields setting has been changed to support unallocated jobs.
• When job allocation related fields are configured in the setting, they will be displayed on allocated job hover.

Region view scheduling with Scheduling Console

• Viewing work by a Region is now supported on the Scheduling Console.
• Schedulers can search for a region, and combine this with other filtering options:
  • Resource name
  • Resource tag
  • Date range
  • Group by
  • Work type
  • Hide ghosts
• By selecting a Region, the console will display:
  • The resources with either a matching primary or secondary regions, and show their jobs/shifts/activities/availabilities/timesheet items.
    • Resources will be shown regardless if they have work 
  • The jobs/shifts that are scheduled within the selected region, but allocated to the resources who do not have matching primary or secondary regions.
  • The jobs that are scheduled within the selected region, but currently unallocated.
• Ghosts are jobs/shifts/activities that do not have regions matching with the selected region. Ghosts remain uneditable, as when viewing by location.
• Available functionalities:
  • Create and manage jobs
  • Create and manage shifts
  • Create and manage activities
  • Create and manage availabilities
  • Manage timesheet items
  • View scheduled hours
• Unavailable functionalities:
  • Base template
  • Replicate Schedule
  • Publish Schedule
  • Print Schedule
• Custom settings that are functional on the Scheduling Console when viewing by location will also be effective on region view. For instances:
  • Job_Hover_Fields
  • Resource_Hover_Fields
  • Pay_Period_Start_Date
  • Pay_Period_Length

Client view scheduling with Scheduling Console

• Viewing work of a Client is now supported on the Scheduling Console.
• Schedulers can search for a Client, and combine this with other filtering options:
  • Resource name
  • Resource tag
  • Date range
  • Group by
  • Work type
  • Hide ghosts
• By selecting a Client, the console will display:
  • The resources that have an Account Inclusion for the related client, and their jobs/shifts/activities/availabilities/timesheet items.
    • Resources will be shown regardless if they have work
    • An indicator (yellow star) will be shown to help schedulers identify these resources.
  • The jobs that are scheduled for the client, but allocated to any resources regardless if they are account-included.
  • The jobs that are scheduled for the client, but currently unallocated.
• Ghosts are jobs that do not have clients matching with the selected client. Ghosts remain uneditable, as when viewing by location.
• Available functionalities:
  • Create and manage jobs
  • Create and manage shifts
  • Create and manage activities
  • Create and manage availabilities
  • Manage timesheet items
  • View scheduled hours
  • View total cost
• Unavailable functionalities:
  • Base template
  • Replicate Schedule
  • Publish Schedule
  • Print Schedule
• Custom settings that are functional on the Scheduling Console when viewing by location will also be effective on client view. For instances:
  • Job_Hover_Fields
  • Resource_Hover_Fields
  • Pay_Period_Start_Date
  • Pay_Period_Length

Centre Capital Cost Charge

• “Centre Capital Cost Charge” is a new picklist available in the Additional Fields section of jobs. 
• This field is configurable via Custom Setting / Skedulo Additional Fields
• By default:
  • Display is set to false and Hidden is set to True, so it’s not enabled.
  • Categories are set to GroupEventBooking, so it’s not available for Single Booking Jobs.

Note:

• In order for this field to be captured in the creation of Service Delivered Records, Lumary has scheduled to release their new version with this logic included. This will be informed later by Lumary.
• This new field was first introduced in HCP v1.223, but with a different default setting. For the environments that have installed our HCP v1.223, use the script below to override the default (as described above), else please ignore this note:

skedhealthcare__sked_Additional_Field__c centreCapitalCostCharge = [SELECT Id, Name, skedhealthcare__Categories__c,

skedhealthcare__Display__c, skedhealthcare__Hidden__c

FROM skedhealthcare__sked_Additional_Field__c

WHERE Name = 'Centre Capital Cost Charge'];

centreCapitalCostCharge.skedhealthcare__Categories__c = 'GroupEventBooking';

centreCapitalCostCharge.skedhealthcare__Display__c = false;

centreCapitalCostCharge.skedhealthcare__Hidden__c = true;

update centreCapitalCostCharge;

Issues Fixed

• On the Roster Management Console, the hovers of the jobs that are late in the day were moving around. The job hover has been repositioned inside the calendar to eliminate this behaviour.
• On the Resource Roster Console, the job hovers were blinking when the details were compacted with lots of information. The job hover was repositioned inside the calendar to eliminate this behaviour.
• When tags have more than 1000 records, not all of them are searchable. Allowing direct search to the server has helped avoid this issue. (Note: the same fix was released in v1.219 and affected the Resource Roster Console only. This version applies the fix in Scheduling Console, Group Event and Job Allocation where the tag fields are located)
• On the Roster Management Console, the search criteria combination, especially with resources, disabled the Apply button. This issue has been fixed.
• New balance check logics that were introduced in release v1.223 failed checking the service agreement’s end date. Dates are now supported.
• Issues (“too many rows”, “heap size”)  had been reported on the Available and Unavailable resource lists on the Job Allocation modal . This was due to the large number of records being queried  (excessive number of resources, resource tags, allocated jobs).
  
  • The solution has now been refactored to support large volumes of records:
    • Unavailable resources are presented, however the reasons are not initially loaded. Only when schedulers hover over an individual resource, the reasons will be analysed and displayed.
    • Some data points such as scheduled hours and estimated travel times, which might add weight to the load, are temporarily disabled on unavailable resources until the new implementation is stable, ensuring the feature is functional first. (this remains unimpacted on available resource list)
    • Queries on available and unavailable lists are separated to ensure no legacy logics would impact.
    • When this setting Show_Unavailable_Resource is set to “false”, it not only hides the section on the UI but also does not use the new logic
    • Tests have been performed on more environments including several of clients to ensure the conditions, initial data and settings are mimicked.
    • If your organisation is experiencing issues with the Allocation modal, the new logic needs to be set using
    • Custom Settings / Sked Configs /  Load_All_Info_Unavailable_Resources =  false

 

Important

Additional Install Component: If you are upgrading from version 1.139 or less this version of the AU Healthcare Package requires the installation of an additional component. Installation is required to enable certain core functionality

Refer to the AUHC Additional Install Component page for further details and steps to perform the installation.