There is a variety of step naming conventions. Use these step structures:

• The structure that is available when you add a new step (for example, Assign Source Values).
• Camel case (for example, assignSourceValues).
• Lowercase with spaces or underscores (for example, assign source values, assign_source_values).

To use numbers to distinguish step names, include the number of the step at the end, with a space (for example, P_PUR assign_source_values 1). If you copy the numbered step, the next sequential number will be added automatically.

If you use Plan includes, the prefix of each step is derived from the Plan/include name. P is the abbreviation for party.

The naming structure is:

• P_MAIN + step description (use one of the three previously mentioned conventions)
  • P_CLN
    • P_PUR
    • P_NAME

Similarly, A is the abbreviation for address. For address cleansing, the prefix is:

• A_MAIN
  • A_CLN
    • A_PUR
    • A_ADR

The objective of this convention is to enable you to find the proper step in the hierarchy as fast as possible.

Examples:

• P_PUR_assignDecodeValues
• P_PUR_createPurValues
• P_NAME_uk name parsing
• P_NAME_UK Name Parsing
• A_ADR UK Address Identifier 1
• A_ADR_UK_addressIdentifier 1

If you are building a simple Plan or project, you do not need to use the full structure described here. However, it is a best practice to use as many naming conventions as possible. This ensures that even temporary or rarely used Plans, steps, and files are properly named and located according to iWay DQC conventions.