A recipe is a set of pre-configured assets that helps you efficiently implement common
Application Integration use cases. A recipe contains one or more assets, such as process
objects, app connections, and processes, which you can configure based on your specific use
case. Application Integration offers recipes for various business use cases, such as, GenAI,
industry solutions, business process automation, and data management automation, enabling you to
accelerate your workflows and drive real business value.
Copying recipes
You can copy an existing recipe to quickly create a process for an
Application Integration
use case. This saves time by eliminating the need to manually create
each asset from scratch. After you copy a recipe, you need to complete certain
configuration tasks to use it. For example, you must configure properties related to user
authentication and the runtime environment in app connections and processes, and then
publish the assets. You can further modify the assets based on your business use case.
Copying recipes provides a fast and reliable way to implement a common use case with
minimal effort.
Benefits of copying recipes
If you copy a recipe, it offers the following benefits:
You save time by eliminating the need
to manually create each asset from scratch.
You leverage community-created
recipes to solve similar use cases faster.
You simplify configurations by
focusing on key settings such as environment settings and authentication.
Creating and publishing your own recipes
In addition to using existing recipes, you can contribute to
Application Integration
Recipes by
creating your own to address specific business use cases. When you create a recipe, you
must provide basic details such as the recipe name, description, and intended use case.
After adding all necessary details and assets, you submit the recipe for review.
The recipe undergoes a review and approval process to ensure quality and accuracy. Once
approved, the recipe is published on the
Recipes
page. It then
becomes available to other users who can reuse it for similar business use cases.
Example use case
Imagine a scenario where you need to synchronize Dynamics 365 accounts and contacts with
Salesforce accounts and contacts. This workflow requires multiple assets such as two
process objects, three app connections, and three processes. Instead of manually creating
all these assets from scratch, you can use the Synchronize Dynamics 365 Accounts or
Contacts with Salesforce Accounts or Contacts recipe to achieve your use case with minimal
configuration. You can use the recipe as is or extend and configure it as per your
business use case.
The following image shows a sample process workflow that synchronizes Dynamics 365
accounts and contacts with Salesforce accounts and contacts.
ASK INFAPreview
