Box

Use the IBM® App Connect Enterprise Toolkit to configure message flow nodes that are converted from the IBM App Connect Professional Box activities.

About this task

When you import an orchestration that contains Box activities, the conversion utility creates a message flow with the Box Request node. See Table 1, for information on which activities this node is used for.

Table 1. IBM App Connect Professional Box activities and the corresponding IBM App Connect Enterprise message flow nodes
IBM App Connect Professional activity IBM App Connect Enterprise node
Add Users To Group

Box Request node
Update files

Box Request node

Box Request node is used in IBM App Connect Enterprise for all the activities of Box.com connector in IBM App Connect Professional.

For performing any action in Box, first you need to connect to Box.com.

The following link shows all the Box activities in IBM App Connect Professional: https://www.ibm.com/docs/en/app-connect-pro/7.5.5?topic=studio-boxcom-activities

The following link shows all the Box activities in IBM App Connect Enterprise: https://www.ibm.com/docs/en/app-connect/13.0.x?topic=nodes-box-request-node

Connecting to Box

Procedure

  1. Select the Box Request node in the message flow.
  2. In the Properties tab, click Launch connector discovery to open the wizard.
    App Connect Enterprise toolkit showing interface for specifying Box request node properties
  3. Select a Box policy project from the drop-down menu or create a new one. Box connection information to be saved in a policy. Interface for specifying the name of the policy project Interface for specifying the name of the policy project
  4. Click Test Vault Access to check whether vault credentials are correct. If not, type the credentials. The vault is used to store the Box connection credentials. The process of connecting to Box and discovering information from it saves your Box credentials in the vault.
  5. Click Launch Discovery. A new configure connector node window opens. Interface for specifying policy project with vault key field completed
  6. If you previously connected to a Box system, then a list of those connections would be displayed. If you did not previously connect to a Box system, then the status of the Box connector is shown as Not connected. Connector discovery window with a drop-down list of Account options displayed
  7. If you did not previously connect to a Box system, then follow these steps:
    1. Expand Not connected, expand any section (for example, Files) and choose any action (for example, Retrieve file metadata).
      Connector discovery window showing drop-down list of options of actions to carry out in the Files section
    2. The list of objects and actions are replaced with a Connect button. Click Connect. Connector discovery window with connect button displayed
  8. If you previously connected to a Box system and want to add an account, follow these steps:
    1. Expand Box.
    2. In the drop-down in Account, the current Box account shows as selected. Click the drop-down and select Add a new account.
      Connector discovery window with a drop-down list of Account options displayed
  9. Complete the requested connection information for your Box account, including the access token, request token, client ID and client secret.
    Interface for specifying Microsoft Exchange connector details
  10. Click Connect to verify the connection, then close the window.

What to do next

Note: For all actions with Box, apply the following steps, then continue on to the steps specific to each activity:
  • Select the node in the message flow.
  • In the Properties tab, click Launch connector discovery to open the wizard.
  • Select a Box policy project from the drop-down menu or create a new one.
  • Click Test vault access to check whether vault credentials are correct. If not, type the credentials of the vault you are using.
  • Click Launch discovery. A new configure connector node window then opens.
  • If you previously connected to a Box system, then a list of those connections would be displayed. If you did not previously connect to a Marketo system, then the status of the Box connector is shown as Not connected.
  • Expand the Box section and select the Box account that you want to connect to.

Box Request node for add users to group activity

Procedure

  1. Expand Group membership and choose Create group membership.
  2. Expand Controlsselect a suitable option when asked how you want to populate the target fields in Box.
    1. Option 1: Define mappings. Specify data for required target fields (User ID and Group ID). You can also specify data for any optional fields that you want to use for the target application. You can type the values in the fields or map the values from previous nodes. If default value is available use it, otherwise use the previous nodes output. Refer to the generic documentation on How to Add the Previous Node's Output .
    2. Option 2: Use the input message unchanged.
  3. Click Save and close the window.
    Screenshot of connector discovery window

Box Request node for update files activity

Procedure

  1. Expand Files and choose Update files.
  2. Expand Controlsselect a suitable option when asked how you want to populate the target fields in Box.
    1. Option 1: Define mappings. Specify data for any required target fields. You can also specify data for any optional fields that you want to use for the target application. You can type the values in the fields or map the values from previous nodes. If default value is available use it, otherwise use the previous nodes output. Refer to the generic documentation on How to Add the Previous Node's Output .
    2. Option 2: Use the input message unchanged.
  3. Set the conditions, either by typing the values in the fields or map the values from previous nodes. Specify the file ID as condition.
  4. Click Save and close the window.
    Screenshot of connector discovery windowScreenshot of App Connect Enterprise toolkit with example message flow Screenshot of connector discovery window with ID in put box highlighted