Like endpoints, connectors send and receive data between systems. Unlike Nextworld endpoints which require configuration of the request and response bodies, connectors have a user-friendly interface that allow you to use data mappings to select and filter for the fields and business data you want included. Connectors currently support several registrations, including:
- Batch data sync—Schedule or manually initiate a data sync which imports a copy of data from an external system, and imports it into a platform table. This data can then be manipulated or used in other processes.
- Real-Time data—View data from an external system in real-time within a platform application. This data is not saved or persisted in the platform.
- Logic invocation—Send business data and initiate a logic invocation within an external system.
Data sync
Use Batch Data Sync registrations to map external business data into an internal platform table. For example, you could configure a Batch Data Sync registration that imports data once a day from a J.D. Edwards financials table into an internal financials table. Then, you could build an interactive report over that data to view current financials data from the external platform.
Create a new table, or use an existing table, when you configure your data source registration. After you select an external table and populate the fields, select which fields you want included in your data sync, then map those fields to existing data items in your internal table. Or, if you created a new table, enter new data item names to create the appropriate data items while you map the fields.
After you create a data source registration in the connector configuration management record, another record is created in the Data Import Definitions application.
Data syncs can be manually run, or you can create a schedule for recurrent syncs to occur.
Real-time data
Use Real-Time Data registrations to show real-time external business data within an internal platform application. Real-time data is read-only and not stored or persisted in the underlying table. For example, you could configure a Real-Time Data registration to show business data subjected to compliance regulations which don't allow you to export business data.
You can create a Real-Time registration over an external orchestration, or a data service. If you create a registration over an external orchestration, you are registering a logic invocation from the external system to an internal platform table. Data service registrations are registering an external table to an internal table.
When you create your registration, the system also creates a new table to hold the incoming data. If you ever delete the registration, the table is also removed. After you select an external table and populate the fields, select which fields you want included, then map those fields to internal data items you want included in your table. If there are no existing data items for the external fields, you need to create them in the Data Item Definitions application.
Build an application over the internal platform table associated with the registration to view the real-time data.
Initiate logic
Use logic registrations to initiate logic in external systems, then map data from those external systems back into a logic block within the platform. For example, you could configure a logic registration that sends AR Invoice data into the J.D. Edwards platform. When the data is sent, a logic orchestration is called within their platform to insert that data into one of their tables. After the data has been assigned to their table and fields, they send an output back to Nextworld with the document number where our invoice data was recorded.
Select a registration type then load the available logic from the external system. When you name the logic registration and save the record, a logic block, input, and output table are automatically created to hold the external data.
After the logic is created, you can open the detail of that record to review and configure the input and output mappings between the external and internal systems. The external system fields are automatically available within the input and output mappings of the detail, but you must map internal fields to those external fields. When you select internal field names in the subtables, they are automatically added to the underlying table.
In addition to the outputs specific to the external system, all Logic Registration logic blocks have a generic Value output included with them called LogicInvocationSuccess. This value provides an overall success or failure indication at runtime, and can be used in conjunction with the logic block's message list in order to pivot the calling logic based on whether the external system's logic succeeded.
Connector applications
There are multiple applications used for connector configuration, including:
- Connector Catalog application—Review the external systems which you can connect to, as well as the supported versions. Catalog records are controlled and shipped by the platform. Learn more in Connector Catalog application.
- Connector Credentials Setup application—Configure the authorization type, connection URL, and credentials for the system you want to connect with. Connector credential records are created by system administrators in their development environments. Learn more in Connector Credentials Setup application.
- Connector Configuration Management application—Configure the details of the connector, such as the data mappings and schedule for the data sync. Reference the connector catalog record and connector credentials, then configure the data source registration or logic registration. Connector management records are created by system administrators in their development environments. Learn more in Connector Configuration Management application.
- Connector Sync Inquiry application—Review the status of any syncs which have been attempted for connectors. You can also view sync status records and summary information on the Connectors dashboard. Learn more in Connector Sync Inquiry application and Review connector sync statuses with the Connectors dashboard.
Learn more in Connector configuration overview.
Review connector sync statuses with the Connectors dashboard
System administrators use the Connectors dashboard to monitor the status of sync attempts from configured connectors. For example, if an environment has a scheduled sync configured to send and retrieve data from J.D. Edwards, system administrators could use the Connectors dashboard to ensure each sync was successful, review the name of the table or logic block where the data is being held, and open up the details of a record to view any error messages.
Connectors send and receive data between the platform and an external system tables and logic blocks. Learn more in Connectors.
The Connectors dashboard is made up of the following dashboard cards:
- Recent Syncs by Data Source—Shows a summary view of data syncs based on the data source registration. The summary view provides the time of last attempted sync, status of the sync, and the name of the table being synced.
- Data Sync Execution—Shows records for every sync attempted by a connector. Each record provides the sync status, connector name, data import run number, and the name of the table being synced.