Prerequisites for Creating a Connection

You must satisfy the following prerequisites to create a connection with the Oracle Sales Cloud Adapter.

Prerequisite Description For More Information
Subscribe to Oracle Sales Cloud. This action enables you to create an Oracle Sales Cloud user account with the correct privileges. You specify this user account when creating an Oracle Sales Cloud Adapter connection on the Connections page. See Oracle Sales Cloud.
Upload a security certificate. Certificates validate outbound SSL connections. If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown. In that case, you must upload the appropriate certificate. A certificate enables Oracle Integration to connect with external services. See Upload an SSL Certificate.
Obtain the necessary Oracle Sales Cloud service catalog service WSDL URL, event catalog URL, or interface catalog URL. You must specify a mandatory Oracle Sales Cloud Adapter service catalog service WSDL (for accessing business objects) and optionally an event catalog URL (for accessing event subscriptions) or interface catalog URL (for accessing Oracle Fusion Applications REST API resources) on the Connections page. See Obtain the Oracle Sales Cloud Adapter Service Catalog Service WSDL, Event Catalog URL, or Interface Catalog URL.
Subscribe to events in Oracle Sales Cloud. To subscribe to events with Oracle Sales Cloud, you must perform a number of configuration steps. See Configure Oracle Sales Cloud for Event Subscriptions and Enable Event Subscriptions in Oracle Sales Cloud.
Use groovy scripts in integrations. You can use the groovy script editor to create scripts to invoke integrations. See Integrate Groovy Scripts.

Obtain the Oracle Sales Cloud Adapter Service Catalog Service WSDL, Event Catalog URL, or Interface Catalog URL

You must obtain a required service catalog service WSDL (for accessing and configuring the inbound and outbound adapter to use either business objects or business services) and optionally an event catalog URL (for accessing and configuring the inbound adapter to use event subscriptions) or interface catalog URL (for accessing and configuring the outbound adapter to use Oracle Fusion Applications REST API resources). You specify the necessary WSDL and URLs in the Connection Properties dialog.

You specify the appropriate property values in the Oracle Sales Cloud Adapter Connection Properties dialog on the Connections page.
Description of ics_osc_connect_props.png follows
Description of the illustration ics_osc_connect_props.png

The following sections describe how to obtain the service catalog service WSDL, event catalog URL, and interface catalog URL:

For Fusion Applications Releases 10 Through 12

Obtain the Oracle Fusion Applications Releases 10 through 12 service catalog service WSDLs, event catalog URLs, and interface catalog URLs through the following methods.

Obtain the Service Catalog Service WSDL For Releases 10 Through 11

WSDL Requirements Where Do You Get the WSDL?

The URL must be that of a service catalog service WSDL. The service catalog service is a Fusion Application service that returns a list of external services available for integration. It allows clients to retrieve information about all public Fusion Application service endpoints available for that instance.

The service catalog service enables clients to retrieve information about all public Oracle Fusion Application service endpoints available for that instance. The information it returns is specific to the particular cloud instance and also reflects the new services that may have been introduced in patches applied to the instance. This service is used to programmatically discover the SOAP services available on the cloud instance and retrieve the necessary metadata to invoke the SOAP services to manage business objects.

The developer creating an Oracle Sales Cloud connection must work with the Oracle Sales Cloud service administrator to get the concrete WSDL URL for the service catalog service provisioned for the specific SaaS application.

This section describes how to derive the external virtual host and port for a tokenized service catalog service WSDL. The topology information in the Topology Registration setup task contains the external virtual host and port for the domains and applications. The following instructions describe the steps for deriving the values using the service catalog service WSDL URL as an example: https://atf_server:port/fndAppCoreServices/ServiceCatalogService.

To access the Review Topology page, the ASM_REVIEW_TOPOLOGY_HIERARCHY_PRIV entitlement must be granted to the user’s job role. The entitlement is granted to the ASM_APPLICATION_DEPLOYER_DUTY duty role, which is inherited by the duty roles ASM_APPLICATION_DEVELOPER_DUTY and ASM_APPLICATION_ADMIN_DUTY.

If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role. Contact your cloud instance security administrator for assistance.

  1. Log in to the cloud instance.

  2. Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.

  3. Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.

  4. Click the Detailed tab in the middle of the window.

    The tab shows the list of domains configured in the cloud instance.
    Description of osc_get_wsdl_detals.png follows
    Description of the illustration osc_get_wsdl_detals.png

  5. Map the token name for the service path value to the domain name in the Topology Manager:
    Token Name in Service Path Domain Name
    atf_server CommonDomain
    crm_server CRMDomain
    fin_server FinancialDomain
    hcm_server HCMDomain
    ic_server ICDomain
    prc_server ProcurementDomain
    prj_server ProjectsDomain
    scm_server SCMDomain
  6. Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain. In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.
    Description of osc_get_wsdl_detals2.png follows
    Description of the illustration osc_get_wsdl_detals2.png

  7. Replace the domainName_server:PortNumber with the external virtual host and port identified in the previous step. For example:

    https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl

Obtain the Service Catalog Service WSDL For Release 12

To obtain the physical endpoint of your instance, perform the following steps:
  1. Log in to the Fusion Applications home page. For example:

    https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome

    Where acme is the system name and fs is a Fusion Applications domain.

  2. Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ServiceCatalogService?WSDL. For example:

    https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ServiceCatalogService?WSDL

Obtain the Event Catalog URL

You must know the customer relationship management (CRM) URL format to access the CRM application user interface. Follow the URL format to determine the event catalog URL. For example, if the CRM URL format is:

https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHome

Then the event catalog URL is:

https://fusxxxx-crm-ext.us.oracle.com/soa-infra

The event catalog URL https://host:port/soa-infra is a partial URL and must only be provided on the Connections page. Do not open this URL with a browser. If you do, you receive a Page not found error. The adapter does not access this URL directly. Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).

To check the public events defined in the catalog, enter the following complete URL in a browser:

https://host:port/soa-infra/PublicEvent/catalog

Obtain the Interface Catalog URL

The interface catalog URL is formatted as follows. Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.

https://host:port_for_the_common_domain/helpPortalApi/otherResources/latest/interfaceCatalogs

For Fusion Applications Releases 13 and Later

Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.

Obtain the Service Catalog Service WSDL

To obtain the physical endpoint of your instance, perform the following steps:
  1. Log in to the Fusion Applications home page. For example:

    https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome

    Where acme is the system name and us6 is the data center.

  2. Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ServiceCatalogService?WSDL. For example:

    https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDL

Obtain the Event Catalog URL

Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint. You must switch to the new consolidated endpoint that conforms to the following naming pattern:
https://systemName.fa.dcsn.oraclecloud.com/...
You must switch to the consolidated endpoint immediately after upgrading to Release 13. Newly provisioned instances using Release 13 only have the consolidated endpoint available. In Release 13, multiple domains are consolidated. You must specify the domain in the URL. For example, if specifying the fa domain, the URL looks as follows:
  1. Copy the following URL:

    https://acme.fa.us6.oraclecloud.com/
  2. Append soa-infra to the end of the URL:

    https://acme.fa.us6.oraclecloud.com/soa-infra

Obtain the Interface Catalog URL

The interface catalog URL is formatted as follows. Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.

https://host:port_for_the_common_domain/root_context/otherResources/latest/interfaceCatalogs
Where root_context is one of the following root context values:
  • ERP/SCM pillar:

    • fscmRestApi: for ERP/SCM REST services (includes PPM/Procurement).

    • fscmService: for ERP/SCM non-REST services, such as SOAP services.

  • HCM pillar:

    • hcmRestApi: for HCM REST services.

    • hcmService: for HCM non-REST services, such as SOAP services.

  • CRM pillar:

    • crmRestApi: for CRM REST services.

    • crmServices: for CRM non-REST services, such as SOAP services.

Configure Oracle Sales Cloud for Event Subscriptions

You must create a CSF key to subscribe to both standard and custom events in Oracle Sales Cloud. This key is required by the event handler framework when it invokes the integration. The credentials of the integration are managed by the CSF key. Create the CSF key in Oracle SOA Composer.

Note:

  • There is only one SOA instance in Release 13.

  • The Oracle Integration password may expire periodically. Your application administrator must contact the Oracle Integration administrator to get the refreshed user credentials. The application administrator must update the CSF key when this password is refreshed.

Ensure that you specify the following information correctly when creating the CSF key:
  • Create the CSF key with a name that is a combination of the Oracle Identity Cloud Service service ID and the name of the integration instance.

    1. In the upper right corner of Oracle Integration, click user name menu, then select About.

    2. Copy the Identity Domain value (for example, idcs-638a2ce020e60c2881) and the Service Instance value (for example, oic1575).

    3. Assemble the CSF key value with the identity domain first and the service instance second (no space in between): idcs-638a2ce020e60c2881oic1575.

  • Create the CSF key with the Oracle Integration user account with which you log in to Oracle Integration and not the user name created when you subscribed to Oracle Sales Cloud.

  • Ensure that the CSF key password has not expired.

  1. Log in to Oracle SOA Composer with a user that has the SOA administrator role. Obtain the hostname and port from your administrator.

    For example, in Release 12:
    http://Sales_domain_URL:port/soa/composer
    For example, in Release 13:
     https://acme.fa.us6.oraclecloud.com/soa/composer
  2. Click Manage Security.

  3. Add the CSF key name. The name must be a combination of the Oracle Identity Cloud Service service ID and the name of the integration instance.

  4. Provide the username and password that you enter to log in to Oracle Integration. Do not enter the username and password created when you subscribed to Oracle Sales Cloud.

    The Oracle Integration user must exist in Oracle Integration and have been assigned the ServiceUser role.

    The CSF key entry in the Oracle Sales Cloud infrastructure stores the Oracle Integration credentials used by Oracle Sales Cloud. When Oracle Fusion Applications send outbound requests to Oracle Integration (at runtime), it sends the credentials (username and password) of this account for authentication.

  5. Click Register.

Enable Event Subscriptions in Oracle Sales Cloud

Before you can subscribe to events with the Oracle Sales Cloud Adapter, you must perform a series of configuration tasks. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with Oracle Sales Cloud in this integration.

Verify the Source System Record in Oracle Sales Cloud

The integration is designed to work with Oracle Sales Cloud Release 10.

To verify the source system record in Oracle Sales Cloud:

  1. Log in to an Oracle Sales Cloud instance with a user with system administrator privileges.

  2. Navigate to the Setup and Maintenance page.

  3. Select the All Tasks tab.

  4. Enter Manage Trading community Source System in the Name field, and click Search.

  5. In the Search Results section, click the icon under Go to Task.

    The Manage Trading Community Source Systems page is displayed.

  6. Select Starts with from the Code drop-down menu.

  7. To the right of Starts with, enter a value in the field, then click Search. For this example, RNOW is entered.

  8. In the Search Results section, verify the value you entered (for this example, RNOW) is displayed in the Code column and ensure the Enable for Trading Community Members checkbox is selected. If the Enable for Trading Community Members check box is not selected, then perform the following steps:

    1. Select the RNOW row.

    2. Click the Edit icon.

    3. Select the Enable for Trading Community Members checkbox.

Create the Source System Record in Sales Cloud

To create the Source System Record in Sales Cloud:

If the Source System definition RNOW record is not found in the Sales Cloud instance, then follow the steps below to create one:

  1. Log in to the Oracle Sales Cloud instance with a user with system administrator privileges.

  2. Navigate to the Setup and Maintenance page.

  3. Select the All Tasks tab.

  4. Enter Manage Trading community Source System in the Name field, and click Search.

  5. In the Search Results section, click the icon under Go to Task.

    The Manage Trading Community Source Systems page is displayed.

  6. Select Starts with from the Code drop-down menu.

  7. Enter RNOW in the field, then click Search. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which Oracle Sales Cloud is communicating.

  8. Under Search Results, click the New icon.

  9. On the Create Source System page, fill in the values as follows. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which Oracle Sales Cloud is communicating.

    • Code field: Enter RNOW.

    • Name field: Enter Service Cloud.

    • Description: field: Enter a description. For example:

      Maintains cross references between the Oracle Fusion Applications database and records imported using comma-separated files.
    • Enable for Trading Community Members checkbox: Select the checkbox.

  10. Click Save, then click Close.

Verify Source System Entities

To verify source system entities:

  1. Navigate to the Setup and Maintenance page.

  2. Select the All Tasks tab.

  3. Enter Manage Source System Entities in the Name field, and click Search.

  4. In the Search Results section, click the icon under Go to Task.

    The Manage Source System Entities page is displayed.

  5. From the Source Systems for Trading Community Members list, select Service Cloud (RightNow). For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which Oracle Sales Cloud is communicating.

  6. In the Service Cloud (RightNow): Entities section, ensure that the Address, Contact Points, and Parties checkboxes are selected.

Enable the Trading Community Events Profile Option

This profile option only applicable to Trading Community Architecture (TCA) objects such as Accounts and Contacts. If the profile option is set to No out of the box, the events for the Accounts and Contacts objects are disabled. The rest of the objects do not require any profile option and are enabled to raise business events out of the box.

To enable the trading community events profile option:

  1. Navigate to the Setup and Maintenance page.

  2. Select the All Tasks tab.

  3. Enter Manage Trading Community Common Profile Options in the Name field, and click Search.

  4. In the Search Results section, click the icon under Go to Task.

    The Manage Trading Community Common Profile Options page is displayed.

  5. Select HZ_ENABLE_EVENT_TRACKING.

    The Manage Trading Community Common Profile Options page for the HZ_ENABLE_EVENT_TRACKING page is displayed.

  6. In the HZ_ENABLE_EVENT_TRACKING:Profile Values section, set the Site level Profile Value to Yes.

  7. Click Save, then click Close.

  8. On the Manage Trading Community Common Profile Options page, select HZ_INVOKE_OBJ_WF_ON_TRACKING.

    The Manage Trading Community Common Profile Options page for the HZ_INVOKE_OBJ_WF_ON_TRACKING page is displayed.

  9. In the HZ_INVOKE_OBJ_WF_ON_TRACKING: Profile Values section, set the Site level Profile Value to Yes.

  10. Click Save, then click Close.

Create an Integration User Account

To invoke an Oracle Sales Cloud service catalog or event catalog web service from Oracle Integration, you create a separate user.

To create the integration user account:
  1. Log in to Oracle Sales Cloud with a user with system administrator privileges.

  2. Navigate to Navigator > My Team > Manage Users.

    The Manage Users page is displayed.

  3. Click Manage Users.

  4. Click the Create New User icon beside Show Photo.

  5. Enter the following information, and click Save.

    Field Description
    Last Name

    Enter CUSTOMER_OIC_INTEG_USER

    Email

    Enter a valid email address.

    Hire Date

    Enter the date.

    User Name

    Enter CUSTOMER_OIC_INTEG_USER.

    Person Type

    Enter Employee.

    Legal Employer

    Select a valid legal organization.

    Business Unit

    Select a valid business unit.

    Send user name and password

    Select this checkbox.

    User Login

    Enter CUSTOMER_OIC_INTEG_USER.

    Password

    Enter a password for the username.

    A notification email is sent to the email address after the user is created.

  6. Log out of Oracle Sales Cloud.

  7. Log in to the Oracle Sales Cloud instance with CUSTOMER_OIC_INTEG_USER and the temporary password provided in the notification email.

  8. Change the password after logging in initially.

    The Oracle Sales Cloud page appears.

  9. Log out of Oracle Sales Cloud.

Assign Integration Roles

You associate a user with roles and privileges in Oracle Authorization Policy Manager on the Oracle Entitlements Server for Releases 10 and 11. If using Releases 12 and later, you use the Security Console to manage users and roles.

You can configure an Oracle Integration instance to use the Username Password Token security policy to access the resources in an Oracle Sales Cloud Adapter instance.

An Oracle Sales Cloud Adapter instance exposes service catalogs and event catalogs to Oracle Integration. These resources are secured in the Oracle Sales Cloud Adapter. You need to assign the required roles and privileges to a user.

Note:

For prebuilt integrations, you must use the name CUSTOMER_OIC_INTEG_USER. In prebuilt integrations, connections and filter expressions for echo suppression refer to CUSTOMER_OIC_INTEG_USER as the user name. For new integrations, the user name can be anything.

Role Description

ALL_INTEGRATION_POINTS_ALL_DATA

Starting with release 12, this role is no longer supported. When existing customers upgrade to release 12, users with this role continue using it, although it is hidden from the Security Console. If you create a new integration user in release 12 or later, you cannot assign this role.

Customer Relationship Management Application Administrator

This role is supported in releases 12 and later.

SOAOperator

The SOA Operator role.

FND_MANAGE_CATALOG_SERVICE_PRIV

Role for managing the web services catalog.

Additional roles may be required per each interface requirement.

Note:

You must have administrator privileges in Oracle Authorization Policy Manager to perform the following steps.

Assigning Integration Roles in Releases 12 and Later

Use the Security Console to manage application security such as roles, users, certificates, and administration tasks. Access to the Security Console is provided by the predefined Security Manager role. Access the Security Console in the following ways:

For example, the Roles page for the Integration Specialist user looks as follows:

Description of int_special.png follows
Description of the illustration int_special.png

See Oracle Cloud Applications Security Console of Cloud Securing Oracle Sales Cloud.

Assigning Integration Roles in Releases 10 and 11

  1. Log in to Oracle Authorization Policy Manager.

  2. Under Search, select Users from the For dropdown list.

  3. Enter CUSTOMER_OIC_INTEG_USER (for prebuilt integrations) or any name (for new integrations) in the Search field, then click the Search icon.

  4. Select that name in the search results, then click the View icon.

  5. On the username tab (CUSTOMER_OIC_INTEG_USER or whatever name you created), click the Application Role Assignments subtab.

  6. Click Map.

  7. In the Map Application Roles to User dialog:

    1. Select crm from the Application Name dropdown list.

    2. Select Contains from the Role Name dropdown list, enter ALL_INTEGRATION_POINTS_ALL_DATA (for releases 11 and earlier) or Customer Relationship Management Application Administrator (for releases 12 and later) in the Role Name field, and then click Search.

    3. Select ALL_INTEGRATION_POINTS_ALL_DATA (for releases 11 and earlier) or Customer Relationship Management Application Administrator (for releases 12 and later) in the search results, then click Map Roles.

      The role is mapped for the user under crm.

  8. Click Map.

  9. Perform the following steps in the Map Application Roles to User dialog.

    1. Select hcm from the Application Name dropdown list, and repeat steps 7.b, and 7.c.

    2. The role is mapped for the user under hcm.

  10. Click Map.

  11. Perform the following steps in the Map Application Roles to User dialog.

    1. Select fscm from the Application Name dropdown list, and repeat steps 7.b, 7.c.

      The role is mapped for the user under fscm.

  12. Click Map.

  13. Perform the following steps in the Map Application Roles to User dialog.

    1. Select soa-infra from the Application Name dropdown list.

    2. Select Contains from the dropdown menu next to Display Name.

    3. Enter SOA Operator in the Display Name field, and then click Search.

    4. Select the SOA Operator role in the search results, then click Map Roles.

      The role is mapped to the user under soa-infra.

  14. On the username tab (CUSTOMER_OIC_INTEG_USER or whatever name you created), click Find Policies at the top-right corner of the page

  15. In the Choose an Application dialog, select fscm and click OK.

    The Search Authorization Policies tab is displayed.

  16. Click the New icon under Functional Policies on the Search Authorization Policies page.

  17. On the Untitled tab, enter Policy for manage services catalog in the Name field.

  18. Ensure your username (CUSTOMER_OIC_INTEG_USER or whatever name you created) is listed under Principals. If the use is not listed under Principals, then click + next to Principals.

  19. Perform the following steps in the Search Principal dialog.

    1. Select the Users tab.

    2. Select Starts With from the User Name dropdown list, enter the user name (CUSTOMER_OIC_INTEG_USER or whatever name you created) in the User Name field, and then click Search.

    3. Select the user name in the search results, then click Add Selected.

    4. Click Add Principals.

  20. Select All next to Match under Principals.

  21. Click + next to Targets.

  22. In the Search Target dialog, click the Entitlements tab, then select Starts With from the Name dropdown list.

  23. Enter FND_MANAGE_CATALOG_SERVICE_PRIV, then click Search.

  24. Select Manage Webservices catalog in the search results, then click Add Selected.

  25. Ensure Manage Webservices catalog is added onto Selected Targets.

  26. Click Add Targets.

    A new Policy for manage services catalog is added to the user.

  27. Click Save on the Untitled tab.

  28. Sign out from Oracle Authorization Policy Manager.

Enable Echo Suppression Filters

During bidirectional object synchronization, echoes are generated. For example, an event triggered in Oracle Sales Cloud is synchronized through Oracle Integration to Oracle Service Cloud (with the Oracle RightNow Adapter), which then triggers an event in Oracle Service Cloud and then back to Oracle Sales Cloud, and so on. Oracle Integration-based integrations use echo suppression to prevent unwanted update or create events (the echoes) from returning to the source application.

Filtering is used at the source application together with a LastUpdatedBy attribute in the record payload. In prebuilt integrations, Oracle Integration uses the Oracle Sales Cloud username created as part of the prebuilt integration setup to invoke every API of the application.

While the filtering is defined in Oracle Integration, it occurs in the event handler framework at activation/subscription time.

The Oracle Sales Cloud event handler framework evaluates the echo suppression expression after the internal event has been enriched to prevent the echo payload push to Oracle Integration.

Integrate Groovy Scripts

The Oracle Sales Cloud Adapter inbound endpoint WSDL interface supports the use of concrete values for custom business objects in the WSDL in place of xsd:anyType parameters. This feature enables you to use the groovy script editor to create scripts to invoke integrations. The groovy script editor is unable to recognize xsd:anyType parameters.

Perform the following high level steps from the CRM Fusion Home page (that is, the Fuse user interface) to integrate the groovy script.

Note:

If you have existing integrations with inbound endpoints (with custom business objects having xsd:anyType) generated using an Oracle Integration version prior to 16.3.3 and want to use groovy scripts, the integration must be re-edited and all artifacts must be generated again.
  1. Create a sandbox environment in Oracle Sales Cloud.

    1. In the upper right corner, select Settings > Manage Sandboxes.

    2. Create a sandbox.

    3. Select Set as Active to activate the sandbox.

  2. On the desktop, click Tools > Application Composer.

  3. Register the Oracle Integration web service.

    1. Click Web Services.

    2. Click the icon to create a new web service connection.

    3. Enter the name and WSDL URL, then click Read WSDL.

    4. Complete the other fields on the page, then save and close the page.

  4. Create the object function to invoke the process method of the web service.

    1. In the left navigation pane, click Object Workflows.

    2. Expand Objects > Custom Objects > CommonObject > common_object_name, then select Server Scripts.

    3. From the Actions dropdown list, select Add.

    4. Enter a function name and select a return value (for example, void).

    5. On the right side of the page, click Show/Hide Function Palette.

    6. Click Web Services.

    7. With the process function selected, click Insert.

      The Edit Script field is partially populated with the code for invoking the process method of the web service.

    8. Complete the script to create the object function. For example:


      Description of ics_create_object_func.png follows
      Description of the illustration ics_create_object_func.png
    9. Click Validate.

    10. Save and close.

  5. Create the action to execute the function and expose the action as a button in the user interface.

    1. In the left navigation pane, click Actions and Links.

    2. From the Actions dropdown list, select Create.

    3. Enter a display label and name.

    4. From the Method Name dropdown list, select the method to use.

    5. On the right side of the page, select Script from the Source dropdown list.

    6. In the left navigation pane, click Pages.

    7. Click Desktop Pages.

    8. Click Edit Creation Page.

    9. In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.

    10. Save and close.

    11. Click the Home icon at the top of the page.

  6. Execute the action by clicking the button.