Skedulo New Web App Release Notes v20.36.0

Release date

August 31st, 2020

As of August 31, 2020, the new job details page is no longer in beta and is the default view for all jobs. The new job page has been enabled for all new organizations. 

Organizations that have never tried this page before will see the new job details page when viewing a job.

The new version of job details provides an enhanced user experience with an improved layout including:

• Better visibility and clarity for job-related information.
• Clearer and more accessible navigation to job actions.
• More space for the scheduling view in a dedicated tab.

Customers who have tried the new job details page in the past but chose to revert back to the old jobs page will have the new job details page turned off by default and can continue to use the older version (8.0.1 Job Details (deprecated)) while we continue to support it.

Organizations that do not want to use the new job details page will need to turn it off via the Settings -> Beta features page. 

For more information about the job page, see 8.0.0 Job Details.

You can now view and edit custom fields on the following object record pages:

• Account
• Contact
• Location
• Region
• Tags

Custom fields appear under Additional fields.

We've updated the Optimization history page to include one-off optimization results as well as summary information about optimization runs. 

You can view this information under Manage -> Optimizations.

Under certain circumstances, Skedulo users found that custom fields would disappear on an object when they edited or deleted custom fields on another object. 

This was caused by an incorrect DELETE request that was being sent when saving changes to a custom field.

This issue has been resolved and custom fields no longer disappear when editing other custom fields.

Custom fields with a number type were permitting users to input an invalid number for number/decimal fields. This caused an error when trying to save an object with an invalid number or decimal field value. 

This was due to custom fields not respecting the permitted length on number and decimal fields. 

This issue has been resolved and field lengths are now respected on custom fields with a number type.