Understanding Integrations
A Contract represents a subscription to the platform. The Contract Owner or Administrator can manage key elements of the contract:
-
A workspace is a smaller enclosed environment that contains integration flows and credentials. Generally a workspace reflects an environment such as a staging or production environment.
-
A member is a registered platform user that has been invited to the contract in a specific role.
Workspaces
A workspace is an enclosed environment that contains integration flows and credentials. A contract can have multiple workspaces. Each workspace is virtually separated from other workspaces within a contract.
A workspace usually reflects an environment such as a staging or production environment. Similar integration flows can exist within different spaces, using different credentials. This enables new and updated workflows to be tested thoroughly in a staging environment before being moved to production.
A workspace includes members, Integration flows, and Credentials
-
Any member of the contract can create a workspace.
The workspace owner has full access to Managing workspaces including giving platform users appropriate levels of access.
-
The core function of a workspace is to build and test Integration flows.
An integration flow is a set of integration components and credentials used to synchronize data between multiple applications or services.
-
Credentials are used to authorise different systems to connect with each other.
Integration flows can only be used with the appropriate credentials.
Limited workspaces
All new Workspaces created within a contract are Limited workspaces by default.
Limited workspaces are denoted as Limited when the pointer hovers over the icon next to the workspace name (ie, when the icon takes a mouseover event).
Limited workspaces are designed to function like sandboxes. They have limited logging and data storage.
Limited workspaces are also work-time restricted. All active flows in limited workspaces stop after eight (8) hours.
If an integration flow contains messages in the processing queues, these messages are lost when the flow is stopped.
To continue testing, flows in limited workspaces must be manually restarted.
Limited workspaces should not be used for production flows
Full workspaces
Full workspaces are, by contrast, designed for production use.
Full workspaces are denoted as Full when the pointer hovers over the icon next to the workspace name (ie, when the icon takes a mouseover event).
Full workspaces have no work-time restrictions: integration flows can run continuously and without interruption.
As a consequence, messages in processing queues are not lost to work-time constraints.
If you have a Limited workspace that you want to use for production flows, contact support.
Creating Workspaces
See Managing workspaces for details on how to create a Workspace.