Oracle Cloud Connecting Cloud Applications with Oracle Self-Service Integration Cloud Service

Transcription

1 Oracle Cloud Connecting Cloud Applications with Oracle Self-Service Integration Cloud Service E July 2018

2 Oracle Cloud Connecting Cloud Applications with Oracle Self-Service Integration Cloud Service, E Copyright 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

3 Contents Preface Audience Documentation Accessibility Related Resources Conventions v v v v 1 Understanding Custom Cloud Apps Why Build an SSI Custom Cloud App? 1-1 Exploring the Developer Dashboard 1-3 Preparing to Create a Cloud App Definition and Instance 1-5 Accessing Common Connectivity Support in Integration Cloud Service Developing a Cloud App Definition Understanding a Cloud App Definition 2-1 Creating a Cloud App Definition from a Basic Template 2-4 Creating a Cloud App Definition from an Open API 2.0 File 2-5 Creating a Cloud App Definition from a Postman Collection File 2-6 Creating a Cloud App Definition Trigger 2-6 Creating a Cloud App Definition Action 2-8 Creating a Cloud App Definition Flow 2-9 Creating a Cloud App Definition Schema 2-11 Using Pseudo Code in a Recipe s Trigger and Actions 2-13 Completing the Cloud App Definition 2-13 Validating a Cloud App Definition 2-22 Activating a Cloud App Definition 2-24 Publishing a Cloud App Definition Managing Cloud App Definitions Editing a Cloud App Definition 3-1 Previewing Cloud App Instances for an Active Cloud App Definition 3-3 iii

4 Deactivating a Cloud App Definition 3-5 Deleting a Cloud App Definition 3-5 Working with Cloud App Definition Versions Working with a Cloud App Instance Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type 4-1 Creating a Cloud App Instance Using Basic Authentication 4-6 Creating a Cloud App Instance Using No Authentication Type 4-9 Testing a Cloud App Instance 4-11 Publishing a Cloud App Instance Managing Cloud App Instances Editing a Cloud App Instance 5-1 Deleting a Cloud App Instance Understanding Error Messages A App Definition Lint Checks V2 iv

5 Preface Audience Connecting Cloud Applications with Oracle Self-Service Integration Cloud Service provides information about how developers create cloud app definitions and cloud app instances. In addition, the developer administers custom cloud app instances and makes them available to users. The developer maintains the SSI instance that is unique to the organization. Connecting Cloud Applications with Oracle Self-Service Integration Cloud Service is intended for developers who create cloud app definitions and cloud app instances. In addition, the developer administers custom cloud app instances and makes them available to users. The developer maintains the SSI instance that is unique to the organization. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at ctx=acc&id=docacc. Access to Oracle Support Related Resources Conventions Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit lookup?ctx=acc&id=info or visit if you are hearing impaired. See these Oracle resources: Documentation for Oracle Self-Service Integration Cloud Service in the Oracle Cloud library on the Oracle Help Center. Oracle Cloud The following text conventions are used in this document: v

6 Preface Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. vi

7 1 Understanding Custom Cloud Apps Before you start developing your own cloud app instances, learn some of the basic concepts of custom cloud app development. Topics: Why Build an SSI Custom Cloud App? Exploring the Developer Dashboard Preparing to Create a Cloud App Definition and Instance Accessing Common Connectivity Support in Integration Cloud Service Why Build an SSI Custom Cloud App? Oracle Self-Service Integration custom cloud app support is provided for a developer who maintains the SSI service for an organization. What is a Custom Cloud App? What is a Custom Cloud App Definition? What is a Cloud App Instance? What is the Developer s Role? What is a Custom Cloud App? You can extend SSI to support more cloud-based services by creating custom cloud apps. A custom cloud app is defined by the cloud app definition and the cloud app instance. These cloud apps will appear in SSI so end users can access their features and data within SSI recipes. An SSI end user is presented with a catalog of cloud apps, known as the Cloud Apps catalog, and predefined recipes, known as Public Recipes. The following diagram shows how a custom cloud app definition and a custom cloud app instance provide support for a custom cloud app. 1-1

8 Chapter 1 Why Build an SSI Custom Cloud App? What is a Custom Cloud App Definition? A custom cloud app definition describes what operations are available to act on a specific target cloud application service. The operations are provided in two forms: CRUD operations on business objects and concepts exposed by the target cloud application service. Some examples are Create Opportunity, Update Contact, Delete Row, and Get Incidents Change events on business objects and concepts exposed by the target cloud application service. Some examples are New Opportunity Created, Contact Updated, Row Deleted, and New Received A custom cloud app definition is written in a format that SSI understands. This cloud app definition, referred to throughout this guide as an OCDL document, is created using Oracle s connector definition language (OCDL). What is a Cloud App Instance? The Cloud app instance allows SSI to communicate with an external cloud service instance (at a specific URL, for example) using the actions and data defined in the Cloud App Definition. A cloud app instance includes the configuration parameters to apply an OCDL document to a specific cloud app. You create the cloud app instance by configuring the login criteria based on the OAuth model used by the specific cloud app. What is the Developer s Role? As the developer and administrator, you maintain both the definitions and the instances that are used by your organization. Use this document to guide you through the process of creating and maintaining cloud app definitions and instances. 1-2

9 Chapter 1 Exploring the Developer Dashboard Exploring the Developer Dashboard The main Dashboard is augmented for the developer role to include two additional tabs: Cloud App Instances and Cloud App Definitions Cloud App Instances Cloud App Definitions Cloud App Instances You create a new cloud app instance when you need to authorize SSI to securely communicate with a custom cloud app at a specific location/url. The Cloud App Instances tab in your Dashboard shows all of the cloud app instances that you have created. You create new cloud app instances from here using New Cloud App Instance. You can sort the list of cloud app instances by: Name: Sort by the name you provided when you created the instance. Cloud App Definition: Sort by the cloud app definition that you used with that instance. Status: Sort by either active or draft. The status of each instance is displayed in the entry and is designated as: Active: This instance is available to you and can be used to create accounts and recipes. A cloud app instance is automatically activated when it s complete. Draft: This instance is incomplete. From the menu following actions: for each entry in My Cloud App Instances, you can choose the Edit: Opens the cloud app instance in the editor Publish to Catalog: Lets you publish the cloud app instance to the Cloud Apps catalog for all users. Note: This option is only enabled if corresponding app definition is already published. Otherwise, it s disabled. 1-3

10 Chapter 1 Exploring the Developer Dashboard Delete: Deletes the cloud app instance and stops all recipes that use it. You can open the Cloud Apps catalog to view all published cloud app instances. The published cloud app definitions are displayed in a separate section named Custom Built. When you open a custom built cloud app definition, the cloud app instances are displayed. Cloud App Definitions The Cloud App Definitions tab in your Dashboard shows all of the cloud app definitions that you have created. You create new cloud app definitions from here using New Cloud App Definition. The status of each cloud app definition is displayed in the entry and is designated as: Draft: This status gives you the ability to edit the cloud app definition. It is not available for testing. Active: This status means the cloud app definition is complete enough to be tested. You must explicitly activate a cloud app definition to test it. 1-4

11 Chapter 1 Preparing to Create a Cloud App Definition and Instance Published: This status means that the cloud app definition is visible by other SSI developers and enables them to create an associated cloud app instance. When a cloud app definition is active, you can initiate the following actions: Edit/View Create Instance Publish Deactivate Draft New Version Delete When the cloud app definition is a draft, you can initiate the following actions: Edit Activate Draft New Version Delete Preparing to Create a Cloud App Definition and Instance SSI lets you create your own cloud app definition that you can share with team members. Before you create that cloud app definition, it s good to do some pre-work. Gathering Data 1-5

12 Chapter 1 Preparing to Create a Cloud App Definition and Instance Base URL Criteria Understanding the Workflows Gathering Data You create a cloud app definition using the API from the cloud application you are extending SSI to support. You need information from that cloud application that you ll use in the SSI cloud app definition. Gather the information prior to creating a cloud app definition to ensure success. Create a developer account in the cloud application the cloud application that you want SSI to support. Read the API Documentation for the cloud app that you want SSI to support. Gather the account information, such as the authentication information, client ID, client secret, API key, Base URL, and other pertinent data. Base URL Criteria A Base URL is required for a cloud app definition and can be overridden in the cloud app instance. This value is used to resolve relative paths for this cloud app. The Base URL cannot be any of the following: Localhost All IPs belonging to ( /8) Broadcast IP Multicast IP to Class C private IP address ( Understanding the Workflows As you develop custom cloud app definitions and instances, you can use the following suggested workflows to get started. Private flows are followed as part of your development cycle. You can execute the development flow several times in order to refine the cloud app and, when satisfied, execute the publish flow. Create Definition > Validate > Save as a Draft Create Definition > Validate > Activate Update Definition > Validate > Save as Draft Before you publish a cloud app definition, you can save it as a draft and publish it later. An activated definition can be used to create a private cloud app instance. You might want to save an updated version as a draft that you can test. Publishing flows are used when you want to make your work visible to others. Create Definition > Validate > Activate > Publish This is the most typical workflow for creating a definition. A published cloud app definition is viewable by all users. 1-6

13 Chapter 1 Accessing Common Connectivity Support in Integration Cloud Service Create Definition > Validate > Activate > Create Instance > Create Recipe > Publish Update Definition > Validate > Activate > Create Instance > Publish Update Definition > Validate > Activate > Create Instance > Publish > Create Recipe A published cloud app instance is viewable by all users. You can update a cloud app instance, but it will affect active recipes. You can update a cloud app definition, but it will affect active recipes. Accessing Common Connectivity Support in Integration Cloud Service SSI Common Connectivity Support (CCS) is available in Oracle Integration Cloud Service. The connectivity is available under the Adapters tab in Integration Cloud. You must have administrator permissions to add the SSI Common Connectivity Support adapters to Integration Cloud. 1. Log in to Integration Cloud using your administrator credentials 2. Click CCS Registration from the Settings section of the left navigation pane. The CCS Registration wizard opens. 3. Enter the CCS API Endpoint. The CCS API Endpoint is in https format and includes a reference to ssi. 4. Enter the CCS Auth Endpoint. The CCS Auth Endpoint is in https format and includes a reference to idcs. 5. Enter your username and password in the next two fields. 6. Create a client app in Oracle Identity Service with the proper CCS scopes. 1-7

14 Chapter 1 Accessing Common Connectivity Support in Integration Cloud Service This will provide you with the Client ID and Client Secret. 7. Enter the Client ID and Client Secret. 8. Click Register And Import. During the registration and import process, all of your registration information is stored. The available adapters are added to Integration Cloud, which might take a few minutes to complete. 9. Click the left arrow in the left navigation pane, and then click Designer > Adapters. By default, all available adapters are listed. 10. In the Adapters pane, click the filter and select Type > Private. A list of the available common connectivity adapters is displayed. The SSI Common Connectivity Support is now available to use in Integration Cloud Service. 1-8

15 2 Developing a Cloud App Definition A cloud app definition is a detailed description of how to interact with a particular cloud app including the triggers and actions it supports and the resources it handles. Topics: Understanding a Cloud App Definition Creating a Cloud App Definition from a Basic Template Creating a Cloud App Definition from an Open API 2.0 File Creating a Cloud App Definition from a Postman Collection File Creating a Cloud App Definition Trigger Creating a Cloud App Definition Action Creating a Cloud App Definition Flow Creating a Cloud App Definition Schema Using Pseudo Code in a Recipe s Trigger and Actions Completing the Cloud App Definition Validating a Cloud App Definition Activating a Cloud App Definition Publishing a Cloud App Definition Understanding a Cloud App Definition A cloud app definition is written in specialized Oracle connector definition language (OCDL) code which is specified by a JavaScript Object Notation (JSON) schema and is referred to as an OCDL document. It s a detailed description of how to interact with a particular cloud app including the triggers and actions it supports and the resources it handles. You can create an OCDL document using the SSI Cloud App Definition editor or use your favorite editor. Some developers might choose to combine both options. Once you open an OCDL document in the SSI Cloud App Definition editor, you can use the built-in validation tool to check the accuracy of your code. Parts of an OCDL Definition Required Fields OCDL document Examples Parts of an OCDL Definition The OCDL document contains the following: Triggers that define the curated interface for the events generated by a target application 2-1

16 Chapter 2 Understanding a Cloud App Definition Actions that define the curated interface for the target application's operations Flows that contain all execution logic for the OCDL document Schemas that contain all reusable schemas Required Fields Each cloud app definition document requires certain fields, and the SSI Cloud App Definition editor guides you through the process of completing those fields. title: OCDL document title, visible to the end user description: OCDL document description, visible to the end user categories: a list of unique categories that characterize the target provider baseurl: base REST API URL for the target provider icons : base64 encoded icons of different sizes OCDL document Examples The following are examples of the main parts of an OCDL document. Trigger "triggers": "onfilecreated": "summary": "File Created", "description": "This trigger detects when a file has been added.", "input": "$ref": "#/schemas/folderpath" "output": "$ref": "#/schemas/fileoutput" "type": "poller", "split": true, "before": "uri": "flow:onfilecreated_before" "poll": "uri": "flow:onfilecreated_poll" "callback": "uri": "flow:onfilecreated_callback"... Actions "actions": "createfileaction": "summary": "Create File", "description": "This action creates a file when provided with the file content reference.", "input": "$ref": "#/schemas/createfileactioninput" "output": "$ref": "#/schemas/fileoutput" 2-2

17 Chapter 2 Understanding a Cloud App Definition "uri": "flow:createfileaction"... Flows "flows": "createfileaction": "input": "$ref": "#/schemas/createfileactioninput" "output": "$ref": "#/schemas/fileoutput" "step": [ "assign": "from": "path": "fixpath(input.path, true, true) + input.filename", "autorename": "true" "to": "uploadparams" "invoke": "method": "POST", "uri": " "input": "headers": "Dropbox-API-Arg": "headersafejson(uploadparams)" "body": "input.content" "output": "response"... Schemas "rowschema": "type": "object", "title": "Row", "required": [ "row", "sheet" ], "dependencies": "row": [ "sheet" ] "properties": "sheet": "title": "Sheet", "type": "string" "row": "metadata": "uri": "flow:getfirstrowschema", "schema": true 2-3

18 Chapter 2 Creating a Cloud App Definition from a Basic Template... To learn more about working with OCDL, see Language Reference for Oracle Self- Service Integration Cloud Service. Creating a Cloud App Definition from a Basic Template You can create your own cloud app definition using the Cloud App Definition editor. By creating your own cloud app definition, you can add new cloud apps to the system that can be used in recipes created by users in your organization. The cloud app definition models and implements the actions and triggers offered by the connector. 1. From your Dashboard, click the Cloud App Definitions tab. 2. Click New Cloud App Definition. 3. Complete the summary information section. a. Enter a name for your definition. The name will be visible in the Cloud App Definitions catalog. b. Add a description. c. Add categories for the description. You can look at the categories in your Cloud App Definition catalog for example terms to use when categorizing this cloud app. d. Add the Base URL. The Base URL should be provided in the cloud app s documentation. See Base URL Criteria for Base URL requirements. e. Add a graphic that represents the cloud app. PNG format is acceptable, and the graphic size is limited to fewer than 50KB. Your summary information is complete. The image shows an example of a cloud app definition using Hubspot. 2-4

19 Chapter 2 Creating a Cloud App Definition from an Open API 2.0 File At this point, SSI requires the creation of an authorization test flow. The authorization test flow models the API call that SSI will conduct to test the connection. Typically, you will choose a safe and repeatable API call which returns some data for example logged in profile name. You can leave this blank. 4. Select the default option Basic Template. 5. Click Done. A draft of your cloud app definition opens in the OCDL editor. What you ve created is a placeholder cloud app definition. Now you need to add the trigger, action, schemas, and flows. See Creating a Cloud App Definition Trigger, Creating a Cloud App Definition Action, Creating a Cloud App Definition Schema, and Creating a Cloud App Definition Flow, and Completing the Cloud App Definition. Creating a Cloud App Definition from an Open API 2.0 File If you have your own Open API 2.0 file, then you can upload the file in the Cloud App Definition editor to create a cloud app definition. 1. From the Cloud App Definitions tab, click Create New Cloud App Definition. 2. In the New Cloud App Definition Editor, enter a display name for your cloud app definition. 3. (Optional) Enter values for the Description, Categories, and Base URL fields. 4. In the Graphic field, you can keep the default graphic or upload a new graphic by clicking Change. 5. In the Start with section, click Open API 2.0 File. 2-5

20 Chapter 2 Creating a Cloud App Definition from a Postman Collection File 6. Click Upload Open API 2.0 File and choose a file to upload. 7. Click Create. The new cloud app definition is listed in My Cloud App Definitions. Creating a Cloud App Definition from a Postman Collection File If you have your own Postman Collection file, then you can upload the file in the New Cloud App Definition editor to create a cloud app definition. 1. From the Cloud App Definitions tab, click Create New Cloud App Definition. 2. In the New Cloud App Definition Editor, enter a display name for your cloud app definition. 3. (Optional) Enter values for the Description, Categories, and Base URL fields. 4. In the Graphic field, you can keep the default graphic or upload a new graphic by clicking Change. 5. In the Start with section, click Postman Collection v1 File. 6. Click Upload Postman Collection File and choose a file to upload. 7. Click Create. The new cloud app definition is listed in My Cloud App Definitions. Creating a Cloud App Definition Trigger To model a trigger, you must first decide what the trigger will do. This requires knowledge of the cloud application that you re using. Typically, the SSI end user will be familiar with the events associated with what they can do when logged in to the cloud app web site. Triggers for a specific cloud app should be modeled to occur on events that would be familiar to an end user. This 2-6

21 Chapter 2 Creating a Cloud App Definition Trigger requires knowledge of the cloud app that you want to support. For this exercise, you can review the cloud application s API to understand what s available. Note: Refer to Language Reference for Oracle Self-Service Integration Cloud Service for questions you have about the language. This example shows how to model the trigger of creating a contact. 1. From your Dashboard, click the Cloud App Definitions tab. 2. Click the cloud app definition that you want to edit. The Cloud App Definition Editor opens. 3. Copy and paste the following code to create a trigger. The following code is specific to the example that uses Hubspot. The trigger you develop depends on specific names being used elsewhere in the OCDL (schemas and flows). "triggers": "oncontactcreated": "summary": "Contact Created", "description": "This trigger detects when a new contact has been created.", "output": "$ref": "#/schemas/contactoutput" "type": "poller", "split": true, "before": "uri": "flow:oncontactcreated_before" "poll": "uri": "flow:oncontactcreated_poll" "callback": "uri": "flow:oncontactcreated_callback" 4. Save your changes. 2-7

22 Chapter 2 Creating a Cloud App Definition Action Creating a Cloud App Definition Action To model an action, you must first decide what the action will do. This requires knowledge of the cloud application that you re using. Typically, SSI users are business users who understand actions from the context of what they can do in the application s user interface. Once you have decided the action to model, you must see if the corresponding action can be accomplished programmatically through the cloud application s API. You can review the cloud application s API to understand what s available. Note: Refer to the Language Reference for Oracle Self-Service Integration Cloud Service for questions you have about the language. This example shows how to model the action of creating a contact. 1. From your Dashboard, click the Cloud App Definitions tab. 2. Select the cloud app definition that you want to edit. The Cloud App Definition Editor opens. 3. In the OCDL Definition, start with an action. The example uses createcontact for the action. "actions": "createcontact": The action requires a summary, description, input, and output definitions, and you add those in the next steps. 4. Add the action summary and description. "summary": "Create Contact", "description": "This action creates a contact.", 5. Add the input and output parameters. "input": "$ref": "#/schemas/createcontactinput" "output": "$ref": "#/ schemas/createcontactinput" The input and output parameters reference the schema that you add to the OCDL Definition in Creating a Cloud App Definition Schema. 6. Add the flow reference.. "uri": "flow:createcontact" The flow is referenced from the flow that you will add in Creating a Cloud App Definition Flow. 2-8

23 Chapter 2 Creating a Cloud App Definition Flow The final action will look similar to this: "actions": "createcontact": "summary": "Create Contact", "description": "This action creates a contact.", "input": "$ref": "#/schemas/createcontactinput" "output": "$ref": "#/schemas/createcontactoutput" "uri": "flow:createcontact" Creating a Cloud App Definition Flow The flow models the implementation of the action. It takes the input and output that the action defines as its own input and output. The steps can be considered a metadata style of programmatic code with constructs such as assigns, loop, conditionals, and while. Additionally, a special invoke step permits callouts to third party APIs. Note: Refer to the Language Reference for Oracle Self-Service Integration Cloud Service for questions you have about the language. This example shows how to model the flow for creating a contact. 1. From your Dashboard, click the Cloud App Definitions tab. 2. Click the cloud app definition that you want to edit. The Cloud App Definition Editor opens. The code sample in this exercise has two flows. The first flow implements the createcontact action. The second flow implements the testconnection action. 3. Add a createcontact action that uses a step to invoke the contact method by copying and pasting the following code sample into the editor. "flows": "createcontact": "input": "$ref": "#/schemas/createcontactinput" 2-9

24 Chapter 2 Creating a Cloud App Definition Flow "output": "$ref": "#/schemas/createcontactoutput" "step": [ "invoke": "method": "POST", "uri": "contacts/v1/contact/", "input": "body": "properties": [ "property": "' '", "value": "input. " "property": "'firstname'", "value": "input.firstname" "property": "'lastname'", "value": "input.lastname" "property": "'website'", "value": "input.website" "property": "'phone'", "value": "input.phone" ] "output": "response" "assign": "from": "canonical-vid": "response.body['canonical-vid']", "profile-url": "response.body['profile-url']" "to": "output" ] Note that the flows.createcontact.step.invoke.uri field is mandatory." 4. You can create the testconnection action by copying and pasting the following code: "testconnection": "step": [ "invoke": "method": "GET", "uri": "contacts/v1/lists", "output": "output", 2-10

25 Chapter 2 Creating a Cloud App Definition Schema "catchall": "throw": "errorname": "RuntimeError", "input": "error.body.message" "if": "condition": "Boolean(output.body.offset)!=true", "then": "throw": "errorname": "RuntimeError" ] If you want to start with a completed cloud app definition, see the code example in Completing the Cloud App Definition. Creating a Cloud App Definition Schema The schema represents the action signature. It models the input parameters and the output parameters that show up in the SSI user interface as user input widgets. Here are some hints to help you determine the schema: Read the cloud application s REST API for the data that you want to implement. Use a tool such as Postman or the Advanced Rest Client to test the REST API call that will be called to conduct the action. Use the output of REST API test to model the set of input necessary to call the REST API call and receive the expected output. Use a tool such as to convert the JSON output to JSON Schema. Note: Refer to the Language Reference for Oracle Self-Service Integration Cloud Service for questions you have about the language. The following instructions use the create contact action. 1. From your Dashboard, click the Cloud App Definitions tab. 2. Click the cloud app definition that you want to edit. 2-11

26 Chapter 2 Creating a Cloud App Definition Schema The Cloud App Definition Editor opens. 3. Determine how many fields of the create contact you want to use. For example, the API might include twenty properties, but you only want five properties. firstname lastname website phone 4. Refer to the results of calling the REST API that you are modeling in the invoke section of the associated flow(s) using the third-party tools suggested above. 5. Add the properties to the OCDL Definition in the Cloud App Definition Editor. The syntax is similar to the following: "firstname": "type": "string", "title": "First Name", "description": "First Name" 6. Finish the schema by adding the remaining code: The syntax is similar to the following: "schemas": "createcontactinput": "type": "object", "title": "Input", "description": "Input", "properties": " ": "type": "string", "title": " ", "description": " " "firstname": "type": "string", "title": "First Name", "description": "First Name" "lastname": "type": "string", "title": "Last Name", "description": "Last Name" "website": "type": "string", "title": "Website", 2-12

27 Chapter 2 Using Pseudo Code in a Recipe s Trigger and Actions "description": "Website" "phone": "type": "string", "title": "Phone", "description": "Phone" Using Pseudo Code in a Recipe s Trigger and Actions Pseudo code style is the way that you can present a recipe step in the format of a readable sentence. Pseudo code can be used in a recipe s trigger and actions. It lets the user easily see brief information about how the recipe steps work. An is the pseudo code Send to your.name@domain.com via Mock Gmail, as shown in the image. Mock Gmail is an account created for demonstration purposes. Pseudo code is optional, but if you want to use the pseudo code feature, you need to add pseudo code to your action and trigger. 1. Open a cloud app definition. 2. In the editor, add the following code to the action. "sendmailaction": "summary": "Send ", "description": "This action sends an .", "pseudocode": "", "input": "$ref": "#/schemas/sendmailactioninput" "output": "$ref": "#/schemas/onnewmailtriggeroutput" "uri": "flow:sendmailaction" See the OCDL Pseudo Code information in the Language Reference for Oracle Self-Service Integration. Completing the Cloud App Definition A complete cloud app definition includes a trigger, actions, schemas, and flows. To help you get started, you can use the following code to create a completed cloud app definition. 2-13

28 Chapter 2 Completing the Cloud App Definition 1. From your Dashboard, click the Cloud App Definitions tab. 2. Select a draft cloud app definition to edit. If you don t have a draft cloud app definition, then create a new definition by following the instructions in Creating a Cloud App Definition from a Basic Template. 3. In the Cloud App Definition editor, delete all of the code in the cloud app definition. 4. Add the trigger, action, schemas, and flows to the cloud app definition by copying and pasting the following code: "description": "HubSpot is a marketing application service that manages contacts and campaigns.", "categories": [ " Marketing", "Marketing" ], "baseurl": " "test": "uri": "flow:testconnection" "flows": "createcontact": "input": "$ref": "#/schemas/createcontactactioninput" "output": "$ref": "#/schemas/createcontactactionoutput" "step": [ "invoke": "method": "POST", "uri": "/contacts/v1/contact/", "input": "body": "properties": [ "property": "' '", "value": "input. " "property": "'firstname'", "value": "input.firstname" "property": "'lastname'", "value": "input.lastname" "property": "'website'", "value": "input.website" "property": "'company'", "value": "input.company" "property": "'phone'", 2-14

29 Chapter 2 Completing the Cloud App Definition "value": "input.phone" "property": "'address'", "value": "input.address" "property": "'city'", "value": "input.city" "property": "'state'", "value": "input.state" "property": "'zip'", "value": "input.zip" ] "output": "response" "assign": "from": "canonical-vid": "response.body['canonical-vid']", "profile-url": "response.body['profile-url']" "to": "output" ] "testconnection": "step": [ "invoke": "method": "GET", "uri": "/contacts/v1/lists/all/contacts/all/?count=1", "output": "output", "catchall": "throw": "errorname": "RuntimeError", "input": "error.body.error_summary" "if": "condition": "Boolean(!!output.body.contacts)!=true", "then": "throw": "errorname": "RuntimeError" ] 2-15

30 Chapter 2 Completing the Cloud App Definition "oncontactcreated_before": "output": "step": [ "invoke": "method": "GET", "uri": "/contacts/v1/lists/all/contacts/recent", "input": "parameters": "count":"1" "output": "response" "assign": "from": "latestcreatedtime": "response.body.contacts[0].addedat" "to": "output" ] "oncontactcreated_poll": "input": "output": "type": "object", "properties": "persist": "notification": "type": "array", "items": "type":"object", "properties": "vid": "type": "integer", "title": "Contact Id", "description": "Contact id." "createdate": "type":"integer", "title":"contact Created Time", "description":"contact created time" "firstname": "title": "First Name", "description": "First name", "type": "string" "lastname": "title": "Last Name", "description": "Last name", "type": "string" "company": "title": "Company", "description": "Company", "type": "string" 2-16

31 Chapter 2 Completing the Cloud App Definition " ": "title": " ", "description": " ", "type": "string" "phone": "title": "Phone", "description": "Phone", "type": "string" "step": [ "invoke": "method": "GET", "uri": "/contacts/v1/lists/all/contacts/all", "input": "parameters": "count":"100" "output": "response" "assign": "from":"response.body.contacts.map((e)=>return vid: e.vid )", "to":"vidarray" "assign": "from":[], "to":"contactarray" "while": "condition":"!isempty(vidarray) && index < vidarray.length", "do":[ "invoke": "method": "GET", "uri": "/contacts/v1/contact/vid/vid/profile", "input": "parameters": "vid": "vidarray[index].vid" "output": "contactresponse" "assign": "from":"contactarray.concat(contactresponse.body)", "to":"contactarray" 2-17

32 Chapter 2 Completing the Cloud App Definition ] "assign": "from":"contactarray.filter((contact)=> return contact.properties.createdate.value.tonumber() > input.latestcreatedtime).map((e)=> return vid: e.vid, createdate: e.properties.createdate.value.tonumber(), firstname: e.properties.firstname.value,lastname: e.properties.lastname.value,company:e.properties.company.value, e.properties. .value,phone: e.properties.phone.value )", "to":"newaddedcontacts" "if": "condition":"newaddedcontacts.length > 0", "then": "assign": "from": "persist": "latestcreatedtime": "maxvalueby(newaddedcontacts, 'createdate', now().todate().tomilliseconds())" "notification": "newaddedcontacts" "to": "output" "else": "assign": "from": "persist": "latestcreatedtime": "input.latestcreatedtime" "to": "output" ] "oncontactcreated_callback": "input": "type": "object", "title":"contact Created", "description":"contact created", "properties": "vid": "type": "integer", "title": "Contact Id", "description": "Contact id." "createdate": "type":"integer", 2-18

33 Chapter 2 Completing the Cloud App Definition "title":"contact Created Time", "description":"contact created time" "firstname": "title": "First Name", "description": "First name", "type": "string" "lastname": "title": "Last Name", "description": "Last name", "type": "string" "company": "title": "Company", "description": "Company", "type": "string" " ": "title": " ", "description": " ", "type": "string" "phone": "title": "Phone", "description": "Phone", "type": "string" "output": "$ref": "#/schemas/contacttriggeroutput" "step": "assign": "from": "firstname": "input.firstname", "lastname": "input.lastname", "company":"input.company", "createdate":"input.createdate.todate()", " ":"input. ", "phone":"input.phone" "to": "output" "schemas": "createcontactactioninput": "type": "object", "title": "Input", "description": "Input", "properties": " ": "type": "string", "title": " ", "description": " " "firstname": "type": "string", 2-19

34 Chapter 2 Completing the Cloud App Definition "title": "First Name", "description": "First Name" "lastname": "type": "string", "title": "Last Name", "description": "Last Name" "website": "type": "string", "title": "Website", "description": "Website" "company": "type": "string", "title": "Company", "description": "Company" "address": "type": "string", "title": "Address", "description": "Address" "city": "type": "string", "title": "City", "description": "City" "state": "type": "string", "title": "State", "description": "State" "zip": "type": "string", "title": "Zip Code", "description": "Zip Code" "required": [ " ", "firstname", "lastname" ], "example": " ": "ossa.oracle@oracle.com", "firstname": "Oracle", "lastname": "User" "createcontactactionoutput": "type": "object", "title": "Contact", "description": "Output", "properties": "canonical-vid": "type": "integer", "title": "Canonical ID", "description": "Canonical ID" "profile-url": 2-20

35 Chapter 2 Completing the Cloud App Definition "type": "string", "title": "Profile URL", "description": "Profile URL" "ContactTriggerOutput": "title": "Contact", "description": "Contact", "type": "object", "properties": "firstname": "title": "First Name", "description": "First name", "type": "string" "lastname": "title": "Last Name", "description": "Last name", "type": "string" "company": "title": "Company", "description": "Company", "type": "string" "createddate": "title": "Contact Created Time", "description": "Contact created time.", "type": "string", "format": "date-time" " ": "title": " ", "description": " ", "type": "string", "format": " " "phone": "title": "Phone", "description": "Phone", "type": "string" "actions": "createcontact": "summary": "Create Contact", "description": "This action creates a contact.", "input": "$ref": "#/schemas/createcontactactioninput" "output": "$ref": "#/schemas/createcontactactionoutput" "uri": "flow:createcontact" "triggers": "oncontactcreated": 2-21

36 Chapter 2 Validating a Cloud App Definition "summary": "Contact Created", "description": "This trigger detects when a new contact has been created.", "output": "$ref": "#/schemas/contacttriggeroutput" "type": "poller", "split": true, "before": "uri": "flow:oncontactcreated_before" "poll": "uri": "flow:oncontactcreated_poll" "callback": "uri": "flow:oncontactcreated_callback" Check that there are no errors shown when you validate the cloud app definition code. You might see some warnings, but this is expected for the example code. Refer to the App Definition Lint Checks V2 to understand the validation messages. 5. Save the cloud app definition. Next you can create a cloud app instance. See Creating a Cloud App Instance Using a Basic Authentication. Validating a Cloud App Definition SSI includes a number of features to help validate the definition that highlights both issues (errors) and warnings. 1. In My Cloud App Definitions, select a cloud app definition that you want to validate. 2. From the menu, select Edit. The cloud app definition opens in the Cloud App Definition Editor. 3. Click to start the validation. If there are no validation errors, then you receive a successful message. 2-22

37 Chapter 2 Validating a Cloud App Definition If there are validation errors, then they are listed in the Validation Report. Fix the errors. Click Run Validation to run the validation again. Warnings might occur which could indicate something needs correcting depending on the intent and behavior desired. Warnings don t stop the OCDLfrom being used. However, Errors do require correcting before an OCDL can be used. To learn which criteria the validation uses, see OCDL Lint Checks V2 for details. 2-23

38 Chapter 2 Activating a Cloud App Definition Activating a Cloud App Definition You can easily activate a cloud app definition using the menu option in My Cloud App Definitions. 1. From your Dashboard, open My Cloud App Definitions. 2. Find a cloud app definition that you want to activate. 3. From the menu, select. Activate. The dialog opens. You can have only one active cloud app definition at one time. Note: Once you activate the current definition, the other cloud app definition is deactivated and all associated recipes associated with that cloud app definition will be invalid and inactive. 4. Click Activate. Your cloud app definition is now activated. Publishing a Cloud App Definition When you publish a cloud app definition in SSI, it s available to be used to create a cloud app instance and it s visible to all SSI users in your service instance. 1. From your Dashboard, click the Cloud App Definition tab. 2-24

39 Chapter 2 Publishing a Cloud App Definition 2. Select the cloud app definition that you want to publish. 3. From the menu, select Publish. The dialog opens and asks you to verify if you re sure you want to publish the definition. 4. Change the version number if needed and then click Publish. The cloud app definition is now visible in the Cloud Apps catalog in the Custom Built section. 5. Open the Cloud Apps catalog to see the new definition. 6. Click the new cloud app definition to open the details page. Although the cloud app definition is visible to users, they can t use that cloud app definition in a recipe until there is a cloud app instance of that cloud app definition. 2-25

40 3 Managing Cloud App Definitions You can manage your cloud app definitions to stay current with your business needs. Topics: Editing a Cloud App Definition Previewing Cloud App Instances for an Active Cloud App Definition Deactivating a Cloud App Definition Deleting a Cloud App Definition Working with Cloud App Definition Versions Editing a Cloud App Definition You can edit a cloud app definition. Note that once you change it, any instances and associated cloud app accounts will be invalidated. You might need to edit a cloud app definition for a few reasons, including: You want to add a new trigger or action The cloud app s API has changed, and you need to make an update You want to change the cloud app definition s icon or the basic information about the app such as the description and category. 1. In Cloud App Definitions, use one of the following methods to open the cloud app definition for editing: Click the name of the cloud app definition. From the menu, select Edit/View. If the cloud app definition is active, it will open in the Cloud App Definition Viewer. 3-1

41 Chapter 3 Editing a Cloud App Definition The Cloud App Definition Viewer has three options: Edit: Warns you to first deactivate the active cloud app definition before you can continue. Done: The Cloud App Definition Viewer closes and you return to the Cloud App Definitions dashboard. Preview Cloud App Information page: The Preview Cloud App Information page opens. 2. Click Edit. 3. (Optional) Click Deactivate Definition to edit. 3-2

42 Chapter 3 Previewing Cloud App Instances for an Active Cloud App Definition 4. Edit the cloud app definition in the Cloud App Definition Editor. 5. After you have edited the cloud app definition, validate your changes. 6. Click Done when you are finished. Previewing Cloud App Instances for an Active Cloud App Definition While you are editing an active cloud app definition, you can preview the cloud app instances using the Preview Cloud App Instance page. 1. In My Cloud App Definitions, select the active cloud app definition to edit. 2. From the menu, select Edit/View. 3-3

43 Chapter 3 Previewing Cloud App Instances for an Active Cloud App Definition 3. In the Cloud App Definition Viewer, click Preview Cloud App Information page. The Preview Cloud App Information page opens. 4. Click Back to Editor after you have reviewed the available instances. 3-4

44 Chapter 3 Deactivating a Cloud App Definition Deactivating a Cloud App Definition When you deactivate a cloud app definition, recipes using the instances will be deactivated. 1. Click the Cloud Apps Instances tab. 2. From the menu, select Deactivate. The Deactivate Cloud App Definition? window opens. 3. Click Deactivate. You ll receive a confirmation notice that the cloud app definition has been deactivated. Deleting a Cloud App Definition You can delete a cloud app definition if you no longer want to use it or you want to create a new definition for the same cloud app. 1. Go to My Cloud App Definitions. 2. Select a cloud app definition. 3. From the menu, select Delete. The Delete Cloud App Definition? confirmation dialog opens. 3-5

45 Chapter 3 Working with Cloud App Definition Versions 4. Click Delete to delete the cloud app definition. The cloud app definition is deleted. Any recipe that refers to this cloud app definition will be unconfigured and deactivated. Working with Cloud App Definition Versions You can develop several versions of a cloud app definition, but each requires a unique version number. It s important to understand these version rules, which are useful in managing cloud app definitions when you re editing and republishing newer versions. Note that you can have only one active cloud app definition for the same cloud app. 1. Open the Cloud app Definitions tab. 2. Select a cloud app definition from which to draft a new version. 3. From the menu, click Draft New Version. You can create a new draft version from a draft or active cloud app definition. The New Draft dialog opens. 3-6

46 Chapter 3 Working with Cloud App Definition Versions 4. Select the OAuth type and click Create. The Cloud App Definition Editor opens. 5. Edit the cloud app definition. 6. Click Done when you are finished. The new cloud app definition is added to My Cloud App Definitions. 3-7

47 4 Working with a Cloud App Instance A cloud app instance is a configuration that defines the necessary authentication methods to access a cloud app. Topics: Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type Creating a Cloud App Instance Using Basic Authentication Creating a Cloud App Instance Using No Authentication Type Testing a Cloud App Instance Publishing a Cloud App Instance Creating a Cloud App Instance Using an OAuth 2.0 (threelegged) Authentication Type When you create a cloud app instance, you can configure it to use the OAuth 2.0 (three-legged) authentication type. Preparing to Use OAuth 2.0 (three-legged) Authentication To get the required information from the cloud app, create a developer account with that cloud app. Once you ve created the account, you ll receive the required information needed to create the cloud app instance. Register SSI as an application with the desired cloud app. Obtain the client ID and secret. Obtain the valid authorization callback and redirect URIs. The information that you gather from the cloud app is used to create the permission dialog that is used by the end user. The following image represents what the user will see: 4-1

48 Chapter 4 Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type See Preparing to Create a Cloud App Definition and Instance for more information. 1. From the Cloud App Instance tab of your Dashboard, click Create a New Cloud App Instance. 2. In the New Cloud App Instance window, click Select a Cloud App Definition. The Select a Cloud App Definition window opens. 3. Choose either a custom built definition or a definition built by Oracle. The cloud app definition opens in the New Cloud App Instance editor. 4-2

49 Chapter 4 Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type 4. Enter a Display Name for your cloud app instance. This name is what your users will see in their Cloud Apps catalog. 5. If required, add a Base URL for your instance. Note that if you add a Base URL, it will override the Base URL in the cloud app definition. 6. For Authentication Type, click the OAuth 2.0 (three-legged) option. The OAuth 2.0 (three-legged) authentication type opens. 7. Enter the Client ID and Client Secret. 4-3

50 Chapter 4 Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type This information comes from your developer account that you have with the cloud app. 8. To copy the Redirect URI, click Copy to Clipboard. 9. Enter a Base URL. 10. Scope is an optional field. If you enter a description, the syntax is category:action separated by commas. 11. Select a Grant Type of either authorization_code or custom. For authorization_code: a. In the Path field of the Authorize section, enter the required URL. b. Enter a Base URL Override, if needed. c. In the Path field of the Get Token section, enter the required URL. d. Enter a Base URL Override, if needed. e. Add any additional information if needed. For custom: Creating a custom Grant Type is at your discretion. 4-4

51 Chapter 4 Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type The custom grant type requires a username and password. The URI is in the format similar to the following: (Optional). Refresh is an optional field, and you can set it at your discretion. 13. (Optional). Select the Use body instead of headers for client authentication. 14. (Optional). Customize the access token using the following options: Token Parameter Name: authorization Location: either query or headers 15. (Optional). Select an Include type. 16. (Optional). Select an API Key. a. Enter a name. b. Enter a location. c. Choose either Each user will provide a value or Authorize a single Shared Account for all users. 17. Select one of the Cloud App Account options. Users create their own accounts. This is the typical option. Authorize a single Shared Account for all users 18. Scroll to the top of the page and click Create. The new cloud app instance is now listed in My Cloud App Instances and is designated Activeif it has been successfully configured. If there are any omissions or errors, it will remain as a Draft. 4-5

52 Chapter 4 Creating a Cloud App Instance Using Basic Authentication Creating a Cloud App Instance Using Basic Authentication When you create a cloud app instance, you can configure it to use basic authentication. 1. From the Cloud App Instance tab of your Dashboard, click Create a New Cloud App Instance. 2. In the New Cloud App Instance window, click Select a Cloud App Definition. The Select a Cloud App Definition window opens. 3. Choose either a custom built definition or a definition built by Oracle. The cloud app definition opens in the New Cloud App Instance editor. 4. Enter a Display Name for your cloud app instance. This name is what your users will see in their Cloud Apps catalog. 5. If required, add a Base URL for your instance. Note that if you add a Base URL, it will override the Base URL in the cloud app definition. 6. For Authentication Type, click the Basic option. The Basic authentication form opens. 4-6

53 Chapter 4 Creating a Cloud App Instance Using Basic Authentication 7. Select a method for implementing Basic authentication. Select Require the user to specify a Service URL if you want the user to specify a service URL for that cloud app instance. Select Customize field labels for user authentication to customize each field for user authentication. User Name Label Required User Name Placeholder Password Label Required Password Placeholder Service URL Label Service URL Placeholder Validation Expression Use constants as a set of strings and operators 4-7

54 Chapter 4 Creating a Cloud App Instance Using Basic Authentication You can select both options. 8. Optional. Select an API Key. a. Enter a name. b. Enter a location. c. Choose either Each user will provide a value or Authorize a single Shared Account for all users. 9. Select one of the Cloud App Account options. Users create their own accounts Authorize a single Shared Account for all users 10. Scroll to the top of the page and click Done. 4-8

55 Chapter 4 Creating a Cloud App Instance Using No Authentication Type The new cloud app instance is now listed in My Cloud App Instances and is designated Active. Creating a Cloud App Instance Using No Authentication Type Create a custom cloud app instance so you can provide a specific application that your organization uses in its daily business. 1. From the Cloud App Instance tab of your Dashboard, click Create a New Cloud App Instance. 2. In the New Cloud App Instance window, click Select a Cloud App Definition. The Select a Cloud App Definition window opens. 3. Choose either a custom built definition or a definition built by Oracle. The cloud app definition opens in the New Cloud App Instance editor. 4-9

56 Chapter 4 Creating a Cloud App Instance Using No Authentication Type 4. Enter a Display Name for your cloud app instance. This name is what your users will see in their Cloud Apps list. 5. If required, add a Base URL for your instance. Note that if you add a Base URL, it will override the Base URL in the cloud app definition. 6. Select the type of authorization to use. OAuth 2.0 (three-legged). See Creating a Cloud App Instance Using an OAuth 2.0 (three-legged) Authentication Type for instructions. Basic. See Creating a Cloud App Instance Using a Basic Authentication Type for instructions. None. Continue to the next step. 7. Select None. 4-10

57 Chapter 4 Testing a Cloud App Instance 8. (Optional). Check API Key if you want to specify an API key value with each call to the cloud app. a. Add a name. b. Add a location, which can be by headers, query, or path. c. Decide how the API Key will be used by selecting one of the following: Each user will provide a value. Specified for all users. 9. In Cloud App Account, decide how the user will be authorized to use this instance by selecting one of the following: Users create their own accounts. Authorize a single Shared Account for all users. 10. Click Create when you are finished. The new cloud app instance is now listed in My Cloud App Instances and is labeled Active. Testing a Cloud App Instance You can check a cloud app instance by creating a cloud app account with that instance and using it in a recipe. Note that if the cloud app definition and cloud app instance are not both published, you'll be the only one who has access to test them. 1. In the My Recipes section of the Dashboard, click Create a New Recipe. 2. Name and describe your new recipe. 3. Click Trigger to expand the Trigger section. 4. Click Select App and choose the SSI timer as a trigger application. 5. Configure the Single Event Timer, which can be set to any time. 4-11

58 Chapter 4 Testing a Cloud App Instance 6. In the Action section, select Create Account. 7. Create an account using the newly created cloud app instance. 8. In the Input section, add content to the fields. 4-12

59 Chapter 4 Testing a Cloud App Instance 4-13

60 Chapter 4 Publishing a Cloud App Instance 9. Click the Activate switch in the upper right corner to save and activate the recipe. The Recipe Editor closes and returns to My Recipes. 10. In My Recipes, select the new recipe, and click the menu to expand it. 11. Select Run Now. 12. In the Run Now dialog, click Run. 13. Go to the Recipe Job History and look for a history of the job run. If you see an entry for that job run, then you know that your cloud app instance is working. Publishing a Cloud App Instance When you publish a cloud app instance in SSI, it is available to be used in recipes. 1. In your Dashboard, click the Cloud App Instance tab. 2. Select the cloud app instance that you want to publish. 3. From the menu, select Publish to Catalog. A dialog opens to verify that you do want to publish that cloud app instance. If you publish it, it s visible in the Cloud Apps catalog and available to all users. This cloud app instance will replace other cloud app instances of the same type. 4-14

61 Chapter 4 Publishing a Cloud App Instance 4. Click Publish to publish the cloud app instance. a. Optional. Select Delete my private working version after publishing. 5. Open the Cloud Apps catalog and view the details for the cloud app that you just published. The publishing details for that instance are highlighted in the instance menu. 4-15

62 5 Managing Cloud App Instances You can modify your cloud app instances to keep them current with your business needs. Topics: Editing a Cloud App Instance Deleting a Cloud App Instance Editing a Cloud App Instance You can edit a cloud app instance if you want to change its configuration. Edit a cloud app instance to keep it current with the latest cloud app versions. 1. In your Dashboard, click Cloud App Instances. 2. Find a cloud app instance that you want to edit. If the cloud app instance is active, you need to deactivate it. 3. Click the menu and select Edit. The Cloud App Instance Editor opens. 4. Edit your cloud app instance as necessary. 5. Click Done when you are finished. 5-1