Revision as of 11:43, 2 August 2024

Introduction

The system allows you to rename most fields that are available. Changes will be applied globally to all record types and also be included in reports/data extractions. You will also notice the field will be renamed in the Menu items.

Future plans

Where practical, we want the system to talk the organisation's own language. Currently, these items can be renamed:

• Organisation and people types, e.g. if you want to rename Clients to Service Users
• The standard field labels used on those types, e.g. if you want to rename Ethnic Group to Ethnicity
• Groups of actions, e.g. if you want to rename cases to enquiries or referrals

These items will be renameable in a future release:

• Projects, e.g. if you want to call them Services
• Clubs and Clinics, e.g. if you want to call them Group Activities
• Meetings at Clubs and Clinics, e.g. if you want to call them Sessions
• Attendess of Meetings at Clubs and Clinics, e.g. if you want to call them Customers

These items define the behaviour of the system, so we have no plans to make them renameable :

• The menu
• Roles
• Actions, as in the Action List
• Success messages, warnings and errors, e.g. "Please enter a date to continue"
• Record a Contact
• Ladder Outcomes

As the of renameable items continues, in order to prevent one word being used to describe multiple things, it will be necessary to have reserved names which cannot be used, both for the web application, and the API.

Web application reserved names are likely to include:

• Groups, which are used for the Group Access security settings
• Users, e.g. people who have a login
• Action List and Case Manager, which are tools used to manage your workload
• Templates, Stages and Workflow, which are used to structure Record a Contact
• Record a Contact
• Ladder Outcomes
• Extension Databases

API reserved names are likely to include:

• Anything listed with an API name in the terminology editor in the web application
• type
• active
• project