Healthcare for Skedulo and Lumary v1.217

 

Release Date

April 5th 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 

Clone/Copy a group event template

• Group event templates can now be cloned:
  • There is a custom setting available to enable the Clone function : Skedulo Configs / Show_Clone_Group_Event_Button / True.
  • When cloning there are several options available. A combination of options can be selected:
    • Group event details: selecting this option will clone the data in group event details and additional fields sections.
    • Clients with service details: selecting this option will clone all clients along with their contact information and service agreement details. The data in the requirements/tags and pickup/dropoff sections will also be copied over.
    • Clients without service details: selecting this option will clone all clients with their contact info only (new service agreement details should be re-selected on the new group event). The data in the requirements/tags and pickup/dropoff sections will also be copied over.
• New group event will have a new default name as “Clone - <Old Name>”. The name can then be adjusted.
• When needing to find the origin where a new group event template was cloned from, the description field will have the “Clone From- ” indicating this.

Configure additional fields onto group event attendee template table

• In order to view more meaningful client information, the fields can now be configured on the group event attendee template.
• While “Name” and “Service” are static, other configurable fields can come from the below Objects:
  • Contact
  • Group Client
  • Service Agreement Item
• The order of configurable fields are determined while setting up a new field in the custom setting. (using Order field - see setup below)
• A horizontal scroll bar is supported when many fields are in place.
• In the case where there are no custom settings configured, the group event attendee template will display the default columns (as current).

How to setup:

1. Navigate to Custom Settings - Skedulo Additional Fields
2. Select New 
3. Field format to create a new column:

• Name: name of the field that will be stored in the backend
• Active = Checked
• Categories: GroupEventClient (do not change)
• Field Api Name: field name of that field (get from Object manager → one of the three Objects are supported (Contact, Group Client, Service Agreement Item >  Fields and Relationships > Field Name)
• Field Type: type of field (get from Object manager → one of the three Objects are supported (Contact, Group Client, Service Agreement Item >  Fields and Relationships > Data Type)
• Label: label of the field that will be displayed on the user interface
• Object Api Name: API name of that object (get from Object manager → Details) (get from Object manager → one of the three Objects are supported (Contact, Group Client, Service Agreement Item > Details > API Name)
• Order = order of this field when display in Client list (start from 0, the flexible config column will display after the Service column) [OPTIONAL]
• Display = Checked

Apply a change to future jobs when making update on group event attendee template

• When adding a new client, removing or updating a client from the group event attendee template, schedulers have the ability to select from which date the change will be applied on the scheduled jobs:
  • Today’s date is defaulted
  • Schedulers can select a future date
• This will apply the change to those scheduled group event jobs that have start dates equal to or greater than the date selected.
• There is an option to just apply the changes to the template and no jobs will be updated.

 

Sort client names in group event jobs

• In a group event job, the client list can now be sorted by Client Name A-Z or Z-A 

 

Confirmation message for reversing client cancellation in group event jobs

• In group event jobs, when reversing a client cancellation, the confirmation message has been changed to avoid confusion.

Base template self-replicates on a predefined frequency

• Streamlining the base template replication process, one or many base templates can automatically replicate themselves back-to-back or every 1, 2, 4 weeks (based on predefined frequency defined in a custom setting).
• When the self-replication process is complete, an email notification is sent out as it was with the manual process.

How to setup:

1. Navigate to Custom setting → Healthcare Self Replication
2. Select New
3. Complete the fields and save the record:

• Name: name of the record
• Active: scheduled jobs will only replicate the templates with Active setting = True
• Base Template_Id: ID of the base template, to get template ID:
  • Navigate to Base template in SF
  • Click to Base template detail
  • Get Template ID from URL

• End Date: end date of auto-schedule batch (can be blank) (use Active when needing to stop self-replicating on a specific template).
• Frequency: the gap between each self-replication, input number of days.
• Include Activities: check if the replication needs to include activities.
• Include Allocated Resources: check if the replication needs to include allocated resources.
• Include Jobs: check if the replication needs to include jobs.
• Include Shifts: check if the replication needs to include shifts.
• Skip Holidays: check if the replication needs to skip holidays.
• Start Date: first date to start the self-replication.

4. Run the script to register “Schedule job” (Setup → Developer Console → Debug → Open Execute Anonymous Window )

skedhealthcare.skedSelfReplicationSchedulable handler = new skedhealthcare.skedSelfReplicationSchedulable();

handler.start('Self Replication name');

5. Verify the “Schedule Jobs” list had a new job schedule with pre-fix “Self Replication” (pay attention to “Next Schedule Run” column)

Examples:

Base Template:

• Name: Test
• Period: Monday 3/4/2023 - Sunday 9/4/2023

1. When it is needed to replicate the Base Template “Test” every week:
   1. Base Template ID: ID of “Test”
   2. Start Date: Monday 10/4/2023 (so the first scheduled self-replication is on Monday 10/4/2023)
   3. Frequency: 7 (days) (so the next scheduled self-replication is on Monday 17/4/2023)
   4. Active: True (update the value to False when needing to stop future self-replication)
2. When it is needed to replicate the Base Template “Test” every 4 weeks:
   1. Base Template ID: ID of “Test”
   2. Start Date: Monday 10/4/2023 (so the first scheduled self-replication is on Monday 10/4/2023)
   3. Frequency: 28 (days) (so the next scheduled self-replication is on Monday 1/5/2023)
   4. Active: True (update the value to False when needing to stop future self-replication)

Identification of unsuccessful reasons in the email notification when replicating roster

• In the replication email notification, the below information will be presented:
  • Total number of source jobs
  • Total number of unsuccessfully validated jobs
  • Total number of successfully replicated jobs
  • Total number of unsuccessfully replicated jobs
  • A table of successfully replicated jobs
  • A table of unsuccessfully validated jobs, indicating: 
    • Job IDs
  • A table of unsuccessfully replicated jobs, indicating:
    • Job IDs 
    • Exception log IDs (new)
• With the logID, unsuccessful replication reasons can be traced.

Notes: There is an existing custom setting, enable_log, that would prevent the system from retrieving and sending the logID with the email notification. In this case, the messages presented in the email would be different as no logIDs are attached.

Filter client statuses in Client Availability Console

• The Client Availability Console has a new filter option using the client status. This can be used when needing to filter out the clients that have statuses as inactive or deceased.
• The filter allows for multi-selection of statuses. By default all statuses will be selected.

Client names in Timesheet Console are displayed in an alphabetical order

• When hovering over the group event jobs in the Timesheet Console, the list of clients is sorted by their full name in alphabetical A-Z order.

View ‘Client Alerts’ when printing rosters from the Roster Management Console

• When printing rosters from RMC, client alerts are displayed in a new column.
  • There is a custom setting available to determine if the column is shown, Skedulo Config / Show_Client_Alert,
  • Client alerts are presented on both single and group event jobs.

Custom setting to exclude/include unavailability records from “Total Hours Available” in Utilisation Report

• Currently, the utilisation percentage is calculated based on “Total Scheduled Hours” divided by “Total Hours Available”, where:
  • Total Scheduled Hours = Job allocations + Payable availability records
  • Total Hours Available = “Available” availability records - “Unavailable” availability records.
• By turning on the custom setting:
  • Utilisation = (Job allocations + Payable availability records) / (“Available” availability records)

Notes: Since this feature is not included within Healthcare Package, manual deployment to Client Org is required for this change.

 

Issues Fixed

• Terminologies have been adjusted so that across the system, it reads “Account Inclusions” (instead of Whitelist) and “Account Exclusions” (instead of Blacklist).
  • Only for the values in exception reasons picklist requires a manual update, the script below must be run:

skedhealthcare.skedPostInstaller handler = new skedhealthcare.skedPostInstaller();

handler.startUpdateFieldValues();

• The field mapping is updated on job offer’s flow so that the Resource’s Response is  displayed (it was showing the Status of the overall offer).
• The issue has been fixed where filtering Resources on Resource Roster Console by tags was not taking into consideration the Resource tags expiry date.
• The issue has been fixed where Job Service Items’ times were reloaded back to original times after navigating from Create to Allocate modal.

• The issue has been fixed where Scheduling Console failed to load and displayed a message “Attempt to dereference a null object” (happened only when custom setting Exception_Level = resource)

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.