Need Support? Let’s guide you to the right answer or agent.

BCDE

ADD A NEW IDEA

i18n - Internationalisation

Showing 8 of 168

Support multiple language specific strings for METADATA FIELD names

As a schema designer I want to be able to use the same metadata field across multiple languages to allow for a single schema to deliver for global users. This needs to include: System metadata fields Global metadata fields Local metadata fields
over 1 year ago in Core CDE / i18n - Internationalisation 0 Future consideration

Support CSV files globally - i.e. CSV files with region specific separators

As a user I want to be able to import information from a CSV from any region across the globe - where separators may not be commas. For example, Sweden does not use "," as a delimiter in a CSV file - it uses ";". Wikipedia notes the following abou...
over 1 year ago in Core CDE / i18n - Internationalisation 1 Planned

Support multiple language specific strings for ENUMERATED METADATA FIELD VALUES

As a schema designer I want to be able to define an enumerated metadata field (single select drop down/multi-select drop down/taxonomy) that supports multiple languages - i.e. one value per language to reduce administrative overheads around schema...
over 1 year ago in Core CDE / i18n - Internationalisation 0 Future consideration

Support multiple language specific strings for ROLES

As a role admin I want to be able to use one set of roles across multiple languages. Each role will need to be able to store a translation for the role name in each language. The correct role name will need to display according to the user's langu...
over 2 years ago in Core CDE / i18n - Internationalisation 2 Future consideration

Ability to rename system fields in schema config

As a customer I want to be able to rename all system metadata fields (globally) to my chosen term. E.g. As a customer I want to be able to rename the "version number" system field to "revision number". Renaming a system field locally in a schema i...
about 3 years ago in Core CDE / i18n - Internationalisation 0 Future consideration

Support multiple language specific strings for FIELD SETS (REASONS FOR ISSUE)

As a schema admin I want to be able to define multiple language strings for field sets/reasons for issue to support defining a single schema that works globally. As a schema admin I want to be able to define a logical order for the field sets - be...
over 1 year ago in Core CDE / i18n - Internationalisation 0 Future consideration

Multilingual Support for UX

As a user I want to be able to use the BCDE interface in my native language. Elements related to multiple language support that need consideration are: User interface elements Menus Buttons Guidance text The user will be provided with a mechanism ...
over 3 years ago in Core CDE / i18n - Internationalisation 0 Planned

Support multiple language specific strings for ISSUE CATEGORIES

As a schema designer I want to be able to use Issue Categories across multiple languages. Each issue category should be able to store a translation for each supported language. The language string shown when displaying issue categories - i.e. in m...
over 2 years ago in Core CDE / i18n - Internationalisation 0 Future consideration