Skip to main content
Task Management in FlowX.AI includes comprehensive localization capabilities, allowing you to deliver fully translated task management interfaces in multiple languages. Configure 51 FlowX substitution tags in CMS for each language you want to support.

Localization approach

Task Management localization operates through FlowX Substitution Tags:

FlowX Substitution Tags (51 Keys) - manual configuration

Custom Task Management UI elements that must be configured manually in CMS for each language:
  • Table column names (title, stage, assignee, status, priority)
  • Task actions (assign, unassign, hold, execute)
  • Bulk operations (assign all to me, unassign all, hold all)
  • History events and status values
  • Comments and user selection dialogs
If you need to configure FlowX substitution tags default text values (51 keys) in CMS, you can do so by navigating to CMS → Substitution Tags and adding the default text values for the substitution tags.

FlowX substitution tags

FlowX substitution tags control custom Task Management interface elements outside the data table. These 51 tags must be configured manually in CMS for each language.

Complete tag reference

Search & Navigation
  • sys_tm_search - “Search”
Table Columns
  • sys_tm_title - “Title”
  • sys_tm_stage - “Stage”
  • sys_tm_assignee - “Assignee”
  • sys_tm_status - “Status”
  • sys_tm_priority - “Priority”
  • sys_tm_last_updated - “Last updated”
Manual Configuration Required: All 51 FlowX substitution tags must be configured manually in CMS for each language you want to support. They control custom Task Management UI elements outside of the data table.

Implementation guide

To localize Task Management, configure the 51 FlowX substitution tags in CMS for each language you want to support.
1

Add FlowX substitution tags to CMS

For each supported language:
  1. Navigate to CMS → Substitution Tags
  2. Add values for all 51 sys_tm_* tags for the target language
  3. These control custom Task Management UI elements:
    • Task actions (assign, hold, unassign)
    • Bulk operations (assign all to me, unassign all, hold all, unhold all)
    • History events (task created, user created this task, started process instance with id, started process instance on build, task ownership changed to, task moved to, task status changed to, task assigned to, task owner removed)
    • Comments section (comments, write a comment…)
    • User selection dialogs (select person, search users, search term validation)
    • UI states (loading, nothing found)
    • Data display (in, yes, no)
2

Configure custom column names (Optional)

If you need columns beyond the default ones:
  1. Define custom parameters in Process Settings → Task Management
  2. Use substitution tags for column display names
  3. These tags will also need CMS translations for each language
  4. When you configure the column display name, use the substitution tag for the column name( it is called using ”@@” prefix)
3

Test localization

Verify that Task Management is properly localized:
  • Task action buttons (assign, unassign, hold, execute)
  • Bulk operation buttons (assign all to me, unassign all, hold all)
  • Task history timeline and status values
  • Comments section and user assignment dialogs

Localization best practices

1. Maintain consistency

Ensure translation consistency across:
  • CMS substitution tags
  • Custom column display names

2. Handle dynamic content

For history events and comments that include dynamic values (user names, dates, IDs), use the variable placeholders:

Localization by component

Task list view

Task details panel

Bulk operations

Search and sort on translated labels

SaaS ¡ 5.13
Available on SaaS with FlowX.AI 5.13. This feature is live on managed (SaaS) deployments now. Self-hosted deployments will receive it with the next LTS release family.
The task list searches and sorts on the labels it displays, in the language the task list is shown in, instead of on the values stored on the task. A user who types a word they see in the grid, in their own language, finds the matching tasks. This applies to columns that display a label:
  • Status: matched and sorted on the translated sys_tm_* status labels. With the Romanian example below, searching Finalizat finds finished tasks.
  • Enumeration columns: matched and sorted on the enumeration labels for the viewer’s language.
  • Text columns that hold a substitution tag: a value stored as a substitution tag is matched and sorted on the tag’s translated text. Ordinary text values match as before.
How each operation behaves on these columns:
  • Search box: partial, case-insensitive match against the label. A value displayed as a label is found through its label, not through the stored code.
  • Text filters: filters applied in the task list match the labels the same way. Filters saved in a view’s Dataset Config keep comparing the stored values, so existing views return the same tasks. Filters on enumeration and status columns, which you pick from a list, work as before.
  • Sorting: tasks are ordered by the displayed label, ignoring letter case. Tasks with no value in the sorted column are listed last, in both ascending and descending order.
In a running app, the labels come from the build the app runs. In FlowX Designer, they come from the app version you are editing.
If the task list has no language set, or its labels can’t be read, search and sort use the stored values, as in earlier versions. An enumeration value or status that has no label in the viewer’s language is matched on its stored value. A text value stored as a substitution tag that has no translation is displayed empty, is not found by search or text filters, and is sorted with the empty values.

Troubleshooting

Problem: Task actions, history, or comments display in English.Solutions:
  1. Verify all 51 sys_tm_* tags are configured in CMS
  2. Check that translations exist for the current user’s language
  3. Ensure CMS language codes match your application’s language selection
  4. Verify substitution tag syntax is correct (no typos)
Problem: Some elements in one language, others in another.Solutions:
  1. This indicates incomplete CMS configuration - likely missing FlowX substitution tags
  2. Verify all 51 sys_tm_* tags are translated in CMS for the target language
  3. Use browser dev tools to identify which specific elements are untranslated
Problem: Custom columns display original names instead of translations.Solutions:
  1. Ensure custom column display names use substitution tags
  2. Verify those substitution tags are configured in CMS for all languages
  3. Check that column configuration points to correct substitution tag keys

Example: complete Romanian localization

Here’s an example of configuring Task Management for Romanian language:
1

Add Romanian CMS translations

In CMS, add translations for all 51 tags:
2

Verify complete localization

Test all areas to confirm:
  • ✅ Task actions show Romanian labels (from CMS)
  • ✅ History events display in Romanian (from CMS)
  • ✅ Comments section uses Romanian labels (from CMS)

Additional resources

Task Management Overview

Learn about Task Management features and configuration

CMS Substitution Tags

Configure substitution tags in Content Management System
Last modified on September 29, 2026