There are global configurations that can be specified for citizen messages, such as enabling certain types and configuring their display order. The different types of messages also include their own configuration points. Specific information regarding how to customize the various message types is provided in later sections of this document. Please refer to the Cúram Universal Access Configuration Guide for more information on how to change the global configurations and on delivering Citizen Messages using web services.
The textual content of a given message type can also be configured. Each message type has a related properties file that includes the localizable text entries for the various messages displayed for that given type. These properties also include placeholders that are substituted for real values related to the citizen at runtime.
The wording of this text can be customized, by inserting a different version of the properties file into the resource store. Please see the table below which defines which properties file should be changed for each type of message:
| Message type | Property file name |
|---|---|
| Payments | CitizenMessageMyPayments.properties |
| Application Acknowledgment | CitizenMessageApplicationAcknowledgement.properties |
| Verifications | CitizenMessageVerificationMessages.properties |
| Meetings | CitizenMessageMeetingMessages.properties |
| Referral | CitizenMessagesReferral.properties |
| Service Delivery | CitizenMessagesServiceDelivery.properties |
It is also possible to remove placeholders (which are populated with live data at runtime) from the properties. However, there is currently no means to add further placeholders to existing messages. A custom type of message must be implemented in this situation.