Creating an Integration Interface
To create an integration interface, you need to use an action form for a business process, or an attribute form for managers. With these forms, you can verify that all required fields are included in the interface design. After you have specified the fields you want on the interface, you need to create an interface template (a CSV file). This template, along with the other details of the integration interface, is imported along with the BP or manager into Unifier.
Tips for a successful interface design
- Data elements that are marked as required fields on the validation form should be included in the integration interface and should have the direction set to Input or Both.
- Standard data elements can only have a direction of Output. Avoid using them if you plan to use CSV integration for input.
- Be sure all field labels on a form are unique. If your form contains two fields with the same label, Unifier will stop the integration and issue an error message. To avoid this, be sure that all field labels on a form are unique. For existing forms, either remove the duplicate from the integration interface, or change one of the duplicate labels to something unique. (Changing the label will affect all forms in which that field (data element) is used.
- You cannot override the template project currency using the Project/Shell Creator business processes.
- CSV import is only available for a Simple-type Project/Shell Creator business process.
- Microsoft Excel truncates csv files with 15 or more rows and drops the additional commas from the 15th row onwards, resulting in an error when you try to import the file. You can avoid this issue for users by placing a required field as the last column of the design, and therefore, avoid having empty columns at the end of the file.
- If you add new data elements to your forms after creating the integration interface, they will not automatically be added to your existing integration design; you must add them manually if you want to include them in the design.
- If you remove a data element from a form after creating the integration interface, the data element will not be automatically removed from the interface design; you must remove it manually to avoid an error.
- If you change the design of your integration interface, be sure to export the new version of the xml or csv template first, before importing new records.
- Unifier can update Workflow BP records with the workflow details, and uses the step action form for validation. This enables an integration user to use the workflow step form to validate, when creating or updating a Workflow BP record through the new Rest Services. Also, when an integration form is defined in a Workflow BP, the following note is displayed under the Validation Form drop-down field: Note: The Validation Form will be used for business process methods of REST Web Services V1 type. This note is not available for Non-workflow BP records and other attribute forms in uDesigner.
- Unifier does not preserve, or retain, the query conditions for BP pickers that have been enabled to receive values through any type of integration. Oracle recommends that you use BP data pickers instead of BP pickers. In addition, when you are using BP pickers ensure that the display element value is unique; otherwise, the integration will fail if multiple business process records with the same display element value exist.
In This Section
Creating an Integration Template
Last Published Monday, June 3, 2024