The July 2024 release of Application Integration includes the following new features and enhancements.
Recipes
Application Integration provides several recipes that you can use to achieve common use cases. Recipes contain a package of pre-configured assets such as process objects, app connections, and processes that you can configure based on your use case.
With recipes, you can save time as you do not have to manually create multiple assets from scratch for an Application Integration use case. You can copy a recipe to quickly create a process for an Application Integration use case. After you copy a recipe, you need to complete certain configuration tasks to complete and run the process successfully. You can modify the assets further based on your business use case.
Application Integration provides the following recipes:
Synchronize Dynamics 365 Accounts or Contacts with Salesforce Accounts or Contacts
When an account or contact is created or updated in Dynamics 365, the process is triggered, and the account or contact details are synchronized with a Salesforce account or contact.
Synchronize Dynamics 365 Cases with ServiceNow Incidents
The process synchronizes cases that were created or updated during the previous day in Dynamics 365 with ServiceNow incidents.
Synchronize NetSuite Cases with Salesforce Cases
When a case is created or updated in NetSuite, the process is triggered, and the case details are synchronized with a Salesforce case.
Synchronize Salesforce Accounts with Dynamics 365 Accounts
The process synchronizes a Salesforce account with a Dynamics 365 account based on the Salesforce Account ID specified as an incoming parameter.
Synchronize Salesforce Cases with ServiceNow Incidents based on Platform Events
When a case is created or updated in Salesforce, a Salesforce platform event triggers the process, and the case details are synchronized with a ServiceNow incident.
Synchronize Salesforce Contacts with Database Contacts
The process synchronizes contacts that were created or updated in Salesforce with contacts in the JDBC Connector and the supported databases.
Synchronize Salesforce Contacts with ServiceNow Users
The process synchronizes a Salesforce contact with a ServiceNow user based on the Salesforce Contact ID specified as an incoming parameter.
Synchronize ServiceNow Incidents with Dynamics 365 Cases
The process synchronizes incidents that were created or updated during the previous day in ServiceNow with Dynamics 365 cases.
Synchronize Workday Hired Employees with ServiceNow Users
The process synchronizes employee accounts that were created or updated during the previous period in Workday with ServiceNow users.
Convert electronic health information from HL7 to FHIR
Application Integration provides the following recipes to convert electronic health information from HL7 to FHIR:
- Convert patient admission data from HL7 ADT A01 to FHIR R4
- Convert patient registration data from HL7 ADT A04 to FHIR R4
- Convert patient update information from HL7 ADT A08 to FHIR R4
- Convert laboratory order data from HL7 OML O21 to FHIR R4
- Convert general order entry data from HL7 ORM O01 to FHIR R4
- Convert unsolicitated observation result data from HL7 ORU R01 to FHIR R4
- Convert unsolicitated vaccination update data from HL7 VXU V04 to FHIR R4
GeminiAI Prompt Chaining
Use the recipe to design prompt chains and resolve them in sequence so that it provides the desired responses from a large language model (LLM).
GeminiAI Chat with History
Use the recipe to maintain chat history in a file and use it as context for the next user query and the large language model's (LLM) response.
GeminiAI Chat with File
Use the recipe to provide a file path and a user prompt, read the text from the file, and answer the user's questions based on the text using a Gemini Large Language Model (LLM).
Loan Processing with GenAI
Use the recipe to evaluate a loan request and approve or reject it based on the applicant's credit score.
Simple RAG Consumption With PineCone
Use the recipe to receive a query from the user, convert it into vectors, form the context, and return a comprehensive response using a Large Language Model (LLM).
For more information about these recipes, see the corresponding recipe guides.
Connectors
Application Integration provides the following new connectors:
Azure OpenAI Connector
Azure OpenAI Connector integrates APIs described using the OpenAPI specification with Azure services. Azure OpenAI Connector provides seamless interaction between your OpenAPI-defined APIs and various Azure services, enabling powerful integrations and automation.
Dynamics 365 Connector
Dynamics 365 Connector performs CRUD operations, such as create, read, update, and delete, on Dynamics 365 tables. You can use Dynamics 365 Connector to securely read data from and write data to Microsoft Dynamics 365. You can synchronize the data and easily schedule real-time Application Integration processes. This connector works with the Dynamics 365 API 9.2 version.
Gemini Connector
Gemini Connector provides advanced AI multi-modal content generation functionalities. Gemini APIs are used for content generation and embedding. Gemini Connector uses the API key to authenticate Gemini connection requests. You can perform various actions, such as content generation and embedding, separately or in batches, count the number of tokens for input content, and get information about a specific model or a list of models available through the Gemini API.
Marketo Connector
Marketo Connector performs CRUD operations, such as create, read, update, and delete, on Marketo entities. You can use Marketo Connector to connect with other systems or applications.
NetSuite Connector
NetSuite Connector performs CRUD operations, such as create, read, update, and delete, on NetSuite tables. You can use NetSuite Connector to securely read data from or write data to NetSuite.
OpenAI Connector
OpenAI Connector connects to OpenAI language models and AI technologies through APIs. You can use an OpenAI connection for сhat completions, file embeddings, and batch requests using an API key.
Pinecone Connector
Pinecone Connector interacts programmatically with a Pinecone account using Pinecone REST APIs and HTTP requests. You can use the Pinecone REST APIs to perform the following tasks:
- Query, fetch, update, upsert, or delete vectors.
- Get index statistics.
- Get a list of vector IDs and indexes.
ServiceNow Connector
ServiceNow Connector performs CRUD operations, such as create, read, update, and delete, on ServiceNow tables. You can use ServiceNow Connector to securely read data from and write data to ServiceNow, and to connect to any cloud application. You can synchronize the data and easily schedule real-time Application Integration processes.
For more information about these connectors, see the corresponding connector guides.
New Application Integration Home page
Application Integration has a new Home page for a better user experience. You can create a process, guide, app connection, human task, service connector, and process object by clicking the respective display panels on the new Home page. The page also displays panels that are available for the following purposes:
•To use recipes, which are pre-defined templates that will help you to quickly configure business flows
•To view all the projects and folders that were updated recently
•To view a summary of unpublished assets and recently updated assets
The Application Integration Home page is scaled to 100% zoom level by default.
The following image shows the new Application Integration Home page:
For more information about the Application Integration Home page, see Getting Started.
New user interface for creating app connections
Application Integration has a new app connection creation page. The page populates tiles in a grid view or table view based on one of the following options that you select:
•All. Lists all the native connectors and service connectors that are available in the organization.
•Native Connectors. Lists all the out-of-the-box connectors that are used to connect to third-party applications.
•Service Connectors. Lists all the custom-made connectors that are used to connect to third-party applications.
For more information about configuring app connections, see Connectors for Cloud Application Integration.
AMQP Connector
You can configure load balancing for AMQP connections that run on a Secure Agent cluster. Load balancing ensures that routes are distributed across different Secure Agent machines in a Secure Agent cluster, making each node perform better and take less time to operate.
Additionally, when you configure an AMQP connection, you can use the custom message ID to override the default JMS message ID. You must ensure that the message header contains the custom message ID.
For more information about configuring an AMQP connection, see AMQP Connector Guide.
Automatic field mapping based on names
In the Create step, Assignment step, Service step, and Subprocess step, you can automatically map the fields including complex process objects configured in the process.
Automatic field mapping saves time and effort because you do not have to manually perform field mappings.
Application Integration matches the best possible fields based on the field name and data type that are configured in the process. Informatica does not guarantee exact field matches. After the fields are mapped, you must manually verify if the mappings are correct.
For more information about automatic field mapping, see Design.
Publishing a process to API Center
After you save and publish a process, you can publish the process to API Center using the new Publish to API Center button in the process designer. You can then create an API, apply policies, and manage and monitor the API in API Center.
For more information about publishing a process to API Center, see Invoke.
Support for listener-based connectors on the Cloud Server
You can publish and run the following listener-based connections on the Cloud Server:
1Amazon SQS
2RabbitMQ
For more information about configuring these connections, see the respective connector guides.
Support for Databricks database using a data access service connector
You can use a Data Access Service (DAS) connector to connect to a Databricks database. When you connect to Databricks, you can use a personal access token (PAT).
For more information about creating a data access service connector to access data from a Databricks database, see Design.
Enforcing multipart requests in service connectors
You can enforce a multipart request in a service connector binding to combine one or more sets of data into a single body, separated by delimiters. You can upload attachments and transfer data of several types in a single request payload. For example, you can transfer a file along with a JSON object using a multipart request. This feature is available only for the POST, PUT, PATCH, and DELETE methods.
For more information about designing service connectors, see Design.
