FME Flow: 2026.1

Workspace Apps

Select Flow Apps > Workspace Apps tab.

Workspace apps allow FME Flow clients to run workspaces from a web browser. The "apps" are shared as URLs, and may be presented through customizable web pages.

Tip   
  • You can provide your clients with access to multiple workspace apps and other links from a single, customizable web page. For more information, see Gallery Apps.
  • Workspace apps provide some Progressive Web App (PWA) features, such as Add to Home Screen (A2HS). For more information, see this FME Community article.

The Workspace Apps tab of the Flow Apps page lists the workspace apps that have been created.

By default, all apps are enabled to run when created. Disabled apps do not run. To disable or enable an app, select an app, then select Actions > Disable or Enable.

From the Actions menu, you can also Remove an app or Change Expiration of an app.

To view and run an app, or copy an app's URL, click the View or URL icon of the corresponding app, respectively.

To edit a workspace app, click on it.

To Create a Workspace App

  1. Click Create under the Workspace Apps tab. Alternatively, to duplicate an existing workspace app and revise, select an app, and select Actions > Duplicate. The Create Workspace (or Duplicating) App dialog opens. Complete or update the following:
    • Name: Provide a name for the app. The name appears on the run page for the app. App names are case-insensitive.
    • Title (optional): Provide a title for the app. The title appears in place of Name on the run page for the app.
    • Description (optional): Provide a description for the app. The description appears on the run page for the app. Use the toolbar widgets to customize the appearance of the description, as desired.
    • Repository: The repository of the workspace you want the app to run.
    • Workspace: The workspace you want the app to run.
    • Service: An FME Flow service that the workspace is registered to run.
    • App Security: Specifies who has access to the app.
      • Public: Full access to the app is provided to anyone with the URL.
      • Private: Full access to the app is provided to the Roles and/or Users specified under Allowed Roles and Allowed Users. Users must first log in to FME Flow with their username and password before access is granted. Access is denied to all others.
    • User Can Upload: If the workspace uses the Data Upload Service, this setting allows users to upload temporary files that are used to run the workspace.
  2. Parameter Defaults: If the workspace has user parameters, configure the default values for each one when the app runs.

    3. To revert to the original default values of the workspace, click Reset Values.

    Note  If the workspace is republished to FME Flow with new default values for user parameters, the values specified for this app are not affected, unless you click Reset Values.
    • Show in App: If checked, the app allows the user to explicitly specify a value for the parameter, or accept the default value. If unchecked, the app page does not display the parameter, and the app runs according to its default value.
  3. Dynamic Parameter Configuration
    • Enable Dynamic Parameters: If enabled, allows you to use a JSON schema to change default values or available choices of user parameters dynamically at runtime. For information about working with the schema, click View Guide.

      • The Dynamic Parameters guide provides assistance in three tabs:

      • Schema Guide: Explains the dynamic parameters JSON schema, with an example.
      • Generate Configuration: If Enable Configuration Loading at Launch is enabled, this tab allows you to generate a dynamic parameters JSON configuration for any of the current set of user parameters.
        • Parameters: Select the user parameters you want to configure dynamically in the JSON schema.
        • Schema Sample: The JSON schema populates the user parameters selected in Select parameters to configure (above) with the values specified under Parameter Defaults. You can manually update these default values and make any other adjustments to the schema as desired. When finished, test and download the schema as follows:
          1. Click Test. The dialog displays the parameter configurations that are found. To see these parameters as they would appear in the app, click Preview. To close the view, click Close.
          2. To download the configuration as a JSON file, click Download JSON.
      • Generate URL Config: If Enabled URL-Based Configuration (below) is enabled, this tab allows you to generate a static URL from a JSON parameter configuration.
        • Parameter Configuration Schema: Paste a user parameter configuration in the form of a valid JSON schema. For assistance generating the schema, use the Generate Configuration tab (described above). When finished, click Generate Url. The URL appears below. Click on the URL to open it in your browser. To copy, click Copy Url.
    • Enable URL-Based Configuration: If enabled, a URL pushes URL-encoded JSON parameter configurations to launch the app. The URL must supply the configurations through a query string parameter named dynamicParameterData. For assistance generating the URL, click View Guide (see "Working with View Guide," above).
      • Allowed Parameters: To ensure security of the URL, specify the user parameters the URL is allowed to push.
    • Enable Configuration Loading at Launch: If enabled, the app pulls JSON parameter configurations when it launches. Configurations are pulled from the specified Data Source: 
      • Resource: Parameter configurations derive from a JSON schema in Resources.
      • Workspace: Parameter configurations derive from a workspace that returns the required JSON schema.
        • Repository: The repository containing the Workspace.
        • Workspace: The workspace from which parameter configurations derive.
      • URL: Parameter configurations derive from the specified URL, such as an external web service or Data Virtualization endpoint.
      Tip  To display the parameter configurations from the specified Data Source, click Test. To see the parameters as they would appear in the app, click Preview.
  4. Resource Permissions: If the designated Workspace requires access to Resources in addition to those specified under Parameter Defaults, click Add Resources to specify the Resources folder that app users have permission to access. In the Select file for dialog, click the plus (+) icon beside each Resources folder to add. When finished, click Confirm.
    5. Warning  Access is granted to an entire Resources folder. For maximum security, create your own Resource Connection and, in that folder, place only those files to which you want to grant access.
  5. Connection Permissions: If the designated Workspace requires access to additional Database Connections or Web Connections, click Add Connections to specify the connections that app users have permission to access. In the Add Connections dialog, click the plus (+) icon beside each connection to add. When finished, click Add Connections.
  6. Customize (optional): You can customize various elements of the run page for the app. Alternatively, to specify that the app should run as soon as its URL is invoked, without displaying a run page, enable Run Immediately (at bottom).
    7. Note  Icon, Logo, and Banner fields support only .jpg and .png files.
    • Browser Icon: A clickable icon to reference the app URL.
    • Heading Background Color: A background color to comprise the banner at the top of the app page. Appears behind Heading Banner, if transparent.
    • Heading Logo: Appears over Heading Banner and/or Heading Background Color, centered.
    • Heading Banner: An image to comprise the banner at the top of the app page. If transparent, appears over Heading Background Color.
    • Footer Text: Appears beneath the Links on the app page. Use the toolbar to customize as desired.
    • Footer Logo: Appears beneath Footer Text, and behind Footer Banner, if transparent.
    • Footer Banner: An image to comprise the banner at the bottom of the app page. If transparent, appears over Footer Logo.
    • Log Debug: When enabled, records additional information to FME Job Logs. This setting is best used when an error has previously occurred and you seek further information.
    Note  Log Debug may cause slower workspace performance and large log file sizes.
  7. Click Create. A message appears to indicate the app is created, along with the app URL. Click Copy to copy the URL. To run the app, click the URL.

    8. Note  Other permissions may still be required, and you may need to further test and adjust the given permissions. For more information about permissions in FME Flow, see Role-Based and User-Based Access Control.

  8. Click Close. The Flow Apps page re-opens and lists your new app on the Workspace Apps tab.