Tracking automatically enabled for all new custom objects

Enabling tracking on a custom object causes any changes to instances of that object’s records to generate a "change event". These "change events" are internal to the platform and are consumed by other platform features, such as triggered actions, webhooks, and GraphQL subscriptions.

Manually enabling tracking for a custom object
Custom objects that were created prior to this release and used with triggered actions, webhooks, or GraphQL subscriptions, needed tracking to be enabled manually by making the following API calls:

Find the objectId of you custom object:

curl --location --request POST "https://api.skedulo.com/custom/schemas" --header "Authorization: Bearer <token>"

Enable tracking on your custom object, by passing your objectId to this endpoint:

curl --location --request POST "https://api.skedulo.com/custom/standalone/schema/{objectId}/track" --header "Authorization: Bearer <token>"

Automatic enablement of tracking for a custom object
With this release, all new custom objects will have tracking automatically enabled when created.
Any custom objects created prior to this change will still need to have tracking enabled manually via the API, as per above.