Dashboard

What the dashboard shows

1. Project summary: Displays the project name, description, current status, and creation date. This gives anyone opening the project immediate context about what it does and where it stands.
2. System health: Shows the live connection status of every system in the project network. Systems display as active, inactive, or in an error state, so your team can identify connectivity issues without running diagnostic commands.
3. Flow activity: Lists recent flow executions alongside run counts, success rates, failure rates, and timestamps. Teams use this to spot underperforming flows or unexpected spikes in execution volume.
4. Error log: Surfaces recent integration errors in one place. Rather than waiting for system alerts, your team can proactively monitor and act on errors as they occur.
5. Recent activity: Tracks configuration changes and team actions within the project, giving you a lightweight audit trail of who changed what and when.

Project Details

What project details include

1. Project name and description: The name and a plain-language summary of the project’s integration purpose.
2. Status: The current operational state of the project, such as Active, Inactive, or Draft. Status communicates whether the project is live and processing data.
3. Created by and creation date: The user who created the project, along with when it was created. Useful for tracing project ownership in large organizations.
4. Last modified: The date, time, and user associated with the most recent change. Use this to confirm that a project reflects its latest configuration.
5. Connected systems: A list of every system that is currently part of the project network. This gives you a quick inventory of what is integrated without opening the network canvas.
6. Team members: All users who have access to the project, alongside their assigned roles. This makes it easy to verify access without navigating to membership settings.

Edit Project

What you can change

1. Project name: Rename the project when its scope changes or when organizational naming conventions are updated. The new name appears everywhere the project is referenced in OneEnterprise.
2. Description: Update the project’s plain-language summary to reflect integration changes, clarify the purpose for incoming team members, or document a significant configuration milestone.
3. Status: Set the project’s operational state. Use status to communicate where the project is in its lifecycle — for example, moving it from Draft to Active when it enters production, or to Inactive when an integration is paused.
   

Add or Remove Team Members

Team member roles

Adding members

Removing members

A project must always have at least one Owner. You cannot remove the last Owner. Assign a new Owner before removing the current one.

Project Network

What is a project network?

1. A project network can include multiple systems simultaneously.
2. Every system in the network needs a configured connection before data can flow through it.
3. Systems and connections can be added or removed at any stage of the project without disrupting unrelated flows.
   

Add Entity

Adding a system is the first action you take when building a project network. It registers a system as a participant in the integration and places it on the network canvas. OneEnterprise includes a system catalog with prebuilt connectors for common enterprise platforms, including ERP, CRM, and cloud applications. You select systems from this catalog and add as many as the integration requires. At this stage, the systems are present on the canvas but are not yet connected.

Connect Entities

Connecting systems defines the relationship between two systems on the network canvas. A connection establishes the direction of data flow — identifying which system is the source and which is the target for a given integration. On the canvas, connections appear as lines linking two system nodes. Each connection must be initialized before OneEnterprise can exchange data through it. A project network can contain multiple connections between different combinations of systems.

Initialize a Connection

Initializing a connection is the step that authenticates OneEnterprise with each system involved. During initialization, you provide the credentials or API keys for the source and target systems. OneEnterprise uses these credentials to test reachability and confirm that data can flow between the systems. A connection that passes its test displays a green status indicator on the canvas. Connections that fail initialization cannot be configured or used in flows until the underlying authentication issue is resolved.

If initialization fails, verify that the system’s API endpoint is reachable from your network and that the credentials match those in the source or target system’s admin settings.

Configure Connection Details

Edit Connection is the interface in OneEnterprise for modifying the configuration of an existing connection between two entities in the project network. A connection determines how data flows between a publisher system and a subscriber system. Over the life of an integration project, business requirements change — objects are added, flow directions are adjusted, error-handling policies are updated, and filter logic is refined. Edit Connection is where all of those changes happen.

Edit Connection is only available from the Interaction view. The Dataflow view does not support connection editing. Navigate to the Interaction view before accessing connection settings.

Accessing Edit Connection

To reach the Edit Connection interface, you open a project and switch to the Interaction view. Clicking the connection line between two entities on the network canvas opens the Network tab, which displays the connection details and an action menu. The Edit Connection band in that menu is the entry point for all connection editing.

The first thing Edit Connection asks you to confirm is which object and flow direction you want to edit. A pop-up presents two drop-down menus: one for the object and one for the flow direction supported by that object. This selection scopes the session — every setting you see after clicking Proceed applies specifically to that combination of object and flow direction.

The Edit Connection screen

After selecting an object and flow direction, the Edit Connection screen loads. Its layout gives you full control over a connection without overwhelming you with all settings at once. Content is organized into tabs, bands, and expandable sections that you work through progressively.

Object and flow direction selectors

At the top of the screen, the Object drop-down and Flow Direction drop-down show the selections you made in the pop-up. You can change either from here — switching to a different object or flow direction without going back to the pop-up. The screen refreshes to display the settings for your new selection.

Customize

The Customize button opens the Edit Configuration screen, where you can configure and activate a published object. It is the deeper configuration layer for the selected object.

Entity tabs

The screen organizes settings into two entity tabs — one for the Publisher entity and one for the Subscriber entity. The Publisher tab opens by default. Each tab contains the settings specific to that entity’s role in the connection. Hovering over a tab shows a tooltip with system details, which is useful when multiple connections are open and you need to confirm which system you are configuring.

Bands

Within each entity tab, settings are grouped into collapsible bands. Bands keep the interface compact — you expand only the section you need by clicking the accordion icon in the top-right corner of each band. Every band works this way, from Activation Status through to Value Mapping. Some settings within a band may appear enabled or disabled depending on the entity type.

Activation settings

The Activation band controls whether the selected object is live in the integration and how much diagnostic information OneEnterprise captures about it. Expanding the Activation band reveals two settings: Activation Status and Trace.

Activation Status

Activation Status determines whether the object actively participates in the integration or remains inactive. Setting the object to Active means OneEnterprise processes data for it as flows run. Setting it to Inactive pauses processing for that object without removing its configuration. Both states save automatically when you select them, and a confirmation message appears on screen. Teams typically use Inactive status during testing, maintenance, or when an object’s integration is temporarily suspended.

Trace

Trace controls diagnostic logging for the selected object. When Trace is enabled, OneEnterprise captures a record of data as it moves through the connection, which is valuable for diagnosing unexpected behavior or verifying that transformations are working correctly. The Trace band contains a toggle switch to enable or disable this logging. Enabling or disabling Trace saves automatically.

The Log Level and Trace Limit fields remain inactive until you enable the Trace toggle. This ensures that the logging configuration is accessible only when logging is active.

Configuration settings

The Configuration band is the most extensive section in Edit Connection. It contains seven distinct areas, each controlling a different dimension of how the connection processes and routes data. Expanding the Configuration band reveals all seven areas as individual bands: Error Handling, Filter, Mapping, Settings, Subscription, Trigger, and Value Mapping.

Error Handling

The Error Handling band defines how the connection responds when data processing fails. Clicking the band opens a list of error settings, each displayed on its own band with a drop-down at the end. The available options in each drop-down correspond to the specific error scenario that the setting governs. Configuring error handling gives the integration predictable, controlled behavior when exceptions occur — rather than failing silently or requiring manual intervention for every error.

Filter

The Filter band controls which incoming records OneEnterprise processes for this connection. Rather than passing all data from a source system through to the target, filtering lets you scope the integration to only the records that meet your criteria. OneEnterprise supports three filter modes, selectable from a drop-down at the top of the Filter screen: Use Default Filter, Use Custom Filter, and Use Both Filters.

The Default Filter is a pre-built ruleset provided by the application. You select values for the fields that the system presents — you cannot add or remove fields from the ruleset itself. An And/Or toggle at the top of the filter lets you control how multiple rules are evaluated together. Use And when all rules must be satisfied simultaneously; use Or when matching any one rule is sufficient. When the Default Filter is selected, the Custom Filter is disabled.

The Custom Filter gives you full control over which fields drive the filter logic. You build the filter by selecting fields from a catalog of available fields and organizing them into rulesets. The Customize Field List button opens a pop-up where you move fields between an Available Fields list and a Filter Fields list. Fields can be added, removed, reordered via drag-and-drop, and renamed directly in the Filter Fields section.

Mapping

Mapping defines how data from the source system is transformed into the structure that OneEnterprise — or the downstream target system — expects to receive. When a trigger activates and raw incoming data arrives, it rarely matches the format the target system needs. Mapping bridges that gap through XSLT stylesheets, which apply transformation rules to convert and reshape the data field by field. Mapping delivers several practical benefits for integration teams:

1. Data transformation: Converts source field structures to the target's expected format, handling differences in naming conventions, structures, and data types.
2. Field-level control: Lets you rename fields, reformat values, and apply conditional logic at the individual field level.
3. System independence: Decouples the source system’s data model from OneEnterprise’s internal model, so changes to one system do not break the other.
4. Reusability: A single mapping definition applies across multiple flows and triggers, reducing duplication.
5. Flexibility: XSLT supports conditional logic, string manipulation, date formatting, and other advanced transformations.
   

The Mapping band displays the list of units for the selected object. Each unit appears on a separate band showing the unit name and description. Selecting a unit opens the XSLT editor, where a drop-down list the available stylesheets from the Library module. You select a stylesheet, view and edit it in the editor, and save. To create a new stylesheet, the plus icon takes you to the XSLT Stylesheets section of the Library module, where you name and save the new stylesheet before returning to Mapping to apply it.

Settings

The Settings band contains automation settings that control how the connection processes data in operation. Each setting appears on its own band with a drop-down of available options. These settings are distinct from connection-level parameters — they govern the automated behavior of the connection during execution, such as how data is batched or scheduled. 

Subscription

The Subscription band is a read-only view that shows which entities subscribe to the selected automation. Each subscribing entity appears on its own band. This section exists for reference — it tells you how many systems downstream depend on this connection’s automation, which is useful context when evaluating the impact of a configuration change.

Trigger

The Trigger band displays the condition that initiates the connection’s workflow. A trigger is the mechanism that starts the integration process when specific criteria are satisfied. OneEnterprise supports four trigger types, and the band’s appearance adapts to whichever type is configured.

1. Timer Trigger: A Timer Trigger runs the connection at scheduled intervals.
   
2. HTTP Trigger: An HTTP Trigger fires when OneEnterprise receives an HTTP request at a specific endpoint. HTTP trigger supports the following authentication types:
   
1. No Authentication: Displays the endpoint URL with a copy icon. The Processing Queue section appears for asynchronous calls.
   
2. Basic Authentication: Displays the URL and a credentials table listing configured usernames and passwords. Passwords are masked by default and can be revealed using the eye icon. New credentials can be added, and existing ones can be updated or deleted.
   
3. Token Authentication: Displays the URL and the authentication token, each with a copy icon for easy reference. The Processing Queue section appears for asynchronous calls.
   
3. Queue Trigger: A Queue Trigger fires when data arrives in a designated queue. 
   
4. Subscription Trigger: A Subscription Trigger activates when a subscribed event occurs in a connected system. 

Value Mapping

Value Mapping is the mechanism that aligns discrete values between systems that use different terminology for the same concepts. A payment type called ‘Credit’ in one system might be ‘CRD’ in another. A store identifier of ‘Store A’ locally might map to a numeric location code in the ERP. Without value mapping, these mismatches would cause data to be rejected or misrouted. Value Mapping resolves them declaratively before data ever reaches the target system.

The Value Mapping band lists all objects available for mapping, each on its own band with a status drop-down. A search field and a Type filter (In Review or Release) help you find specific objects in larger projects. Expanding an object band reveals the mapping interface, which shows two columns side by side:

1. Publisher System: The source entity that provides data to OneEnterprise. The values in this column reflect what the external system sends.
2. OE Message (OneEnterprise): The internal representation in OneEnterprise. The values here are what OneEnterprise expects to store and route downstream.

Each row in the mapping interface is a pair of drop-downs — one per system — where you select the corresponding values. Rows can be deleted individually using the delete icon. Custom mapping rows can be added by typing a name into the text field at the bottom of the list and saving. 

Configure Objects for Integration

Configuring objects is the final step in establishing the project network. It tells OneEnterprise which data entities within each system are available for integration. Objects represent the types of records your integration will work with — for example, Accounts, Contacts, Orders, or Invoices. They can be standard entities provided by the connected system or custom objects defined within your organization’s instance.

When you configure objects, OneEnterprise retrieves the full list of available entities from the connected system. Select the objects relevant to your integration, then configure each object.

The pop-up interface

The Select Object and Data Flow Direction pop-up is a focused, two-field interface. It presents exactly what it needs to proceed — two drop-down menus and two action buttons — so you can make your selection and move forward without distraction.

Element	Description
Object drop-down	Lists all objects configured for the selected connection. Each object represents a data entity — such as a Business Partner, Sales Order, or Invoice — that this connection is set up to handle.
Flow Direction drop-down	Lists the flow directions supported by the object you selected. Available directions depend on how the connection was originally configured and may include inbound, outbound, or bidirectional options.
Proceed	Confirms your selection and opens the Edit Connection screen, scoped to the object and flow direction you chose.
Cancel	Closes the pop-up without opening the Edit Connection screen. No changes are made to the connection.

Object selection

The Object drop-down lists every data entity that the selected connection is configured to handle. The options you see reflect the objects that were defined when the connection was set up in the project network. Selecting an object tells OneEnterprise which entity’s settings to load in the Edit Connection screen.

Object selection also determines what appears in the Flow Direction drop-down. Different objects within the same connection can support different flow directions, so the Flow Direction options refresh based on whichever object you pick. If you are unsure which object to select, check the connection’s documentation or the Project Details view, which lists the objects configured for each system in the project network.

Flow direction selection

Flow direction defines the role each entity plays in a given data exchange:

1. Inbound: Data flows from the external system into OneEnterprise. The connected entity is the publisher, and OneEnterprise is the receiver.
2. Outbound: Data flows from OneEnterprise to the external system. OneEnterprise pushes processed data to the connected entity.
3. Bidirectional: Data moves in both directions. This direction appears when the object is configured to both send and receive data between the two entities.

The directions listed in the drop-down are limited to what is supported for the object you selected. Not every object supports every direction — the available options reflect the connection’s actual configuration. Selecting the correct flow direction is important: each direction has its own independent set of settings in the Edit Connection screen, including its own filter logic, mapping rules, trigger configuration, and error-handling policy.

If an expected flow direction does not appear in the drop-down, the object may not be configured for that direction in the project network. Review the connection setup in the Edit Project Network interface to add or modify supported flow directions.

Once objects are configured, they become available in the field mapper when your team builds integration flows for this project network. The object configuration is the bridge between the systems in the network and the flows that move data between them.