Skedulo New Web App Release Notes v19.36.0

Release date

September 2nd, 2019

In preparation for Skedulo to implement a global multi-region infrastructure, all users will now be required to log into the web app using their team name. Those who try to log in using the option "Login with Salesforce" will be redirected (back to their team's login URL) and must log in using their team name.

Note: Onboarding without a team name will no longer be permitted.

Refer to Logging into the Skedulo Web App.

Schedulers can now restore canceled jobs (for real this time)—"Jobs which have been canceled can now be restored to their previous state. The option "Restore job" can be found in the job header of the job details view—in the additional options menu."

For added measure, we have also added the ability to restore jobs in a recurring schedule (jobs that recur at a future date).

Note: Currently, the option to restore jobs is not supported if your organization has enabled "Resource Requirements."

Refer to Restore a Canceled Job.

For those who use shifts, the "Resources" schedule page now shows shifts labeled with location and shift name.

Refer to Resources Console.

The main "Shifts" console user interface has been updated to reflect the same colors used to display shifts on the scheduling swimlanes.

Refer to Shifts.

We've made some improvements for the job details swimlanes—now cards can't be dragged while an update is in progress from a previous movement.

When looking at a resource's schedule you can now see their travel time.

Note: This travel time only shows when a resource is allocated a job during their availability and adheres to the travel time settings (so you can ignore travel times for the first job of the day for example).

Refer to Resources Console.

We've fixed an issue where new jobs could not be created from a template. The problem arose when job templates contained tags that had been removed via Salesforce.

Now, if a job template has tags that have been deleted, we will remove them from the "Create Job" page and display a warning notification to the user. If the user loads a job template containing deleted tags, we will post a warning notification to let the user know, so the user can manually remove them.

We've fixed a bug associated with multi-day job cards in the scheduling swimlanes (viewed using the calendar "Week" setting). Now resizing the job from the start-time will not save changes to the server.

Recurring schedules now show start and end dates according to the format selected in the "User Preferences," e.g., Day, Month, Year, or Month, Day, Year.

We've fixed an issue in the "Resources" schedule page where jobs were difficult to distinguish when activities with the same start-time overlapped them. Static activity cards have been moved behind static job cards. Dynamic job cards will always take priority and show up above static cards like activities. This way the user will still get context on an activity that is behind a job card. We have also increased the width of the activity card to 95% so a user can still see and click it.