An Interface is the second main object in SKYVVA after the integration. The interface describes the structure of data to exchange between Salesforce and other applications. It has other property which defines the processing mode e.g. synchronous or asynchronous, batch or bulk, etc.
Important attributes to be considered while creating an Interface
| Fields | Description |
| Name | Mandatory field based on which interface is created. |
| Status | You should always set the status to deployment to make sure the interface activated. |
| Sequence | The sequence is automatically incremented as and when you create a new interface. Only 2 digits are accepted, which means the max value is 99. |
| Adapter | Select a corresponding adapter based on your requirement to connect to a legacy system or homegrown database or CSV file, let us say if you want to connect to the database, you need to select related Jdbc/Odbc Adapter. |
| Source Name | For inbound scenario, always a sObject name for ex: Account since we are either inserting or updating the SObject in salesforce. |
| Type | It could be Inbound or Outbound based on your requirement, Inbound is generally External system to SFDC and Outbound is from SFDC to any external legacy or homegrown systems. |
| Operation Type | Select the operation based on the Type. If you select the Type Inbound then Operation Type could be Upsert, Update, Insert, and Delete. If you select the Type Outbound then you must select the operation type: none or upsert |
| Connect with Middleware | Mainly used if you are connecting to any legacy system through middleware. For instance, if you want to connect to SAP through PO we can set this flag. |
| MetaData Provider | Specify the Provider where the message type belongs to. |
| Processing Mode | You can select the mode either synchronous or Asynchronous depending on business logic. |
| Bulk Mode | If this flag is checked, then the interface will run in a bulk mode using Salesforce BULK API. |
| Batch Mode | If this flag is checked, then batch processing activated and messages processed in bulk. Typically, baskets have created in SKYVVA. |
| Repository | Select the repository, which contains the message type to be used for the interface. This field is a control field for selecting the message type. If don’t set all message type from all repository is listed which is huge. |
| Search in Source/Target Message Type | The message type from the iRepository. You need to define first a message type in the iRepository. For the inbound interface, it is used as the source type. For outbound interface as target type. |
| Description | To give a meaningful description of your interface. |
Note
Important thing to note, only outbound interface requires an adapter.
For the outbound scenario, it could be a sObject name or IDoc-Bapi name or Database name or Filename based on the requirement.
Operation Type – ‘Query’ works for both directions ‘Inbound’ as well as ‘Outbound’
Interface List
The interface List includes operations for the following: Positional access — manipulates elements based on their numerical position in the list.
Artikel
- 3.1 Create and delete an Interface
- 3.2 Ichain
- 3.3 Inbound Setup
- 3.4 Outbound Setup
- 3.5 Runtime Configuration-General
- 3.6 Runtime Configuration-Inbound
- 3.7 SOQL Query for filter sObject
- 3.8 Alerting Setup
- 3.9 Bulk Setting
- 3.10 How to post the SKYVVA message Id on the application Subject
- 3.11 Query Editor
- 3.12 Generate Metadata
- 3.13 Inbound Posting Behavior
- 3.14 Handle request and response as a transaction for synchronous call
- 3.15 View chain definition in an interface as tree
- 3.16 How to Edit and Delete Istructure on interface related page.
- 3.17 “What to do with failed message” field?
- 3.18 Interface Operation Type
- 3.19 Bypassing message layer
- 3.20 Messages Board Tab on Interface Header Page
- 3.21 Init-Operations
- 3.22. Processing in transactional mode