Messaging deployment

In addition to the standard messaging processes, you can set up your own messaging processes in Operations and Regulations.

The basic unit of messaging setup is a mapping, where each mapping defines a specific type of message that Operations and Regulations can send or receive. Mappings are defined in the Messaging configuration in the Configuration Editor. Each mapping consists of these parts:

1. A business object moniker, indicating the type of Operations and Regulations record the messages will act on. For example, Hansen.CRM.ServiceRequest is the moniker for service requests.
2. A noun, which will represents the Operations and Regulations business object in inbound or outbound messages.
   Note: You can use the same noun for more than one moniker. For example, you might want to use the noun PublicSectorInspection for inspections in all Operations and Regulations CDR modules.
3. A verb, indicating the action to take on the specified object, such as processing or syncing a service request.
4. A mapping file, used to map data elements in inbound or outbound messages to the correct business object properties, and hence to the correct tables and columns in the database.