Xentara v1.0
User Manual
|
Xentara has a built-in service provider named SignalFlow. This service provider provides element types that can be used to direct signal and data flow within Xentara.
Signal bridges are microservices that copy the values from one attribute to another. Each bridge consists of a number of connection between a readable attribute of a Xentara element, and a writable attribute of the same or of a different Xentara element. Whenever the copy operation is triggered, all the values are read from the source attributes and copied to the corresponding target attributes.
Normally, a signal bridge only copies the attribute values in the operational stage. A bridge can be configure to copy the values in any stage, however.
Signal bridges expose a single task named copy that performs the copying. You can insert that task into an execution pipeline and attach it to a timer or an event. To refer to the task, use its primary key. The primary key of the copy task of a signal bridge called “My.Signal.Bridge” is “My.Signal.Bridge.copy”.
Signal bridges have the following members:
key | The signal bridge’s primary key. |
name | The signal bridge’s name. The name is the last component of the primary key. |
UUID | The unique UUID of the signal bridge. |
copy | Copies the values from the source attributes to the target attributes |
To refer to a member, use its primary key. The primary key of the copy task of a signal bridge called “My.Signal.Bridge” is “My.Signal.Bridge.copy”.