Creating Deployments

Deploy your application for testing or production purposes by creating a new deployment. If your application has more than one revision, you may choose to deploy any specific revision, the latest revision, or even multiple revisions of the same application.

The following fields will be displayed:

  1. Deployment Label: Enter a label for the deployment. These labels are useful for managing and organizing deployments if you wish to deploy the same revision of an application multiple times.

    • Example: If you have two deployments of the same application, one for production and another for testing, you can label the first "Production" and the second "Testing".

  2. Select Application: Select the desired application for deployment. The dropdown list auto-populates with applications on your account.

  3. Select Revision: Select a revision of your application. The dropdown list auto-populates with all revisions of the selected application. By default, Fuse selects the latest revision.

  4. Set Deployment Var(s): (Optional) Enable or disable deployment variables in this deployment. Deployment variables allow you to override application variables to use the values set here. Please see Deployment Variables below for full details on how this feature works.

    Default setting is No. If set to Yes, a table will be added with a new deployment variable entry. The following table fields will be displayed:

    • a. Module: Choose a module with a variable that can be overridden. All such modules will be listed automatically. The first one in the call flow is selected by default.

    • b. Variable: Choose a variable to override from the selected module. All variables that can be overridden will be listed automatically. The first one is selected by default.

    • c. Application Value: Displays the current value of your selected variable. This field cannot be edited.

    • e. Add: Add a new deployment variable entry to the table.

  5. Select Token: (Optional, only if Stripe is enabled) This option will only show if Stripe integration has been enabled in your account. You can select the OAuth token you created in My Account if your application requires the Stripe token for deployment.

    To enable Stripe on your account, please contact Plum Support.

  6. Outbound deployments do not require any phone numbers to be selected.

  7. Private Logging: (PCI accounts only) This option is visible only to customers with accounts labeled as PCI. Select it to enable an in-call, failsafe override that privatizes all modules in the deployment.

Deployment Variables

What are they? The deployment variables feature allows you to select and override an application's variables with new values during deployment. Your selected application and revision must contain at least one module with one variable that can be overridden. The application itself will remain unchanged.

Modules that cannot be overridden include ones that accept user input (e.g., Menu).

When to use them. Deployment variables are useful when you want to change application variables across one or more deployments without editing the actual application itself. You can also use deployment variables to reduce application overhead: if an application's variables are in place, you can set their unique values as deployment variables while creating a deployment.

For example, say your application uses a Transfer module with a variable for the destination number. Next, say you wanted to deploy that application with a different destination number. Instead of editing the application, create the deployment and set a deployment variable that overrides the original number with a new one.

Setting up a deployment variable. After setting Set Deployment Var(s) to Yes, follow these steps:

  1. Under Module, select a module containing your target variable.

  2. Under Variable, select the variable you want to override.

  3. Review Application Value to confirm that you selected the correct variable.

  4. Under Deployment Value, enter the value to override the one under Application Value.

  5. Add more deployment variables as needed by selecting the Add button.

  6. Configure the rest of the deployment as desired, then select Deploy.

Last updated