Property & Casualty Application Naming and Numbering Conventions Reference

Once you've got your own spin, you're free to extend what we've created, and create your own components and processes.

To make your extensions and additions work best with this Application, follow the naming and numbering conventions described below.

Abbreviations

These abbreviations are used in some naming conventions to group items within a product line. Note that the Type field will be used on the product object for product lines.

Note

We use the Type field on the Product object for product lines.

Attribute Categories

Attribute categories are grouped in sequence spaces to prevent clashing. If you create your own, you'll be more successful if you follow the patterns we've established.

Note

Many Insurance UIs display attribute categories and use the sequencing for UI ordering.

Products

We've created product codes using camel case, no spaces, prefaced by the product line abbreviation listed earlier on this page.

If you create other products, set the following information for each product:

• Line of Business = Property & Casualty (all products in this org)

• Product Family

• Type

• Sub Type

OmniScripts and Integration Procedures

Form all OmniScript and Integration Procedure names in camel case (camelCase).

Follow these guidelines when you set up OmniScripts and Integration Procedures:

• Type field

  • Set this field to the product line of this OmniScript or Integration Procedure

  • Prefix the value of this field with ins for OmniScripts and Integration Procedures common to all product lines

  • Create common groupings for OmniScripts and Integration Procedures used in similar areas

• Sub Type field

  A short and descriptive word or phrase, which will be used as part of the naming convention for Omnistudio Data Mappers

Data Mappers

Consistent naming conventions help you determine what product line a Data Mapper is used for and where it is used.

For Data Mappers used in OmniScripts and Integration Procedures, use the following conventions, without spaces:

<Product Line Abbreviation><Read/Trans/Post><Descriptor><OS/IP Subtype><OS/IP>

For example: wi_ReadProducer_QuoteOS

Where:

• Product Line Abbreviation

  • Use the product line abbreviation from the top of this page.

  • For Data Mappers used across product lines, prefix the name with the full Type of the OmniScript or Integration Procedure.

• Read/Trans/Post

  • Read: Use for Data Mappers of type Extract

  • Trans: Use for Data Mappers of type Transform

  • Post: Use for Data Mappers of type Load

• Descriptor

  A word or short phrase that gives a user a high-level understanding of how this Data Mapper is used.

• OS/IP Subtype

  The Sub Type field of the OmniScript or Integration Procedure that uses this Data Mapper. In combination with the Product Line Abbreviation, this lets the user find where this Data Mapper is used.

• OS/IP

  Either OS or IP, to tell the user whether this Data Mapper is used in an OmniScript or an Integration Procedure.

For Data Mappers used in Cards, use the following naming convention:

<Product Line Abbreviation><Read/Trans/Post><Descriptor>_Card

Add the Card name in the Description field for the Data Mapper.

Where:

• Product Line Abbreviation

  • Use the product line abbreviation from the top of this page.

  • For Data Mappers used across product lines, prefix the name with the full Type of the OmniScript or Integration Procedure.

• Read/Trans/Post

  • Read: Use for Data Mappers of type Extract

  • Trans: Use for Data Mappers of type Transform

  • Post: Use for Data Mappers of type Load

• Descriptor

  A word or short phrase that gives a user a high-level understanding of how this Data Mapper is used.

Calculation Procedures and Calculation Matrices

Create names of Calculation Procedure and Calculation Matrices in camel case. Begin each name with the Product Line Abbreviation from the list at the beginning of this page.