Breadcrumbs

⚠️ Current Limitations

The EnhancedScheduler currently has some limitations that will be addressed in future updates:


📅 Unsupported Event Types

  • "Week And Day" Types: Events that repeat on both a weekly and daily basis are not yet supported.

  • "Custom" Types: Custom events based on specific criteria cannot be created at this time.


❗ Unsupported Combinations

It is possible that certain event combinations are not supported by the EnhancedScheduler. If this occurs, the user will be notified with an error message. If you need to create a special event with a combination that exists in the Niagara view but is not supported in the EnhancedScheduler, please contact us so we can find a solution.


📝 Editing MultiDays Events

  • It is not possible to move the start date of a MultiDays event to a previous day. However, you can still adjust the start time within the original start day.

  • Creating or editing a MultiDays event over a long period (e.g., one month) can take a considerable amount of time because each day's creation is a separate request in the current implementation.


🌐 Lexicon Behavior in the Workbench

Since Niagara 4.14, the language used for lexicons in the Workbench no longer depends on the locale defined in the Workbench settings (Tools > Options > Locale), but rather on the language set at the user level (Services > UserService > <UserName> > Language).

This can cause inconsistencies in the interface — for example, even if the Workbench is set to English, some labels may appear in French if the user's language is set to French.

This behavior did not exist in earlier versions such as 4.10.


Example with EnhancedScheduler

This change makes the EnhancedScheduler view unusable if language settings are misconfigured.

For instance, if the Workbench is set to English but the user is configured in French, it becomes impossible to create or edit an event.
Elements in the event creation popup (such as month names or certain buttons) are not correctly interpreted due to a mismatch in the lexicons, completely blocking the action.


⚠️ Important Note on Default Language

In Niagara 4.14, if the user language field is left empty in the UserService, the default language used will unexpectedly be French, for reasons currently unknown.
It is recommended to explicitly set the user language to avoid unexpected behavior in the Workbench and the EnhancedScheduler view.


❗ Specific Case – Boolean Schedule Default Language Behavior

When creating a new Boolean Schedule, it is mandatory to set the same language in both the Workbench and the UserService. This is because the Boolean Schedule comes with a default value (either trueText or falseText), and this default is tied to a lexicon which always depends on the Workbench language, even in the HTML5 view or web interface.

This creates an inconsistency:

  • If the Workbench is in English but the user is set to French, the Boolean Schedule may display labels incorrectly or inconsistently.

  • Changing only the user's language (for example, to French) will change the interface in the web view, but the default Boolean value will remain in English unless the Workbench language is also updated.

To ensure proper behavior:

  • Always align the Workbench and User language settings (e.g., both in French).

  • After changing the language, restart both the Workbench and the station.

📌 This issue only affects the creation of a new Boolean Schedule. Once created, if you customize the trueText or falseText, or if you use a specific lexicon tag for these values, the problem does not occur.

🚨 This issue is likely a limitation or internal behavior in Niagara.