-
Notifications
You must be signed in to change notification settings - Fork 28
Mapping UI design to REST domain model
The ipaas-rest server use an own domain model which can be inferred from this schema.
Following the UX walkthrough the following mappings can be inferred (all UX objects are in italics, all domain objects in FixedWidth.
| UI / View | Domain | Descriptions |
|---|---|---|
connection type |
|
The overall category for an connection as it can be selected in the first step when creating a connection |
connection field |
|
Each connection type a certain set of fields is available (these has been defined externally and originate from the supported Camel component fields). These fields can be selected in the second step when creating a connection. When all fields |
connection value |
|
This is the data entered for the connection fields as entered in step 2 when creating a connection. It refers to the connection field. |
connection |
|
The connection type and the connection values together are the connection.
This is also used during the creation of an integration when selecting the connection (like here in the lower half). |
action |
|
Each |
action field |
|
These are the possible field values which can be edited when configuring the connection as part of an integration as shown as this step in the integration wizard. |
action value |
|
Analogous to the connection value_s specified when creating a _connection which holds the values configured, the action value holds the |
start / end connection (looking for a better name) |
|
The fully configured connection with the selected action and references to the connection values and the action values. Its created as part of the integration wizard when the start / end connections has been added, like after this step |