Skip to main content

October/November 2022

Kara Kirchner
  • Updated

ENHANCEMENTS

Labor Demand Planning Application & API

This feature is in beta and is only available to members of the Labor Demand Planning Early Adopter Program.

  • New Demand Import API

      • Our Demand Import API has been rebuilt, allowing for simpler integrations with Enterprise Resource Planning (ERP) systems.

        • Automatically applies conflict resolution rules with existing demands, determining the correct end state of an organization's labor demands with minimal user input.

        • Leverages the new Labor Scenarios feature to represent business logic for what templates need to be demanded, and how they relate to each other in time

        • Turning off existing labor demands has been simplified and the handling of assignments which were previously covering those demands has been improved

  • New Demand Planning Page

      • This is a revamped Demand Planning page with improved user experience (UX) which makes manual demand updates more intuitive for the user.

      • This also leverages the new concept of "Labor Scenarios" to allow the demanding of multiple labor demand templates in significantly fewer clicks than our classic Demand Planning page.

  • Labor Scenarios

      • A scenario, or labor scenario, is an entity which can be configured to represent the labor needed for various real world states an organization may find themselves in.

      • Scenarios are composed of labor demand templates, configured in template rotations which define what lines need what labor mixes, and when.

      • Scenarios are sometimes referred to as “base schedules for demands.” They allow the templates to be associated to each other in time and saved as a scenario, which then allows users to simply turn these entire scenarios on or off as their organization’s state changes.

  • Labor Demand Templates

      • Labor Demand Templates receive a brand new UI to facilitate simpler labor demand template maintenance.

      • Templates define the dimensions which should be demanded, and how a set of dimensions relate to each other in time.

      • This is done using offsets on each dimension, with the actual time the dimensions will be demanded later being defined by these offsets and when the template rotation is defined in the Labor Scenario.

*Demands API targets Reporting App, New Demand Planning App and Mass Demand Deletion API.

Indeavor Schedule

  • Roster navigation & performance improvements
    • Roster date range is limited to 45 days at a time (IND-4482)
      • Users are able to navigate to any date in the future or past with up to a 45 day range.
      • If the user selects a date range > 45 days, an error message will display and direct the user to change the date range accordingly to proceed.
      • Reports should be utilized for larger date ranges to limit Roster utilization.
    • Roster 'Today' button loads one week of data (IND-4483)
      • Previously, the 'Today' button would extend a user's date range from today to the selected End Date. This resulted in large date ranges being loaded, mostly unknowingly to the User.
      • Selecting the 'Today' button will navigate the user to today's date and load one week of data only.
  • Leave Requests - Multi-day leave requests are sorted by date on Leave Requests page (IND-4534)
  • New Email Notification provider and mechanisms (IND-2244)
    • Users can configure email notifications for leave requests submitted in Engage (IND-2103)

Advanced Features

This release of the Advanced features application contains the following update to Mass Update:

  • Early Arrival and Late Departure actions can now extend existing assignments, in addition to the previous functionality of adding new assignments concurrent to the existing assignment (IND-4204)

Reporting App

  • New Labor Alignment Analytics KPI (IND-2738)

    • This KPI will measure the deviation between schedules and demands (total shortage hours + total overage hours) / total demanded for hours

Roles App & Identity

To interact with our new APIs, users will need a client credential as a layer of security to access our system.  A UI for the user to request a client credential, on demand. 

  • Admins will now be able to go into the Roles App and access a new Client Credential section.
  • Users can request a Client credential, as well as view and delete existing credentials.
  • Client Credentials are User-specific - Admins cannot see other Admins' credentials.
  • Client Credentials should only be known by the user requesting it.

BUG FIXES

Indeavor Schedule

  • Displaying or not displaying 'Approved Leaves' on the Employee or Jobs Roster does not impact the display of other entities, such as Jobs and Posts (IND-4494)
  • Roster Assignment Percentage is calculated correctly for all Cultures (IND-4434)
  • Labor Demand Template Rounding Rules are saved correctly for all Cultures (IND-2813)
  • Able to adjust and save Employee record after receiving 'The short name must be between 1 and 10 characters long' error message (IND-4480)
  • Past Employee Group Memberships show up when 'Show Only Current' option is unchecked in an Employee record (IND-3792)
  • Special Assignments not counting against Shift-based Leave Quotas (IND-2839)
  • Base Schedule Design Report is accounting for the validity period of preferences (IND-4425)
  • Base Schedule Assignments Report is showing 'Auto-Qualified' allowances for all base schedules (IND-4037)
  • Minor Scheduling Method Builder UI change in the 'Assigned Location' module (IND-3832)

Advanced Features

  • Jobs in Mass Update are now listed in alphabetical order (IND-4484)
  • Times contained in assignment attribute values are now listed in chronological order in Mass Update (IND-2339)

TECHNICAL UPDATES

  • Additional database encryption for some environments
  • Production URL name changes for some environments

Related articles