Skedulo Developers |

Articles in this section

See more

Skedulo Package Release Notes v102.47

Release Date(s)

Sandbox Release Date

February 17th, 2020

Production Release Date

February 24th, 2020

Important

For those organizations who are on a Skedulo long term support arrangement—please check your sandboxes to see if this new package has been deployed successfully (the deployment will be performed on February 17th, 2020). If this package is not installed, you will need to make arrangements to deploy it manually to your sandboxes (to test) before March 9th, 2020 (see Manual Installation Links).

What's New?

Description

Change events are now produced whenever an Activity, ActivityResource or Availability is modified.

The custom batch endpoint will check read permissions on object and fields for the current user before executing incoming GraphQL query and REST `GET` actions.

The batch endpoint now supports actions with type `GET`.

A new remote org preference `salesforceStreamingMethod` has been added. If set to -2 Salesforce streaming is disabled, -1 (the default) platform events are used, a value between 0 and 300 is the interval to wait between polling.

We have added a Debug Log object and a logging mechanism to save error information to the Debug Log object where possible when errors occur.

We've made the following changes to Platform Events:

  • Added Int optional field to Preferences custom setting.

  • Removed EnableChangeEvent preference entry.

  • Added SalesforceStreamingMethod preference entry, defaulting to -1.

  • Added Polling Change Event object with the same fields as the current Change Event platform event.

  • Triggers are updated to route change events to either the Polling Change Event object or to Platform Event based on SalesforceStreamingMethod value:

    • -2: Turn off change event generation.

    • -1: To Platform Event.

    • >0: To Polling Change Event.

      It is recommended to use greater than, or equal to, 5 when using polling change event.

Issues Resolved

Description

Some users had reported that Job Status was automatically reverting back to Pending Allocation.

The Job Status field on Jobs is now derived entirely from the statuses of its children Job Allocation and Resource Requirement statuses by default.

Any update to the Job Status field will have no effect, except when it is changed to Complete or Cancelled status.

The "DisableDirectJobStatusUpdate" custom setting has been added to allow this behavior to be turned off if required.

We've resolved an issue where a resource could still operate within a job workflow after being removed from the job using the Skedulo web application. This would result in them being reallocated to the job in the web app.

Job Allocation records with "Deleted" status are now read-only by default and any update to those records will have no effect.

The "DeletedJobAllocationAreReadOnly" custom setting has been added to allow this behavif desired.

Manual Installation Links

Sandbox: 

https://test.salesforce.com/packaging/installPackage.apexp?p0=04t2v000007Lakc

Production: 

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t2v000007Lakc
Recommended install package for all users.

Related articles

Comments

0 comments

Article is closed for comments.