The Workspace ONE Experience Workflows out-of-the-box business system integration solutions that are developed using Boomi are partially configured. You log into the Hub Services console, Experience Workflows page to install and complete the business system integration with Boomi.

When you configure a business system integration pack, you log into the Boomi portal from the Experience Workflows page and select either the PROD or TEST environment to install the pack. The TEST environment to associate with your user acceptance testing (UAT) Hub Services environment to configure business system integration packs for testing before configuring them in the PROD environment that is associate with your production Hub Services environment.

After you select the environment, you configure the business system connection URLs and the integration property settings.

The HubServices_Boomi_Integration OAuth 2 client that is automatically created in Workspace ONE Access is the connection URL used for all integration packs that you install. The URL is automatically configured in the Experience Workflows Workspace ONE Hub Services Patch Connector, Workspace ONE Hub Services Connector, and Intermediate Data Storage Connector tabs. You do not need to configure the connection URL for the business system integration packs you set up.

Workspace ONE Experience Workflows Out-of-the-Box Integration Packs

The following are the business system integrations that are available as out-of-the-box integration packs in Hub Services.

Business System Name Use Case Addressed
Coupa Requisition ticket approval
Salesforce Opportunity discount approval
SAP Concur Expense report approval
ServiceNow Requisition ticket approval
Workday Inbox task
Adobe Sign Electronically sign documents
Jira Service Desk Jira Service Desk ticket approval

Set up Coupa Requisition Approval in Experience Workflows

The Workspace ONE Experience Workflows integration pack with Coupa scans for requisition tickets in Coupa that require approval and creates an approval notification in Workspace ONE Intelligent Hub that the approver can act on to approve or decline the ticket.

Note: Attachments for this integration pack is only supported when using Workspace ONE Intelligent Hub via the web browser. Attachment support for Mobile and Desktop native Hub clients will be introduced in future releases.

The sequence of the workflow is as follows.

  • When the Boomi process executes the requests for a requisition approval from Coupa, it sends a notification to the approver in Workspace ONE Intelligent Hub.
  • In Workspace ONE Intelligent Hub, the approver can either approve or decline the request.
    • If any updates are made to the requisition, the notification is updated in the approving user Workspace ONE Intelligent Hub app view.
  • Workspace ONE Intelligent Hub sends Coupa the approvers response.

Prerequisites

  • Obtain the Coupa API key for Workspace ONE Experience Workflows.

    Coupa Requisition Approvals integration pack configuration requires an API key for users to authenticate and securely send API requests to your Coupa instance. You must generate a Coupa API key in Coupa. The key is created in the Coupa console's Setup > Integrations > API Keys page. Copy and save the API key that is created because you cannot access the key again in the Coupa console. See the Coupa API Key Security documentation for information about how to generate and save the key.

    You add the API key value to the Coupa Requisition Properties page when you configure the Coupa Requisition Approval integration pack in the Hub Services console Experience Workflows section.

Procedure

  1. Navigate to the Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add Coupa Requisition Approvals integration pack, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Coupa - Requisition Approvals pane, click INSTALL.
  4. Configure the connector values required for the Coupa - Requisition Approvals set up.
    Tab Name Action
    Coupa Connector Enter your Coupa customer URL. For example, https://<customer_name>.coupahost.com.

    To find the Coupa Connector name, go to the Coupa instance and copy the name from the URL.

  5. Click Continue. In the Coupa Requisition Properties page, configure the property values.
    Properties Action
    WORKSPACE ONE ACCESS USER GROUPS Enter the Workspace ONE Access user groups that receives the requisition approval notification. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Coupa system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Coupa and in the Workspace ONE Access service receive the requisition approval notification.

    COUPA ACCOUNT URL Enter your Coupa customer URL For example, .API URL <customer_name>.coupahost.com
    COUPA INTEGRATIONS API KEY Enter the API key that you obtained as described in Prerequisites.
    INITIAL RUN DAYS (<=90). The default value is 7 days. This value is the number of days back to retrieve data or requisition from the Coupa system. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the Coupa Requisition Approvals integration pack to send requisition approval request notifications. Two Coupa processes are displayed in the Schedule page. Select only the [Coupa] Requisition Approvals [Workspace ONE] scheduler. You do not schedule the [Workspace ONE] Requisition Approval Action [Coupa] request because when an action is taken on the request notification, the action reply is automatically sent. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up SAP Concur Expense Approval in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with SAP Concur lets users approve or decline expense reports that are created in SAP Concur from the Workspace ONE Intelligent Hub portal. Expense reports in SAP Concur are scanned and Boomi creates an approval notification and sends the notification to the approver in the Workspace ONE Intelligent Hub app.

The sequence of the workflow is as follows.

  • The end users create an expense report in SAP Concur.
  • When the Boomi process executes a request to retrieve expense reports from SAP Concur, it sends the pending expense report notification through Hub Services to the approver in Workspace ONE Intelligent Hub.
  • In Workspace ONE Intelligent Hub, the approver can either approve the report or decline the request.
  • Workspace ONE Intelligent Hub sends the approver's response to SAP Concur.

Prerequisites

The following SAP Concur account setting values are required. You can obtain this information from your SAP Concur Partner Enablement Manager or Partner Account Manager. See the SAP Concur Authentication documentation to register the app and obtain the properties

  • Concur Account connector URL
  • Admin user name and password
  • ClientID and client secret
  • Concur API URL Prefix

You add the Concur clientID and client secret to the Concur Requisition Properties page when you configure the SAP Concur Expense Approval integration pack in the Hub Services console.

Procedure

  1. Navigate to Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add Concur Expense Approvals integration pack, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Concur - Expense Approvals pane, click INSTALL.
  4. Configure the connector values required for the SAP Concur set up.
    Tab Name Action
    Concur Connector Enter your Concur API URL that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager. For example,<customer_name>.concursolution.com.
  5. Click Continue to configure the Concur Requisition Properties page.
    Properties Action
    CONCUR CLIENT ID Enter your Concur Client ID value that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager.
    CONCUR CLIENT SECRET Enter your Concur Client Secret value that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager.
    CONCUR ADMIN USERNAME Enter the Concur admin user name that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager.
    CONCUR ADMIN PASSWORD Enter the admin password that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager.
    CONCUR ACCOUNT URL (BASE URL) Enter the Concur API URL Prefix value that you received from the SAP Concur Partner Enablement Manager or Partner Account Manager. For example, enter https://<customer_name>.concursolution.com.
    WORKSPACE ONE ACCESS USER GROUP Enter the Workspace ONE Access user groups that receives the approval notification. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Concur system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Concur and in the Workspace ONE Access service receive the approval notification.

    INITIAL RUN DAYS (<=90). The default value is 7 days. This value is the number of days back to retrieve data. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the Concur Expense Approvals integration pack to send expense approval request notifications. Three processes are displayed in the Schedule page. Select only the [Concur] Expense Request Approvals [Workspace ONE] process. You do not schedule the [Workspace ONE] Expense Report Action [Concur] response because when an action is taken on the expense report notification, the action reply is automatically sent. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up Salesforce Opportunity Discount Approval in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with Salesforce lets users approve or decline opportunity discount requests that are created in Salesforce from the Workspace ONE Intelligent Hub portal. This experience workflow scans for discount requests in Salesforce that require approval and then creates an approval notification in Workspace ONE Intelligent Hub that the approver can act on.

The sequence of the workflow is as follows.

  • When a sales representative creates an opportunity with a discount greater than the pre-set threshold in Salesforce, a request to approve the discount is created.
  • When the Boomi process executes the request to approve a discount request from Salesforce, it sends a notification to the approver in Workspace ONE Intelligent Hub.
  • In Workspace ONE Intelligent Hub, the approver can either approve or decline the request.
  • Boomi synchronizes the user’s response with Salesforce to update the opportunity request.

Prerequisites

  • Salesforce account URL.
    1. In Salesforce, navigate to Setup and in the Quick Find search box enter Site
    2. Click Domains.
    3. Copy the domain name.
  • Salesforce OAuth SOAP endpoint URL, for example, services/Soap/u/56.0
  • Security token for your Salesforce Account.

    When you create a Salesforce account, Salesforce sends you an email message from support@salesforce.com to the email address associated with the account. The subject of the email is salesforce.com security token confirmation. This email message contains the security token for the account and is not saved in your Salesforce account. If you lose the email or forget the security token value, you must generate it again. When you change the account password or it expires, the security token is regenerated, and a similar email is sent.

  • Steps to get or reset the security token for your Salesforce account
    1. Log into Salesforce from the Salesforce account that is configured for Experience Workflows.
    2. In the Salesforce User Menu, select Setup.
    3. In the menu on the left, under Personal Setup, expand My Personal Information, and then click Reset My Security Token.

      Follow the onscreen instructions. A new email message will be sent with the new security token.

Procedure

  1. Navigate to Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add Salesforce Opportunity Discount Approvals, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Salesforce - Opportunity Discount Approvals pane, click INSTALL.
  4. Configure the connector values required for the Salesforce set up.
    Tab Name Action
    Salesforce Connector Enter your Salesforce customer URL. You can copy the Salesforce URL from your Salesforce instance URL. For example, enter as https://<customer_name>.salesforce.com.
  5. Click Continue to configure the Salesforce Opportunity Properties page.
    Properties Action
    SALESFORCE ADMIN USERNAME Enter the Salesforce login user name.
    SALESFORCE SECURE COMBINATION TOKEN The secure combination token is a combination of your password and your Salesforce security token that you obtained as a prerequisite to configure Salesforce - Opportunity Discount Approvals.

    You append the token to the end of your password. For example, if the password is Xyz@2020 and the security token is 1y3Zqwr34QD, you enter Xyz@20201y3Zqwr34QD as the secure combination token. Note the token is case-sensitive and spaces are not allowed.

    SALESFORCE OAUTH SOAP ENDPOINT Enter the Salesforce OAuth SOAP end point your organization is using. For example, enter as services/Soap/u/56.0.
    SALESFORCE ACCOUNT URL Enter your Salesforce account URL. For example, https://customername.salesforce.com/.
    WORKSPACE ONE ACCESS USER GROUPS

    Enter the Workspace ONE Access user groups that receives the approval notification. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Salesforce system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Salesforce and in the Workspace ONE Access service receive the approval notification.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the Salesforce Opportunity Discount Approvals integration pack to send the discount approval request notifications. Select only the [Salesforce] Opportunity Discount Approvals [Workspace ONE] scheduler. You do not schedule [Workspace ONE] Opportunity Discount Action [Salesforce] response because when an action is taken on the approval request notification, the action reply is automatically sent. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up ServiceNow Requisition Ticket Approval in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with ServiceNow scans for requisition tickets in ServiceNow that require approval and creates an approval notification in Workspace ONE Intelligent Hub that the approver can act on to approve or decline the ticket.

Note: Attachments for this integration pack is only supported when using Workspace ONE Intelligent Hub via the web browser. Attachment support for Mobile and Desktop native Hub clients will be introduced in future releases.

The sequence of the workflow is as follows.

  • An end user requests a resource through ServiceNow that is over a pre-set dollar amount and that request requires approval. The request is tagged as pending in ServiceNow.
  • When the Boomi process executes the request for ticket approval from ServiceNow, it sends a notification to the approver in the Workspace ONE Intelligent Hub app.
  • In the Workspace ONE Intelligent Hub app, the approver can either approve or declines the request.
  • Workspace ONE Intelligent Hub sends ServiceNow the approvers response.

Prerequisites

  • ServiceNow URL Go to your company's ServiceNow URL and copy the URL, https://<yourcompany>.service-now.com.
  • Register your Workspace ONE Access application with your ServiceNow instance.
    1. In ServiceNow, navigate to System OAuth > Application Registry. Click New and select Create an OAuth API endpoint for external clients and fill in the form.
    2. After the form is submitted, search for the application name that you registered. Find and copy the Client ID value and Client Secret.

    You add this information to the ServiceNow properties page.

  • In ServiceNow, set up a user in the admin role with the minimum required access and permissions to approve or decline the request.
    1. In the Filter Navigator, search Users. 
    2. Go to Users and click New to create a new user. 
    3. Give UserID, First name, Last name, Email, Password. And check web services access only and Internal Integration User. 
    4. Then click Edit to add the roles. The approval_admin role must be added to approve or decline the request. The other role that you add needs to be added in the following tables to their Access controls (ACLs). 
    5. Create a custom role with the following access controls (ACL).
      Tables Access Permissions
      sc_request (Requests) Read and write
      sysapproval_approver (Approvals) Read and write
      sys_user (Users) Read
      sc_req_item (Request Items) Read
  • ServiceNow OAuth Access Limiting Scope
    1. Go to the system administrator drop down menu on right side of your ServiceNow console.
    2. Click Elevate Roles. In the pane that displays, check Security Admin and then click OK.

Procedure

  1. Navigate to the Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add the ServiceNow Requisition Ticket Approval integration pack, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the ServiceNow Requisition Approvals pane, click INSTALL.
  4. Configure the connector values required for the ServiceNow set up.
    Tab Name Action
    ServiceNow Connector Enter your ServiceNow customer account URL. For example, https ://<yourcompany>.service-now.com.
  5. Click Continue. In the ServiceNow Requisition Properties page, configure the property values.
    Properties Action
    SERVICESNOW ACCOUNT URL (BASE URL) Enter your ServiceNow customer account URL. For example, https://<customer_name>.service-now.com/.
    SERVICENOW CLIENT ID Enter the client ID that was created in the ServiceNow application registry
    SERVICENOW CLIENT SECRET Enter the client secret that was created in the ServiceNow application registry.
    SERVICENOW ADMIN USERNAME Enter the ServiceNow admin user name.
    SERVICENOW ADMIN PASSWORD Enter the ServiceNow admin user password.
    WORKSPACE ONE ACCESS USER GROUPS

    Enter the Workspace ONE Access user groups that receives the approval notification. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the ServiceNow system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in ServiceNow and in the Workspace ONE Access service receive the requisition approval notification.

    INITIAL RUN DAYS (<=90) The default value is 7 days. This value is the number of days back to retrieve data or requisition from the ServiceNow system. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the ServiceNow Requisition Ticket Approval integration pack to send the approval request notifications. Two processes are displayed in the Schedule page. Select only the [ServiceNow] Requisition Request Approvals [Workspace ONE] scheduler. You do not schedule the [Workspace ONE] Requisition Approval Action [ServiceNow] request because when an action is taken on the approval request notification, the action reply is automatically sent. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up Workday Inbox Task Notification in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with Workday scans the Workday inbox for tasks and creates a notification in Workspace ONE Intelligent Hub to notify users about tasks that are assigned to them. The notification provides a deep link to the task in Workday.

The sequence of the workflow is as follows.

  • The Boomi process uses a custom report to fetch tasks that are in the user’s Workday inbox and sends a notification with the task details to the user's Workspace ONE Intelligent Hub app.
  • Users select the link which is a deep link that sends them directly to the Workday app to take action.

Prerequisite

  • Register Workspace ONE Intelligent Hub app as a client application in the Workday Inbox instance.
  • The following Workspace ONE Intelligent Hub values configured in Workday are required to configure Workday Inbox Task Review integration with Hub Services.
    • Client ID
    • Client Secret
    • Authtoken URL
    • Access Token URL
  • In Workday, search for the Report-as-a-Service (RaaS) custom report investors page that lets you export data from Workday. In the Actions > Web Services menu, view the URLs Web Service page and click OK. In the Workday XML page that displays, right-click REST Workday XML and copy the URL.

    The REST URL can be long. The information you need to configure the Workday properties page is configured in the REST URL as follows.

  • The Workday connector uses the Workday REST API, which uses OAuth 2.0 for authentication. You need to register an API Client for integrations to allow connection to the REST API. In the Register API Client for Integrations page, configure the following.
    • Client Name
    • Select the Non-Expiring Refresh Tokens check box . Enabling this field, avoids regenerating and reconnecting.
    • Select the Tenant Non-Configurable functional area scope to read a custom report.

    Copy and save the Client ID and Client Secret that is created before you click Done.

  • Set up how to manage refresh token for integrations. In the View API Client page for the API client you created, select API Client > Manage Refresh Tokens for Integrations and select the Workday account users to perform the actions.

    Select Generate new refresh token if no refresh token exists. Copy and save the refresh token.

Procedure

  1. Navigate to the Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add the Workday Inbox Task Notification integration pack, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Workday - Inbox Task Notifications pane, click INSTALL.
  4. Configure the connector values required in the Workday set up.
    Tab Name Action
    Workday Connector Enter your Workday Base URL For example, https://<customer_name>.workday.com.
  5. Click Continue. In the Workday Inbox Task Properties page, configure the property values.
    Properties Action
    WORKDAY INTEGRATIONS REFRESH TOKEN Add the refresh token you saved from the Workday Refresh Token Integrations page.
    TENANT ID Enter the tenant ID URL that you use to log into Workday. This is part of the REST URL details.
    ACCOUNT NAME Enter the account name designated in the REST URL.
    REPORT NAME Enter the RAAS custom report name designated in the REST URL
    CLIENT ID Enter the client ID from the Workday Register API Client for Integration page.
    CLIENT SECRET Enter the client secret associated with the client ID.
    REPORT RESOUCE PATH Enter the report resource path in the REST URL.
    WORKSPACE ONE ACCESS USER GROUPS Enter the Workspace ONE Access user groups that receives the Workday notification about tasks in their Workday inbox. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Workday system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Workday and in the Workspace ONE Access service receive the requisition approval notification.

    INITIAL RUN DAYS (<=90) The default value is 7 days. This value is the number of days back to retrieve data or requisition from the Workday system. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule to run the Workday Inbox Task Notification process. Create a schedule in the [Workday] Business Process Tasks [Workspace] scheduler to send the notifications about tasks that are assigned to the user. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up Adobe Sign Document in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with Adobe Sign lets users access Adobe Sign from their Workspace ONE Intelligent Hub portal to electronically sign documents. This workflow scans for Adobe Sign agreements that require an electronically signed signature and then creates a request to sign documents notification in Workspace ONE Intelligent Hub that the user can act on.

The sequence of the workflow is as follows.

  • When the Boomi process executes the request to retrieves agreements that need signatures from Adobe Sign, it sends a notification with details that a document is ready to be signed to the user’s Workspace ONE Intelligent Hub portal.
  • The user clicks on the Go to Adobe Sign link in the notification to launch Adobe Sign in a browser where they can review and sign the document.
  • If any updates are made to the document, the notification is updated in Workspace ONE Intelligent Hub.
  • When the document is signed in the Adobe Sign app, the notification is moved to the Workspace ONE Intelligent Hub History folder in the next scheduled run.

Prerequisites

Obtain the Adobe Sign Connector URL.

  1. In Adobe Sign Instance, after you log in go to the Account tab. In the Account tab, select Adobe Sign API → API Information , Under Documentation select REST API Method Documentation.
  2. The REST API explorer opens in a new tab. Go to Resources and Operations and run BaseURL API.

    In the Request URL, select the Adobe Sign Connector URL, include the port number.

In your Adobe Sign account, create an integration key for this integration with Workspace ONE Intelligent Hub. The Boomi process uses the integration key to make requests to Adobe Sign.

  1. In the Adobe Sign console, click the Account tab and then click Adobe Sign API > API Information.
  2. In the API Information page, click the Integration Key link.
  3. In the Create Integration Key dialog box, complete the following steps.
    1. Enter the Integration Name. This is the name of the app with the integration key that is created. For example, WS1IntegrationKey.

      Save the integration name that you created.

    2. Enable all of the listed scope options to grant to the Integration Key.
    3. Click Save.

    The new app displays in the Access Tokens page.

  4. To get the integration key value, click the app name you created in step 3.a and then click Integration Key.
  5. Copy the integration key from the Integration Key dialog box that displays.

You add this information to the Adobe Sign properties page in the Hub console.

Procedure

  1. Navigate to Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add Adobe Sign, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Adobe Sign Document pane, click INSTALL.
  4. Configure the connector values required in the Adobe Sign set up.
    Tab Action
    Adobe Sign Connector Enter your Adobe Sign Connector customer URL. For example, https://secure.in1.adobesign.com:443.
  5. Click Continue. In the Adobe Sign E-Sign Properties page, configure the property values.
    Properties Action
    INTEGRATION KEY Enter the integration key you created as a prerequisite. This key is used to enable third-party apps to access Adobe Sign data.
    WORKSPACE ONE ACCESS USER GROUPS Enter the Workspace ONE Access user groups that receives the notifications about Adobe Sign agreements. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Adobe Sign system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Adobe Sign and in the Workspace ONE Access service receive the requisition approval notification.

    INITIAL RUN DAYS (<=90) The default value is 7 days. This value is the number of days back to retrieve data or requisition from the Adobe system. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the Adobe Sign Document integration pack. Create a schedule in the [Adobe Sign] E-Signing Document [Workspace ONE] scheduler to send notifications about documents that are ready to be signed. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.

Set up JIRA Service Desk Ticket Approvals in Workspace ONE Experience Workflows

The Workspace ONE Experience Workflows integration pack with Jira Service Desk - Ticket Approvals sets up a process to send notifications through Workspace ONE Intelligent Hub to approvers when users create a request in the Jira Service Desk. Approvers click on the deep link in the notification to navigate to the Jira Service Desk portal where they can take the required action.

Note: Attachments for this integration pack is only supported when using Workspace ONE Intelligent Hub via the web browser. Attachment support for Mobile and Desktop native Hub clients will be introduced in future releases.

The sequence of the workflow is as follows.

  • When the Boomi process retrieves jira requests from the Jira Service Desk, it sends a notification with the details of the request to the approver in the Workspace ONE Intelligent Hub portal.
  • The approver clicks View Service Desk Request in the notification to deep link directly to the jira request page. The approver can approve or decline the request directly from the Jira Service Desk portal.
  • When the action is taken in the Jira Service Desk, the notification is moved to the Workspace ONE Intelligent Hub History folder in the next scheduled run.

Prerequisites

  • In the Jira Developer console, configure the following.
    • OAuth 2.0 (3LO) and save the client ID and secret values.
      1. Navigate to developer.atlassian.com, select your profile icon in the top-right corner, and from the drop down, select Developer console.
      2. Select the app from the list or create one if the app is not in the list.
      3. Select Authorization in the left menu.
      4. Next to OAuth 2.0 (3LO), select Configure.
      5. Enter the Callback URL. Set this to any URL that is accessible by the app. When you implement OAuth 2.0 (3LO) in your app (see next section), the redirect_uri must match this URL.
      6. Click Save changes.
      Note: If you have not added an API to your app, do this now.
      1. Select Permissions in the left menu.
      2. Add Jira platform REST API & Jira Service Desk API.

        These APIs are used in the process to get the request details from the Jira Service Desk.

    • Jira authorization code.
      1. Navigate to developer.atlassian.com.
      2. Select the app from the list.
      3. Select Authorization in the left menu.
      4. Next to OAuth 2.0 (3LO), select Configure.
      5. Copy the Jira platform REST API authorization URL Manually paste read%3Aservicedesk-request%20offline_access%20 scope in the authorization URL.
      6. Paste this URL in browser and copy the Authorization Code.
      Note: To get the access/refresh token in your initial authorization flow, add offline_access scope to the scope parameter of the authorization URL. Paste this URL in the browser and copy the Authorization Code.
      Example URL
      https://auth.atlassian.com/authorize?audience=api.atlassian.com&client_id=YOUR_CLIENT_ID&scope=REQUESTED_SCOPE_ONE%20REQUESTED_SCOPE_TWO%20offline_access&redirect_uri=https://YOUR_APP_CALLBACK_URL&state=YOUR_USER_BOUND_VALUE&response_type=code&prompt=consent

    See the Jira documentation Jira Cloud platform Developer guide, OAuth 2.0 (3LO) apps topic.

Procedure

  1. Navigate to Hub Services console Home > Experience Workflows page.

    You are automatically logged into your Boomi portal from this page.

  2. In the Boomi portal, select the environment to add Jira Service Desk - Ticket Approvals workflow, either PROD or TEST.
  3. Click INSTALL A NEW INTEGRATION and in the Jira Service Desk - Ticket Approvals pane, click INSTALL.
  4. Configure the connector values required in the Jira Service Desk set up.
    Tab Action
    Jira Service Desk Enter your Jira Connector URL. For example, https://companyname.atlassian.net.
  5. Click Continue to configure the Jira Service Desk Properties page.
    Properties Action
    JSD BASE URL Enter the Jira URL. For example, https://companyname.atassian.net.
    CLIENT ID Enter the value from the Jira OAuth 2.0 (3LO) app.
    CLIENT SECRET Enter the value from the Jira OAuth 2.0 (3LO) app
    AUTHORIZATION CODE Enter the code that displays in the callback URL query.
    REDIRECT URI Enter the callback URL.
    WORKSPACE ONE ACCESS USER GROUPS Enter the user group that receives the notifications about Jira requests. You can add a comma-separated list of group names. Enter the Workspace ONE Access user groups that receives the notifications about Jira requests. To receive notifications, users must have the same email address in both the Workspace ONE Access service and the Jira Service Desktop system.

    You can add a comma-separated list of group names.

    If you do not enter a value, all users are queried and only those users that have the same email address in Jira Service Desktop and in the Workspace ONE Access service receive the requisition approval notification.

    INITIAL RUN DAYS (<=90) The default value is 7 days. This value is the number of days back to retrieve data or requisition from the Jira Desktop system. You can change this value. After the initial run, only the data from the last successful run is fetched.

    The Workspace ONE Access Properties settings TENANT URL, REMOTE APP CLIENT ID, AND REMOTE APP SHARED SECRET are preconfigured. Do not change these settings.

  6. Click CONTINUE to complete the installation.

Configure the schedule for the Jira Service Desk Ticket Approvals integration pack. Create a schedule in the [JIRA] Request Approval [Workspace ONE]] scheduler to send ticket approval request notifications. See Schedule to Run Integration Pack Processes in Workspace ONE Experience Workflows.