Skip to main content
Version: Release 24.3

Feature settings

The Feature Settings page allows you to toggle or configure the optional features in Digital.ai Release.

To configure the feature settings, from the navigation bar, click Settings > System Settings, and then click Feature flags tab.

note

The Feature flags page is only available to users who have the Admin global permission.

To configure the feature settings, from the navigation bar, click Settings > System Settings, and then click the Feature flags from the left pane. The Feature flags page is only available to Admin users only. For more information, see global permission.

The Feature flags page has Stable and Incubating tabs.

Note: The features in the Incubating tab are in Technical Preview.

Stable Tab Settings

Go to Settings > System settings > Feature flags > Stable.

External ID for User Profile

You can use the External ID field to add additional details for the external users as per your requirement. For example Employee id or GitHub id.
To add this feature to the User Profile,

  1. Select the Show External ID checkbox.
  2. In the Label field, enter the label for external Id.
  3. Click Save.

External id

Limit Folder Depth in Release

A nested folder structure with more than five or six levels becomes cumbersome to deal with and can adversely impact the performance and lead to the following issues:

  • General slowness
  • High CPU usage
  • CLI tasks become unreliable
  • Create release task is not usable

Configure the folder depth in Release via Settings > System Settings > Feature Flags > Set Limits within release section:

  • Select the Enable checkbox to enable this feature and limit the folder depth based on the value set in the Max folder depth field.
  • Set the folder depth value in the Max folder depth field.

Note: The default folder depth is set to 5. However, admin users can increase the folder depth to more than 5 based on the requirements.

Folder Depth Limit in Release

Limit Minimal Trigger Polling Interval

Currently, the minimum polling interval for triggers is 1 second. This causes increased load in Release and other third-party systems. To overcome this performance issue, the minimum polling interval for triggers is changed to 60 seconds.

Configure the minimum polling interval in Release via Settings > System Settings > Feature Flags > Set Limits within release section:

  • Set the minimum polling interval value in the Min trigger interval field.

Limit Minimal Trigger Polling Interval

Enhancements to Triggers

You have the option to set the maximum number of trigger failures that can occur before a trigger is disabled. To configure this value, navigate to Settings > System settings > Feature Flags. In the Set Limits within release section, you can enter a value or select an option from the drop-down menu for the Consecutive trigger failures field. The default value is 100.

Task Drawer Updates

Furthermore, when a trigger is disabled, a notification is sent to the System Administrator.

New Home Page Dashboard

You can now see a new home page dashboard with customizable tiles. Enable or disable this option by using the Show Home page checkbox in the Feature flags section. This is enabled by default.

New Home Page Dashboard Checkbox

Product Analytics and Guidance Feature

This feature delivers in-app walkthroughs, guidance and release notes in Release using the Pendo.io platform. Anonymous usage analytics are collected in order to improve the customer experience and business value delivery.

See Pendo analytics and guidance for more information.

  • You can enable or disable the Product Analytics and Guidance feature from the Product analytics and guidance group by selecting or clearing the Analytics and guidance check box.
  • Product analytics and guidance is enabled by default.
  • By default, the feature is active for all users in the Release instance.
  • select the Allow users to opt-out check box to let individual users opt out of sharing usage analytics (via the User profile page).

Preserve Output Variable on Failure for Custom Script Tasks

If a custom script task fails, there is an option to preserve any output variables that are created before the failure. There are two ways to configure:

  • This setting is configurable in xl-release.conf file. The default value is false.
  • You can also enable or disable it in Feature Flags > Stable > Custom script task using the Preserve output variable value checkbox.

Custom script task

When this checkbox is selected, and if the Custom Script task fails without exception, output variable values set before failure will be preserved.

Note: This setting is global and applies to all the Custom Script tasks.

GitOps-enabled Version Control

GitOps-enabled version control allows you to store folder content like templates, variables and configuration as YAML code in Git and enables a GitOps style workflow to author, review and promote content between Release environments.

GitOps-enabled

Enable or Disable Task Drawer for Tasks—Users With Administrator Permissions

  1. Log in to Digital.ai Release.

  2. On the top-right corner, click Settings > System settings.

    The System settings screen appears.

  3. Click Feature flags from the left-navigation bar.

  4. Select the Stable tab.

    In the Task details (redesigned UI) section, the Use new Task details version check box is selected by default. This means the new Task Drawer for tasks is enabled by default.

    Note: If you want to use the Task Modal for tasks instead of the new Task Drawer, clear the Use new Task details version check box and click Save.

Enable or Disable Task Drawer for Tasks—Opt Out of Task Drawer

Digital.ai Release 23.1 and later allows non-admin users to enable or disable the Task Drawer feature. This is possible if and only if your Administrator has enabled the new Task Drawer and you want to opt out of it in favor of the Task Modal.

  1. Log in to Digital.ai Release.

  2. In the Profile page, under the New UI for task details section, clear the Use task drawer check box to opt out from the Task drawer and use the Task modal instead.

    Task drawer individual visible

Incubating Tab Settings

Go to Settings > System settings > Feature flags > Incubating.

Reload Jython Modules

Important: Do not use this feature in production environments.

Reload jython modules

Select the Reload jython modules checkbox to enable the reload of jython modules when a plugin is installed. It means that you can install the Jython plugins without a server restart.

Note: You must restart the server for JAR-type plugin uploads.

Strategy to Schedule Jobs

Scheduling strategy is an algorithm that is used in Release to determine whether certain jobs should be delayed or executed immediately.

Navigate to System settings > Feature flags > Incubating > Internal scheduling settings section.

Important: Contact Digital.ai Support to understand and use this setting.

Strategy to Schedule Jobs

You can select a strategy on how the jobs can be scheduled for execution. Select one of the strategy from the Scheduling strategy drop-down list.

  • No backpressure—does not delay the execution of jobs in case the Release server is overloaded.
  • Blocking backpressure—delays the execution of jobs in case the Release server is overloaded.
  • Non-blocking backpressure—delays the execution of jobs in case the Release server is overloaded for a specific period of time.

When you select the Non-blocking backpressure strategy from the drop-down list, a new field called Sleep duration is enabled and you must set a value in milliseconds. This value defines the no of milliseconds that Release must wait to re-run the jobs.

Also, you can change to any of the three options without any restart to your Release server.

Non-blocking backpressure

Monitor Status of Deployment Applications

  1. Log in to Digital.ai Release.
  2. Click Settings > System settings. The System settings screen appears.
  3. In the left-navigation bar, click Feature flags.
  4. Select the Incubating tab.
  5. In the DevOps enabled deployments overview section, clear the Show live status checkbox. This disables the Application deployments dashboard.
  6. In the Application pipelines tag field, Application pipelines templates tag is available by default. Keep this handy, to use it in the tags field of your Release.
  7. Click Save.

Database Query Logging

Navigate to System settings > Feature flags > Incubating > Database query logging section.

Log SQL Statements

By default, you cannot log any database statements. But now, you can select the Log SQL statements checkbox to log the SQL statements. You can enable this to query the statements that are taking more time than defined in the Execution threshold field.

In the Execution threshold field, specify a value in milliseconds. For example, if you set a value of 5000 ms, then only SQL statements which have crossed 5000 ms are logged.

Select the Log parameters checkbox to log the SQL statements with the parameter values. Clear this checkbox to log them without the parameter values.

Release Load Options

  • Unlike Release 22.3 and earlier with which task dependencies were loaded one-by-one, you can now batch-load task dependencies with Release 23.1 and later.
  • To optimize the number of select statements that are processed, you can batch-load task dependencies along with the Release.
  • This means that the dependencies can be loaded simultaneously with the Release, resulting in more efficient processing.
  • Enable this feature by selecting the Batch load dependencies check box.
  • This setting is enabled by default.

Optimized Permission Checker

Navigate to System settings > Feature flags > Incubating > Permission settings section to enable or disable this option.

Note: Contact Digital.ai Support before modifying this feature.

Permission setting

The new permission checker implementation improves the performance by making the API calls faster.

The Use cache checkbox is selected by default. This feature improves the performance by enabling the internal caching feature in Release while multiple permission are enabled in the background.