Version 0075

Updated 1 week ago by Leigh Hutchens

Schedule

Bank holidays

You will now be able to see bank holidays visualized as a red "badge" next to the date and when hovering over the date in the schedule view.

If you want to know more about configuration of bank holidays, please see Bank holidays documentation.

Special days

You will now be able to see special holidays visualized as a grey "badge", next to the date and when hovering over the date in the schedule view.

If you want to know more about configuration of special days, please see Special days documentation.

Examples bank holidays and special days

Day view
Monthly view

Default shift type start and end time

As per this release, we have changed the behavior on default shift type start and end time when assigning/editing a shift in the schedule view or in base schedule.

If the shift type is set up as 00:00-00:00, we will no longer change it to 12:00-13:00.

It's now also possible to add a shift with start and end time of 00:00 to 00:00 (previously, the user had to enter 23:59 as end time) .

Default break start and end time

When adding a break, it will now default to 30 minutes in the middle of the shift. For example, if the shift is from 9:00 to 11:00 the break will default to 9:45-10:15.

If the shift is shorter than 30 minutes, the break will be the length of the whole shift.

Language Support

Neo is now available in Russian.

Bug fixes

  • When changing the home unit of an employee, future absences and leave applications will remain in the "old unit".

REST API

POST ../edit-forecast

With this operation, you can edit the calculated forecast through the API. Use this operation if you want to edit a forecast configuration for a specific time with data you have externally and not to amend through the GUI in Neo Forecast.

Full URL is : /forecast-variables/{externalForecastVariableId}/forecast-configurations/{externalForecastConfigurationId}/edit-forecast?externalUnitId={externalUnitId}?externalSectionId={externalSectionId}

  • ​externalForecastVariableId​ - External ID for the variable set up in Account settingsForecastVariablesExternal ID
  • externalForecastConfigurationId - External ID for the configuration as set up in Account settingsForecastConfigurationExternal ID
  • ​externalUnitId​ - External ID for a unit as set up for units in Classic → Settings → Tables → integration keys
  • ​externalSectionId​ (optional) - External ID for a section as set up for units in Classic → Settings → Tables → integration keys
  • forecastDataModifier​
    • startTime - timestamp from what full hour the edit should be made on
    • endTime - timestamp to what full hour the edit should be made to
    • percentageModification - if you want to modify with a percentage value
    • newValueForPeriod - to set a new value for the chosen period.

More information about API Web Services can be found here.

newValueForPeriod : If data exists, the new value will replace the current value as a percentage of the already existing values. If no value exists, it will allocate the data evenly over the resolution of the variable
You are not allowed to use more than 5 concurrent requests (that is, running more than 5 threads simultaneously).


How Did We Do?