Description |
---|
It's common to apply custom validation rules in a CRM (like Salesforce) to prevent invalid data saving to the database (which can cause certain actions in Skedulo to fail). Previously, when these failures occurred, Skedulo did not display any error message. Now we display the following toast (or pop-out) message: "Custom user validation error: <user defined name of validation rule>." Note: We don't cover all actions yet—for now, just creating and updating jobs. |
When using Skedulo connected to Salesforce, the Skedulo admin settings for "Developer Tools" now includes a new Salesforce nav tab that displays:
Refer to Admin Setting: Developer Tools. |
Building on the enhancements made in our last release, in this update we've improved the stability of the map view (notably, the zoom functions). Refer to Map View. |
Description |
---|
We've fixed the job count display in the "Recurring Schedule" view (in the "Jobs" console). It will now display the correct count of jobs on the page. |
The admin settings for "Custom Fields" has been updated so any new "Case" objects will now use the "Case Number" field as the object's name. Note: This only affects organizations who use Salesforce to connect to Skedulo. |
We've fixed a bug, which would display a green tag next to resources (in the swimlanes) even when not all the job requirements were met. |
We've fixed an issue with "Jobs Calendar" (in the Scheduling console). It was not showing all possible job records. |
Comments
0 comments
Article is closed for comments.