In addition to using out-of-the-box integration packs that are available from the Hub Services Experience Workflows page, you can customize the integration packs to meet your company requirements and build your own integrations.

To edit out-of-the-box integration Boomi processes, you launch the Boomi AtomSphere platform from the Experience Workflows>Services & Resources section in the Hub Services console. In the AtomSphere platform, you edit, deploy, and configure the custom integration pack in the following sequence.

  1. You find the out-of-the-box Boomi process to install in AtomSphere in the Process Library. In Filter by Publisher, select VMware-Primary.
  2. You create an installation folder and copy the out-of-the-box files to the folder. The copied processes in the folder include the main process file and sub files used to create the notification cards in Workspace ONE Intelligent Hub and the action process file and sub files that are used to listen for response actions taken on the cards.
  3. You then create the API service component in that installation folder, configure the API path to the business system, and in the API REST tab, import the listener process as the REST endpoint.
  4. In the AtomSphere Build page Process canvas, you edit the processes to customize the workflow.
  5. You package and deploy the edited process components to a test or a production environment.

See the Boomi documentation for information about creating and editing integration pack processes. The steps here guide you through the sequence to prepare the integration back to be edited and deployed. These steps do not describe in detail how to change the processes.

Editing an Existing Out-of-the-Box Integration Pack Workflows



  1. Navigate to the Hub Services console Experience Workflows page.
  2. In the Services & Resources > Custom Workflows pane, click LAUNCH.

    The Boomi Integration AtomSphere dashboard displays.

  3. In the Build tab in the left navigation pane, create a folder for the installation of the Boomi process you are going to edit.
  4. To find the Boomi process to edit, in the bottom left corner of the page, click Browse Process Library .
  5. In the right column, select to filter by VMware-Primary, to see the list of Workspace ONE Experience Workflows out-of-the-box integrations Boomi processes.
  6. Select the Boomi process to edit and click Install. Select the folder you created and then click Install.

    The main and listener processes and sub processes are copied to the folder.

  7. Click View Process to open the main process in the process canvas.
  8. To add the listener process as the REST endpoint, create the API service component.
    1. Click +New and in the Create Component box, select API as the type of component to create
    2. Enter a name for the API service component in the Component Name text box. For example, if you are editing the Coupa integration pack, the component name can be CoupaAPI.
    3. Select the integration process folder you are working in.
    4. Click Create. The API service component is created and the API Service Configuration page displays.
  9. In the API Service Configuration page General tab configure the following.
    • In the Published Metadata section, enter the Published API Title and Published Version Number.
    • In the Service Configuration > Base API Path, enter the Base API Path for the business system you are editing. You must enter one of the following base API paths, based on the business system integration pack you are editing.
      Business System Integration Pack Name Base API Path
      Coupa CoupaAPI
      Concur ExpenseApi
      Salesforce Opportunity Discount Approval CreateNotification
      ServiceNow Service_Now
      Jira Service Desk Ticket Approval Jira
      Zoom Meeting Recording ZoomAPI
    • In the Advanced Settings > Dynamic Document Property headers, click Add Header. In the first text boxes enter X-WS1-User-id and in the second text box enter X-WS1-User-Email. These header values are the same for all processes you edit.
  10. Select the REST tab and click Import an Endpoint.
  11. In the Import an Endpoint page, select Use an existing process. Click Next.
  12. In the Use an Existing Process section, use the Process text box to search for the action process in the installation folder you created, and select the REST check box. Click Finish.
    Note: The action process file name to select begins with [Workspace ONE]. For example, with Coupa, the label is [Workspace ONE] Requisition Approval Action[Coupa].
  13. The REST Configuration page displays the path to the REST endpoint you imported. Click Save and Close.

    The API is added to the process folder that you are working in and the integration pack you are editing displays in the AtomSphere Build page.

  14. In the AtomSphere Build Process canvas, edit the process to change the workflow.

    Make sure that you add the extensions to test the process, from the AtomSphere Build canvas after you make the changes, and before deploying.

Use [Workspace ONE] Push Notification as a Quick Start Process to Build Your Own Integration

You can use [Workspace ONE] Push Notification from the Boomi process library as a quick start process to build your own integration. This is a ready-made library to create notifications in the Workspace ONE Intelligent Hub app for different business systems.

You start by launching the Boomi AtomSphere platform from the Experience Workflows>Services & Resources section in the Hub Services console. Follow the process sequence described in Editing an Existing Out-of-the-Box Integration Pack Workflows section to create your integration. After the integration you build is installed from the process library, you can modify the process to create business system data in a format that is specified in the Message Shape. More technical details related to the format are described in the process itself. When the process is modified and completed, package and deploy your process as described in the Package and Deploy Your Edited Workspace ONE Experience Workflows Process section.

Package and Deploy Your Edited Workspace ONE Experience Workflows Process

After you edit and save the processes, you create a packaged component and deploy the package from the Atom environment.



The procedures in these steps are not detailed steps about how to configure in the AtomSphere platform. These steps show the general flow of what you do to set up the edited Boomi process to integrate with the Workspace ONE Intelligent Hub app. See the Boomi AtomSphere documentation for detailed steps.

  1. Create the packaged components. To create the packaged component, go to the AtomSphere Dashboard > Deploy > Packaged Components tab. Click Create Packaged Component and then select the following components from the installation folder.
    • Main process component. Example of a main process component file name, [Coupa] Requisition Approvals [Workspace ONE]
    • Action process component. Example of an action process component file name, [Workspace ONE] Requisition Approval Action [Coupa]
    • API Service component. Example of the API service component file name, CoupaAPI.

    See the Boomi documentation about how to package components.

  2. When the packaged component is successfully created, go to Deploy > Deployments and click Deploy Packaged component. For example, for Coupa, select [Coupa]Requisition Approvals [Workspace ONE. The environment is either Test or Production.
  3. After the packaged component is deployed in the environment, go to Manage > Atom Management. Click on the environment that you selected in the previous step. Under Administration, click Environment Extensions. The Environment Extension dialog opens.
    Note: You must have Atom Management privileges and Environment Management privileges to configure these settings.
    1. In the Extensions form Process Filter text box, select the Main process component name from the integration process you are configuring.
      Note: When you configure the Main process connector component, the same values are added to the Action process connector component.
    2. The Connections Settings page is preconfigured with the URL values required for the business system integration set up.
      • Business system connector URL
      • Workspace ONE Hub Services Patch connector URL to call the PATCH API.
      • Workspace ONE Hub Services Token connector URL to call the Hub API.
      • Intermediate Data Storage Connector to call Redis cache

    The Use connection component value check box is enabled by default. Deselect this check box.

  4. In the Extensions form, select Process Properties. In the Process Property text box, the select either the business system properties to configure or the Workspace ONE Access properties.
    1. For business system properties set up the properties that are displayed. The properties required to be set up are based on the business system requirements.
    2. For the Workspace ONE Access properties, the following property values are pre-populated.
      • WORKSPACE ONE ACCESS REMOTE APP CLIENT ID. This is the OAuth2 client ID name HubServices_Boomi_Integration that is registered in Workspace ONE Access.
      • WORKSPACE ONE ACCESS REMOTE APP SHARED SECRET. This is the secret of the client ID.

Setting Up Experience Workflows Process Schedules

After editing and deploying the process, schedule the process to run automatically.

Note: You do not schedule the action component process because the action process listens for responses in real-time.

You create and manage the process schedules in the Atom Management Environment pages where you deployed the process.

You configure a schedule with the time, days, and intervals at which the process is run.

To set up the schedule, go to the Manage>Atom Management page and in the Deployed Processes panel, click the blue arrow icon and select Edit Schedules. The Scheduling dialog box set the schedule. See the Boomi AtomSphere documentation for details.

Managing Experience Workflows Process You Edit

Deployed customized Experience Workflows processes are managed and scheduled only through the AtomSphere platform. To make changes or to see the list of Experience Workflows processes that you deployed in AtomSphere, go to the Hub Services>Experience Workflows tab and in the Services & Resources > Custom Workflows pane, click LAUNCH. The AtomSphere dashboard is displayed. Navigate to Manage > Atom Management > Environments > Deployed Processes.