App Config Variables Settings

Overview

App Config Variables in Questetra BPM Suite allow you to centralize configuration values within the App Modeler and switch between testing and production without having to modify each process model manually.

They are especially useful for managing:

• Email destinations (e.g. test vs production)
• API endpoints
• Default values in forms
• Text content like URLs or signatures

By switching between Profiles in App Conf Variables Settings window, you can instantaneously change the data that is referenced in multiple input fields and in multiple Steps within a workflow at the click of a button. For example, in this way you can change the “To” address in a [Throwing Message Intermediate Event (email)] without touching the configs within the Step itself.

Step 1. Accessing App Config Variables

1. Open your workflow app in the App Modeler
2. In the Modeler, click App Config Variables which is located in the top right corner of the Modeler window
3. The window will show two configurable fields:
   • Profiles (top): A dropdown menu where profiles can be created and selected
   • Variable List (bottom): A list of Variables, and their Values which are associated with each Profile

Step 2. Creating Profiles

Profiles represent configuration contexts — for example:

• Test: values used during internal testing
• Production: values for live operations

How to add a profile:

1. Click “+” beside the Profile dropdown
2. Name the new Profile (e.g. Test_Environment, Production_Environment)
3. Profiles appear in the dropdown; you can switch between them anytime

Step 3. Adding Variables

Each Profile holds one or more Variables.

To add a Variable:

1. Click “+” in the Variables area
2. Set:
   • Variable Name: a unique identifier (e.g. Notification Email, API URL)
   • Value: the actual value (e.g. dev@questetra.com, https://api.test-server.com)
3. Repeat as needed for multiple variables

Step 4. Referencing Variables in the App

To make your app dynamically adapt based on the selected profile:

1. Open a Settings window for a step in your workflow (e.g. in a [Throwing Message Intermediate Event (email)])
2. Select the text field where a value is normally typed (like “To”, “Subject”, or “Body”)
   
3. Click [+Insert Reference] and choose your variable from the dropdown list that appears

In the list Variables appear near the bottom and are labelled “App Config Variable: [variable name]”. When selected it inserts an expression like: ${var[NotificationEmail]}

4. When the Process is run, Questetra replaces this expression with the actual variable value from the selected Profile

Step 5. Example Use Case

Profile	Variable Name	Variable Value
TEST	NotificationEmail	dev@questetra.com
PROD	NotificationEmail	info@questetra.com

If your Email Task uses ${var[NotificationEmail]}:

• Running under TEST → sends to dev@questetra.com
  

• Running under PROD → sends to info@questetra.com

This eliminates the need to manually edit each field during deployment.

Step 6. Tips & Advanced Uses

6-1. Debugging with Profiles

During debug execution, you can select which Profile to use.
This helps simulate different environments safely — e.g. testing an Inquiry Response flow with dummy addresses.

6-2 Customize Communication

When configuring [Throwing Message Intermediate Event (email)] steps, variables can be used in the “From” and “To” addresses, in the subject line and the text body. This can be useful in the following situations:

• Different email signatures based on the recipient
• Different senders for internal/external recipients
• Different support email addresses based on the region

Limitations

• Variables can’t be used in input fields that use dropdowns or radio buttons
• They work only in text fields
• Variables are unique to the Process Model/Workflow where they were created

Step 7. Benefits of Using App Config Variables

Benefit	Description
Centralized Configuration	Modify all key settings in one place instead of editing individual tasks.
Multi-Environment Management	Easily switch between testing and production setups.
Error Reduction	Avoid sending test emails to real users or hitting production APIs by mistake.
Faster Deployment	No need to re-publish the app just to change an address or endpoint.
Debug Flexibility	Test multiple scenarios quickly by switching profiles.

Step 8. Best Practices

1. Prefix variables consistently, e.g., API_, EMAIL_, URL_.
   
2. Review all variable references before publishing.
   
3. Test each profile to ensure values are correctly substituted.

Restrict debug data to safe addresses and dummy endpoints.

Summary

App Config Variables are a powerful tool for ensuring your Questetra workflows are:

• Safe during testing
• Flexible during deployment
• Maintainable across environments

By setting up Profiles and Variables properly, you’ll reduce operational mistakes and streamline app lifecycle management.