Supported Events

You can use events to obtain changes that occur in Oracle Field Service application, such as field changes, status changes, and so on. An event is generated when a change occurs in the application. You need to first subscribe to the required events defined in the application before you try retrieving the related changes.

You must consider the following information while using the events API:

• Event subscriptions expire after 36 hours. If your request contains an expired subscription ID, the API returns a 404 error code. You can also request a subscription several times with the same event list, but the application returns the same subscription ID.
• You can create up to 100 subscriptions at a time. If the number exceeds 100, the subscription creation fails. You must wait for 36 hours for the oldest subscription to expire.
• Events are available for seven days time. Earlier events still may be accessible, however, this can't be guaranteed.

• Events produced by the application should be read and processed once they appear. Old events that were generated 15-20 hours ago may require more time and system resources to be recovered and returned. Avoid creating flows that git require reading from the past; use this ability only when it is necessary to restore after some failure.

• Events API doesn't support file properties.
• The maximum size of a custom property's text is 5KB. If the size is more, then the text is truncated to 5KB and the following message is added after the truncated text:

  TRUNCATED: Property value was > 5KB - too long to be published in full

You can specify these events in the request for creating a subscription:

• Activity Events
• Activity Link Events
• Collaboration Events
• Inventory Events
• Required Inventory Events
• Resource Events
• Resource Preference Events
• Route Events
• Routing Events
• Service Request Events
• Support of Forms
• User Events