Overview of compliant server development artifact changes

In addition to your custom code, you can customize the default application by adding message files, code tables, events, and so on.

The following table summarizes the range of compliant changes you can make to development artifacts.

Table 1. Cúram Development Artifact Compliant Changes
Type of Change	Compliant Changes
Change or remove an existing message file or add additional locale (language) support to an existing message.	Message file (externalized server informational, warning, and error messages - .xml files in the message directory). For more information, see Customizing a Message File.
Change an existing code table display name or description, add a code table item into an existing code table, or enable or disable an existing code table item.	Code Table file (code value pairs - .ctx files in the codetable directory). For more information, see Customizing a code table file.
Add an event registration (to augment initial Cúram functionality, or disable an existing event handler.	Event Definition file (.evx files in the events directory) and Event Handler Registration file (handler_config.xml in the events directory). For more information, see How to merge event files.
Override an existing user preference.	User Preference file (DefaultPreferences.xml file in the userpreferences directory).
Customizing workflow process definition files.	For more information, see Customizing Workflow Process Definition Files.
Override an existing application property.	You cannot override an application property directly. For information about how to customize properties, see How to merge an application prx file. Application Property File (Application.prx file in the properties directory).
Add initial demo or test data (rows) to an existing database table.	DMX File (script for populating the database with data - .dmx files in the relevant data subdirectory).