Languages, Themes and Small Screens
The Rule Repository adapts to the people who use it and the screens they use it on. It can show its text in your language, comes in a light and a dark look, takes its font from your application so it fits in, and rearranges itself on smaller screens, tablets and phones. Most of this is set up by your application; this page explains what you will see.
Languages
Every word the repository shows, from tab names and buttons to messages and tooltips, comes from one text file that your application can replace with a translation. The Rule Editor's words, such as the names of its operators and the hints in its Help String, come from a similar file of its own. A third file translates the names of the fields, methods and actions of your sources, so a field your developers called "Credit Score" can read "Kreditscore" for a German user. If your application provides these translations, the repository, its Rule Editors and your sources appear in your language.
A translation changes only what you read. Rules are stored once: a rule written by a colleague who works in French opens in your language, with the same fields and values. The Rule XML and Source XML tabs, which show what is stored, keep the sources' own names.
What a translation does not change:
- The names your organization gives things in the repository: rules, versions, notes, tests and the names of the source objects in the grids.
- The Danger Zone heading of a deletion's confirmation, which stays in English.
The AI Assistant understands your language. It knows your sources' translated names as well as their own, so you can ask for "Kreditscore" or "Credit Score".
Dates and Times
Dates and times are shown in your local time, for example "Nov 6, 2026, 02:13 PM". The repository keeps them in universal time, so people in different time zones see the same moment in their own time. Hover over a date in a dialog's header to see the exact time, with seconds.
Light and Dark Themes
The repository comes in a light and a dark theme, and its Rule Editors match it. Your application decides which one you see; some applications let you choose, for example from a setting.
The repository uses your application's font and text size, so it reads as part of your application.
Smaller Screens
On screens narrower than a typical desktop, the repository keeps everything working and makes room by tucking things away. When it does, a note at the top says "Some of the functionality has been hidden due to the screen size".
- Grid columns give way. When a grid is too narrow for all its columns, the least important ones are hidden first; the name of the record always stays. Sorting and filtering still work on hidden columns.
- Below about 1400 pixels wide, the row of tabs shows only the current tab and a ⋯ button that lists the others. The filters move behind one button, No filters... or Filtered..., which opens them in a small dialog with Cancel, Reset and Apply.
- Below about 1100 pixels wide, the checkboxes and buttons for comparing versions are hidden, and rules are drawn slightly smaller in dialogs.
Phones
On a phone, the repository is for looking things up and for quick changes rather than for testing:
- Dialogs stack their contents into one column.
- There are no Test or Test Result dialogs: the Test... buttons and New Test... are not shown, and tapping a row in the Tests or Live Evaluations grid shows the message "The requested functionality is not available due to the screen size".
- Show related... is not shown in dialogs.
- The grids have no checkboxes, so batch runs and comparisons are not available.
- The AI Assistant shows the conversation without the Steps pane.