Split (1)

train · 94.6k rows

text stringlengths 65 20k
On the Case Fields page, you can see the new field added under the Case Custom Fields & Relationships section.Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.Appendix A Customer Relationship Management (CRM) Recipes A-352.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.
Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.Appendix A Customer Relationship Management (CRM) Recipes A-352.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.
1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.Appendix A Customer Relationship Management (CRM) Recipes A-352.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.
3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.
4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.
5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.
The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .
Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.
Configure the Oracle REST Jira Connection Configure the Oracle Salesforce Connection Configure the Oracle REST Jira Connection 1.On the Configuration Editor page, select Oracle REST Jira Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.
2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.
The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.
3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.
Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .
Connection URL Enter your Atlassian instance URL, for example, https://myinstance.atlassian.net/ .Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.
Enable two way SSL for outbound connections (Optional)Select No.4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.
4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.
Field Information to Enter Security Policy Leave Basic Authentication selected.Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.
Username Enter the email ID associated with your Atlassian account.Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .
Password Enter the API token you created in your Atlassian account.See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.
See Create an API Token in Your Atlassian Account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.
5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.
If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .
6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.
A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.
7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .
Click Save again if prompted.Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.
Configure the Oracle Salesforce Connection 1.On the Configuration Editor page, select Oracle Salesforce Connection .Appendix A Customer Relationship Management (CRM) Recipes A-362.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.
The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.
3.In the Connection Properties section, enter the following details.Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.
Field Information to Enter Select Salesforce.com Instance TypeSelect Production or Sandbox based on your Salesforce instance type.API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.
API Version Enter your current Salesforce API version.To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.
To obtain the API version, see Configure Salesforce .4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.
4.In the Security section, enter the following details.Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.
Field Information to Enter Security Policy Leave Salesforce Username Password Policy selected.Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.
Username Enter the user name of the account created for Oracle Integration on Salesforce.See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.
See Configure Salesforce .Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.
Password Enter the password of the account created for Oracle Integration on Salesforce.Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.
Note: To the password, you must also append the security token generated for the same account.5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.
5.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.
If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.
6.Click Test to ensure that your connection is successfully configured.In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .
In the resulting dialog, click Test again.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.
A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.
7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.
Click Save again if prompted.Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.
Activate and Run the Recipe After you've configured the connections, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .
1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.
In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.
A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.
Refresh the page to view the updated status of the integration.Appendix A Customer Relationship Management (CRM) Recipes A-37Note: The recipe's integration flow contains the following property: emailNotification : This integration property holds the email address to which notifications of errors in the integration's execution are sent.Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.
Optionally, you can add or update the value for this property after the integration flow has been activated.For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.
For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.
2.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.
a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .
b.Click Run , then click Submit Now .The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.
The Schedule Parameters page is displayed, where you can specify a value for the lastRun parameter.This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.
This parameter stores the date and time of the most-recent successful run of the integration flow.For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.
For the initial run, it contains a default value.The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.
The parameter's value is automatically updated after each successful run, and only the Jira issues created or updated after the date-time stamp stored as parameter's Current Value are processed by the integration in each run.If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .
If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm .Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.
Generally, no input is required.c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.
c.Click Submit on the Schedule Parameters page.You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.
You've now successfully submitted the integration for execution.Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.
Note: You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.
See Define the Integration Schedule.3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.
3.Monitor the execution of the integration flow in Oracle Integration.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.
a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.
b.Click Run , then click Track Instances .c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.
c.On the Track Instances page, you'll see the integration flow of the recipe being triggered and executing successfully.In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
In the first run, the recipe creates corresponding cases in Salesforce for all of your Jira issues.In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
In subsequent runs, it creates cases for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Salesforce cases.4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.
4.Log in to your Salesforce instance and check for the new (or updated) case records.a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.
a.On the Salesforce Setup page, click the Cases tab.Appendix A Customer Relationship Management (CRM) Recipes A-38Note: If you don't see the Cases tab on the Setup page, click the Plus icon to the right of your current tabs, and then click Cases .b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.
b.On the Cases Home page, select All Open Cases in the View field.Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.
Click Go if necessary.The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.
The cases created for Jira issues are displayed.c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.
c.Click a case number to view a case record.d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.
d.On the case's page, click the Details tab to view the associated Jira issue ID.Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.
Using the values in the Jira Issue ID fields of case records, you can verify if all the required cases have been created or updated.Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.
Related Documentation Using the Jira Adapter with Oracle Integration Using the Salesforce Adapter with Oracle Integration Create Zendesk Tickets for Jira Issues Use this recipe to create corresponding tickets in Zendesk for all Jira issues.Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.
Note: This recipe is available as Jira Zendesk \| Create Tickets for Issues in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.
No support is provided for this recipe.Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.
Overview This recipe creates a ticket in Zendesk for each Jira issue as per a schedule specified in Oracle Integration.It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .
It uses the standard REST Adapter and Jira Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.
To use the recipe, you must install the recipe package and configure the connections and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.
Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.
When triggered, in the first run, the integration flow reads all the issue records from the Jira instance and, in turn, creates corresponding ticket records in your Zendesk instance.In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.
In subsequent runs, it creates tickets for new Jira issues and also propagates updates made in earlier Jira issues to the corresponding Zendesk tickets.Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.
Basic data associated with Jira issues, such as issue type, summary, priority, description, status, and comments are synchronized between the two platforms.Appendix A Customer Relationship Management (CRM) Recipes A-39Note: For this recipe to execute successfully the Description field of Jira issues must not be blank.In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .
In the second and subsequent runs of the recipe, updates made to the descriptions of Jira issues aren't synchronized.System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.
System and Access Requirements Oracle Integration, Version 21.2.1.0.0 (210129.2200.39462) or higher Atlassian Zendesk An account on Atlassian with the Administrator role An account on Zendesk with the Administrator role At least one Jira project on your Atlassian account the project(s) can be in any of the Jira products (for example, Jira Work Management or Jira Software) At least one issue in your Jira project Topics: Before You Install the Recipe Install and Configure the Recipe Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Atlassian and Zendesk instances in order to successfully connect to these external systems using Oracle Integration and create tickets in Zendesk for Jira issues.1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.
1.Create an API Token in Your Atlassian Account 2.Configure Zendesk Create an API Token in Your Atlassian Account To access Jira from Oracle Integration and retrieve issue records, you'll require an API token associated with your Atlassian account.To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .
To create an API token: 1.Log in to your Atlassian account using the following URL: https:// id.atlassian.com .2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.
2.On the Start page, click Account Settings .3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.
3.Click Security on the left navigation pane.4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.
4.On the Security page, scroll to the API token section and click the Create and manage API tokens link.5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.
5.On the API Tokens page, click Create API token .Appendix A Customer Relationship Management (CRM) Recipes A-406.In the resulting dialog, enter a label for the new token, and click Create .A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.
A new API token is generated.7.Copy the token's value.Configure Zendesk You can create a user account on Zendesk exclusively for integration purposes.To avoid access-related issues, assign the administrator role to this account.You can use the credentials of this integration user account to access Zendesk using Oracle Integration and create tickets for Jira issues.For information on creating a new Zendesk user account with the administrator role, see Adding agents and admins .Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Jira Connection Configure the Oracle REST Zendesk Connection Note: Optionally, you can configure the following lookup tables in the package.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.