Skedulo Package Release Notes v102.30

Release Date(s)

Sandbox Release Date	May 17th, 2018
Production Release Date	June 4th, 2018
Note: some customers have negotiated advanced notice of upgrade and the ability to opt-out of upgrades. If you are one of these customers, then the above dates may not apply.

What's New?

Description

Added a "View All" permission set to give a user "Read" access to all Skedulo data.

Added a "Baseline" permission set that defines the minimum permissions required for a Skedulo user. Users that do not have either a "Scheduler" or "Resource" permission set should at least be assigned this permission set.

Note: It is especially important to assign the new Baseline Permission Set to users that do not already have one of the provided Skedulo permission sets. Users with only custom permission sets will not receive access to new Skedulo objects to be released in future updates and may run into issues using the application.

Improved the way shift times are calculated. Shifts are defined by start-time, end-time and duration values. Users can now create shifts by providing any two values; the third will be calculated automatically (i.e., start-time and end-time, start-time and duration, end-time and duration).

Example: Start-time=07:00 am and Duration=15 min. End-time is automatically calculated to be 07:15 am.

Note: Start-time and Duration are now optional fields. However, the existing Shift page layout is not updated by the package upgrade. So the page layout has to be manually updated to remove the "Required" property of these two fields (see figure 1 below.)

The package install script now enables the "Job Allocation Time" trigger by default.

"Job Allocation Time" is a new field we added to the "JobAllocation" object to simplify access to the start and end time of a job allocation. We have also added the "Duration" field to "JobAllocations."

Enabled "Field Tracking" for "Job Status" on the "Job" object.

Enabled "History Tracking" on the "Job Allocation" object.

Enabled "Field Tracking" for the following fields: "Time Responded," "Time Start Travel," "Time Checked In," "Time In Progress," "Time Completed."

Added the "Resource Requirements" object.

The resource requirements object will be used in later releases to allow schedulers to specify the quantity, skills and time constraints of the resources they wish to schedule.

Fixed an issue where, during the package update, job allocation migration batches would fail when there were more than 50,000 job allocation records.