Split (1)

train · 94.6k rows

text stringlengths 65 20k
See Get the Template ID .6.Click NotificationMail , and in the New Value field, enter the email ID where you want to notify in case a run time exception/error occurs while running the integration.7.Click Submit .Appendix A Customer Relationship Management (CRM) Recipes A-81You get a confirmation message that the integration properties have been updated successfully.Activate and Run the Recipe After you've configured the connections and updated the integration properties, you can activate and run the recipe.1.On the Configuration Editor page, click Activate .2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .
6.Click NotificationMail , and in the New Value field, enter the email ID where you want to notify in case a run time exception/error occurs while running the integration.7.Click Submit .Appendix A Customer Relationship Management (CRM) Recipes A-81You get a confirmation message that the integration properties have been updated successfully.Activate and Run the Recipe After you've configured the connections and updated the integration properties, you can activate and run the recipe.1.On the Configuration Editor page, click Activate .2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.
7.Click Submit .Appendix A Customer Relationship Management (CRM) Recipes A-81You get a confirmation message that the integration properties have been updated successfully.Activate and Run the Recipe After you've configured the connections and updated the integration properties, you can activate and run the recipe.1.On the Configuration Editor page, click Activate .2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.
Activate and Run the Recipe After you've configured the connections and updated the integration properties, you can activate and run the recipe.1.On the Configuration Editor page, click Activate .2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.
1.On the Configuration Editor page, click Activate .2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.
2.On the Activate Package dialog, click Activate .You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .
You get a confirmation message that the integration is activated.3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .
3.On the Configuration Editor page, select the Oracle ServiceNow DocuSign User Doc SignIn integration, and click Run .4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.
4.In the resulting dialog, note the WSDL URL.You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.
You'll use this for configuring basic authentication in ServiceNow to invoke the integration in Oracle Integration from ServiceNow.Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.
Complete the post activation task of invoking the integration, and then test the recipe.Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.
Invoke the Integration from ServiceNow Test the Recipe Invoke the Integration from ServiceNow After activating the recipe, you must configure basic authentication to invoke the integration from ServiceNow.Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.
Configure basic authentication in your ServiceNow instance with the WSDL generated automatically while activating and running the recipe.This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.
This invokes the integration in Oracle Integration from ServiceNow.For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.
For detail information on how to configure basic authentication in ServiceNow, see Configure Basic Authentication in Using the ServiceNow Adapter with Oracle Integration .Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.
Test the Recipe Test the recipe to check that when a new user is created in ServiceNow, the user receives an email to electronically sign a compliance document.1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .
1.Create a new user in ServiceNow.a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.
a.Log in to your ServiceNow \| Developer instance as a system administrator.b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.
b.On the left navigation pane, enter User Administration in the Filter navigator field.The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .
The Self-Service menu displays all modules related to User Administration .c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.
c.In the Self-Service menu, under User Administration click Users .d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.
d.In the Users page, click New.e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.
e.Fill in the required information in the new user record form.Appendix A Customer Relationship Management (CRM) Recipes A-82Field Information to Enter User ID Enter a unique identifier for the new users ServiceNow log in user name.First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.
First Name Enter the users first name.Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.
Last Name Enter the users last name Department Select the users department from the look up list.Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .
Title Select the users job title.Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.
Click the Suggestion icon to select from a list of suggested titles.Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.
Email Enter the users email address.Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.
Note that this is the email address to which the compliance document will be sent to the user.f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.
f.Click Submit .The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.
The new user record appears at the top of the list in the Users page.2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.
2.Monitor the execution of the integration in Oracle Integration.a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .
a.In the Oracle Integration home page, click Monitoring , then Integrations , and then Tracking .b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.
b.In the Track instances page, you can see the integration flow being triggered and executed successfully.The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.
The recipe now sends the compliance document to the new user's email address that was specified in the new user record form in ServiceNow.3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.
3.Check if you received the compliance document from DocuSign in the specified email address, and you're able to access and sign it.a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .
a.Sign in to the email account that you specified in the ServiceNow new user form in step 1e.b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .
b.Check if you received an email to review and sign the compliance document.c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.
c.Open the email, and click REVIEW DOCUMENT .d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.
d.Select the I agree to use Electronic Records and Signatures check box.e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents in the Integration Store.
e.Select Continue to access the compliance document.f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents in the Integration Store.Oracle provides this recipe as a sample only.
f.On the compliance document, click the START tag on the left.You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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.
You're taken to the Signature field of the document.Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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.
Optionally, drag the START tag to the part of the document where you want to sign.g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.
g.Click the SIGN tag.h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.
h.In the resulting Adopt Your Signature dialog, verify if your name and signature is correct, and then click ADOPT AND SIGN .If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.
If needed, you can change the information.Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.
Enter your name in the Full Name field.Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.
Enter your initials in the Initials field.i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.
i.On the compliance document, click FINISH .j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.
j.In the dialog that lets you know that a copy of the signed document will be sent to your email address, click Continue .You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.
You get an email with the signed compliance document.Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.
Related Documentation Using the ServiceNow Adapter with Oracle IntegrationAppendix A Customer Relationship Management (CRM) Recipes A-83Using the DocuSign Adapter with Oracle Integration Send Documents from Salesforce to DocuSign Use this recipe to send documents attached to a Salesforce opportunity to DocuSign.Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.
Note: This recipe is available as Salesforce DocuSign \| Send Opportunity Documents 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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.
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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.
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 sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.
No support is provided for this recipe.Overview This recipe sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.
Overview This recipe sends all the documents attached to a Salesforce opportunity to DocuSign when the opportunity is moved to the Closed Won status in Salesforce.It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .
It uses the standard Salesforce Adapter and the DocuSign Adapter.To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.
To use the recipe, you must install the recipe package and configure the connections and other resources within the package.When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.
When an opportunity record closes with the status Closed Won in Salesforce, the integration flow of the recipe is triggered.It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.
It receives the opportunity ID from Salesforce and checks if the opportunity record contains any document attachments.If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.
If there are attachments, the integration flow retrieves those documents and sends them to DocuSign.In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .
In DocuSign, these documents are available within a new draft envelope.Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.
Note: The recipe sends a document from Salesforce to DocuSign only when the opportunity record containing the document is moved to the Closed Won status in Salesforce.The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.
The recipe sends only valid PDF documents from Salesforce to DocuSign.System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.
System and Access Requirements Oracle Integration, Version 21.1.2.0.0 (210129.2200.39447) or higher Salesforce DocuSign Developer instance An account on Salesforce with the Administrator role An account on the DocuSign Developer instance with the Administrator role Topics: Before You Install the Recipe Install and Configure the RecipeAppendix A Customer Relationship Management (CRM) Recipes A-84Activate and Run the Recipe Before You Install the Recipe You must perform the following configuration tasks on your Salesforce and DocuSign instances in order to successfully connect to these external systems using Oracle Integration and transfer documents from Salesforce to DocuSign.1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .
1.Configure Salesforce 2.Configure DocuSign Configure Salesforce To access Salesforce using Oracle Integration and retrieve documents attached to opportunities, you must perform certain configuration tasks on your Salesforce instance.Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .
Create a user account on Salesforce for Oracle Integration.You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.
You'll use the credentials of this user account while configuring the Salesforce connection in Oracle Integration.Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .
Also, identify your Salesforce instance type and your current Salesforce API version.In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.
In addition, create an outbound message to trigger the recipe in Oracle Integration, and create a workflow rule to send the outbound message when a Salesforce opportunity is moved to the status Closed Won .Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.
Finally, enable uploading attachments to records as Salesforce Files.Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.
Log in to your Salesforce instance as an Administrator and execute the following tasks.Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.
Note: The steps provided here apply to the Salesforce Classic UI.If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.
If you're using the Lightning Experience UI on your Salesforce instance, switch to the Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.
See Toggle or switch between Lightning Experience and Salesforce Classic .1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.
1.Create an API-enabled custom role.You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.
You'll assign this role to the user account you'll subsequently create for Oracle Integration.a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.
a.On the Salesforce Setup page: i.Expand Manage Users under the Administer section in the left navigation pane.ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.
ii.Click Profiles .b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.
b.On the Profiles page, click New Profile .c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .
c.On the resulting page: i.Select Standard User in the Existing Profile field.ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.
ii.Enter a name for the new profile, for example, API Enabled , and click Save .The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.
The new profile is now saved, and the Profile Detail page of the new profile is displayed.d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .
d.Click Edit on the Profile Detail page.e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.
e.On the Profile Edit page: i.Scroll to the Administrative Permissions section and ensure that the API Enabled check box is selected.Appendix A Customer Relationship Management (CRM) Recipes A-85ii.Scroll to the Standard Object Permissions section and perform the following actions.In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .
In the Accounts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.
Additionally, select the ViewAll check box.In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.
In the Contacts row, leave the Read , Create , Edit, and Delete boxes checked.Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.
Additionally, select the ViewAll check box.In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .
In the Price Books row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .
Additionally, select the Create , Edit, and Delete check boxes.In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .
In the Products row, leave the Read box checked.Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.
Additionally, select the Create , Edit, and Delete check boxes.iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.
iii.Scroll to the end of the page and click Save .2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.You're redirected to the Salesforce instance to set a password for the new user account.
2.Create a user account for Oracle Integration and assign the custom role created previously to this account.Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.You're redirected to the Salesforce instance to set a password for the new user account.e.Set a password and note down the same.
Note: If you have already created a user account for Oracle Integration, you can assign the API-enabled custom role to the existing account.a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.You're redirected to the Salesforce instance to set a password for the new user account.e.Set a password and note down the same.Subsequently, you're signed in to the Salesforce instance with the new account.Appendix A Customer Relationship Management (CRM) Recipes A-86Note: If you're shown the Lighting Experience UI, switch to the Salesforce Classic UI.
a.On the Profile Detail page of the API Enabled profile, click View Users .b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.You're redirected to the Salesforce instance to set a password for the new user account.e.Set a password and note down the same.Subsequently, you're signed in to the Salesforce instance with the new account.Appendix A Customer Relationship Management (CRM) Recipes A-86Note: If you're shown the Lighting Experience UI, switch to the Salesforce Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .
b.Click New User in the resulting page.c.On the New User page: i.Enter a first name and last name for the user, for example, Integration User05 .ii.In the Email field, enter a valid email address.The email address you enter is automatically populated in the Username field.Note down this user name.iii.In the User License field, select Salesforce .iv.In the Profile field, select the profile you created previously, that is, API Enabled .v.Scroll to the end of the page, ensure that the Generate new password and notify user immediately check box is selected, and click Save .The user account is now created, and a verification email is sent to the email address you provided for the account.d.Log in to the corresponding email account and click the Verify Account button in the email message from Salesforce.You're redirected to the Salesforce instance to set a password for the new user account.e.Set a password and note down the same.Subsequently, you're signed in to the Salesforce instance with the new account.Appendix A Customer Relationship Management (CRM) Recipes A-86Note: If you're shown the Lighting Experience UI, switch to the Salesforce Classic UI.See Toggle or switch between Lightning Experience and Salesforce Classic .f.Generate a security token for the new user account.

Subsets and Splits

No community queries yet

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