Using Data Selection to publish types and events to CONNECT data services

Sequential creation of data selection types and data

The AVEVA Events to CONNECT agent creates Types and Data in a sequential manner so that you do not have to toggle the selected property every time. For example, when you create data selection Types and Actions:

1. Create a data selection property Type.

   The Type value can be one of the following:

   • AuthorizationTags

   • AssetTypes

   • Enumerations

   • ReferenceDataTypes

   • EventTypes

   • Assets

   • ReferenceData

   • Events

2. Create a data selection property Action.

   The Action value can be one of the following:

   • Create

   • Update

   • Delete

   • Patch

     Note: The Action property supports the Patch action type for assets.

3. When AVEVA Events to CONNECT polls for data at a scheduled interval or when data selection receives an update, the following data selection items will always be processed in sequential order:

   1. AuthorizationTags

   2. AssetTypes

   3. Enumerations

   4. ReferenceDataTypes

   5. EventTypes

   Note: The processing order of each of the above data selection items is always Delete, Create, and then Update.

4. Once the Types have been created, the following data selection items will be polled in parallel:

• Assets

• ReferenceData

• Events

Note: The processing order of each of the above data selection items is always Delete, Create, Update, and then (for Assets only) Patch.

Sequential data polling sequence

Data is always polled using the following sequence:

4. Delete the Data in parallel.

5. Delete the Types in reverse sequential order.

6. Create or update the Types in sequence.

7. Create or update the Data in parallel.

Sequential data and type publication

The order in which Types and then Data are sent to CONNECT data services is always Delete, Create and then Update. Consider the following example:

8. The user configures one Data selection item for each type with the Create action.

9. The user configures three Event Types data selection items with the Delete action.

10. The user configures five Asset Types data selection items with the Create action.

11. The user configures five Reference Data data selection items with the Create action.

12. The user configures 15 Events data selection items with the Create action.

13. The user configures three Events data selection items with the Delete action.

For the configuration described above, the following sequence occurs on each scan cycle:

14. The AVEVA Events to CONNECT agent will delete the Events in parallel (step 6 in the example above).

15. The Event Types will be deleted.

16. The Asset Types will be created.

17. The Types will be created.

18. The Reference Data will be created.

19. The Events will be created.

Notes:
- You can omit the scheduleId property for data selection items that are Types (AuthorizationTags, AssetTypes, Enumerations, ReferenceDataTypes, EventTypes). This ensures that types are polled only when the agent is started or when data selection items are updated.
- You can keep a valid scheduleId for data selection items that are Data (Assets, ReferenceData, Events). This ensures that the AVEVA Events to CONNECT agent polls for them every scan cycle.