EventTypes are system events being distributed over ActiveMq when certain events happen. These can be configured via API or via Configuration UI.
VidiControl Product Events
This list shows all VidiControl product events. There may be more, adapter-specific events.
|
Event Name |
Description |
Consumer |
|---|---|---|
Swp08Router.switchFailed
|
|
ProxyAPI |
|
JSON
|
||
Swp08Router.switchSuccess
|
|
ProxyAPI |
|
JSON
|
||
Swp08Router.switchExternal
|
7 |
ProxyAPI |
|
||
VidiControl.chunkDeleted
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.chunkChanged
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.chunkCreated
|
|
ProxyAPI |
|
||
VidiControl.vidiCoreItemCreated
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.commandExecutionTimeOutError
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.commandExecutionInvalidDeviceError
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.commandExecutionDeviceStatusError
|
|
ProxyAPI |
|
||
VidiControl.commandExecutionDeviceOffline
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.commandExecutionDeviceDeleted
|
|
ProxyAPI |
|
||
VidiControl.unknownCommandExecutionError
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.commandStatusChanged
|
|
ProxyAPI |
|
JSON
|
||
VidiControl.chunkStatusChanged
|
|
ProxyAPI |
|
JSON
|
||
Content JSON Datastructure
The Content object consists of two fields, action and input. Depending on the action, the input structure may vary.
The Content JSON structure is defined in the configuration depending on the message consumer needs. All examples below show the frontend needs.
Actions
In this section, the different action values with their corresponding input structures are described. It is allowed to configure unlimited actions per event. Even several actions of the same type are allowed.
NotifyClient
Consumer of this action is the ProxyAPI to notify web clients about an update.
Action: notifyClient
Input:
|
Field |
Type |
Description |
Example |
|---|---|---|---|
|
Timestamp |
string |
|
|
|
ChunkId |
string |
|
|
|
UpdatedNeeded |
boolean |
Whether the GUI should be updated regarding this event. |
true |
|
MessageType |
string |
|
|
|
Emitter |
string |
|
|
|
Severity |
string |
The severity of the the Message. Possible Values: Information, Warning, Error |
Information |
|
Message |
object |
Message to be displayed in different languages |
|
StartWorkflow
Action: startWorkflow
Input:
|
Field |
Type |
Description |
Example |
|---|---|---|---|
|
Name |
string |
The name of the Workflow to start |
WF_Import |
|
Version |
string |
The version of the workflow to start |
latest |
|
Data |
object |
this field contains a list of parameters with name, type and values |
JSON
|
NotifyCustom
Consumer of this action is the ActiveMq topic to notify external moules listening.
Action: notifyCustom
Input can be freely configured and depends on the actual configuration and consumer.
Placeholders
These Placeholders in the system are substituted with their current value:
|
Placeholder |
Example Value |
|---|---|
|
{-{Placeholder_ExternalBookingDefinitionId}-} |
CM0B |
|
{-{Placeholder_ExternalBookingId}-} |
CYOB |
|
{-{Placeholder_ExternalChunkId}-} |
JHG3 |
|
{-{Placeholder_ExternalCommandId}-} |
UZGS |
|
{-{Placeholder_VCCollectionId}-} |
COLLECTION-VX-654241 |
|
{-{Placeholder_VCItemId}-} |
ITEM-VX-5746 |
|
{-{Placeholder_VCSequenceItemId}-} |
ITEM-VX-6732 |
|
{-{Placeholder_MessageType}-} |
chunkStatusChanged |
|
{-{Placeholder_ExternalDeviceId}-} |
oNo |
|
{-{Placeholder_DeviceState}-} |
Online, Offline, Deleted |
|
{-{Placeholder_Emitter}-} |
ChunkProcessor |
|
{-{Placeholder_TimeStamp}-} |
2022-11-03T12:08:31.5434113Z |