Introduction

• Object names are added in a number of places for
  • workflows, jobs, variables, locks, file order sources, job resources
  • calendars, schedules
• The article explains naming rules to be considered when adding object names and labels.
• JS7 does not enforce naming conventions for objects: users are free to choose naming conventions at their will, e.g. for job names to use 
  • camel case style as in: loadDataWarehouseDaily
  • mixed style: DataWarehouse-Load-Daily

Character Set

JS7 basically allows use of Unicode characters for object names.

Object Names

In addition a number of restrictions apply:

• Java Naming Rules
  • The following naming rules for Java object names have to be considered: https://docs.oracle.com/javase/specs/jls/se7/html/jls-3.html#jls-3.8
  • This includes not to use Java reserved keywords for object names.
• Additional Characters are allowed:
  • A dot: not as leading or trailing character and not two dots in sequence.
  • A dash: not as leading or trailing character and not two dashes in sequence.
•  Examples
  • National language characters such as Japanese
    • こんにちは世界
  • Use of dot, dash, underscore
    • Say.Hello
    • Say-Hello
    • say_hello

Labels

More relaxed rules apply to labels that are used to indicate the position of a job in a workflow:

• Labels can start with digits, characters, _
• Labels can include $, _, -, #, :, !
• Labels cannot include whatever is not allowed for Object Names, e.g. no quotes, no spaces, [, ], {, }, /, \, =, +

Length of Object Names

The maximum length of object names is as follows:

• Basically object names can consume up to 255 Unicode characters.
• The following restriction applies:
  • Objects typically are located in folders: the overall length of the folder hierarchy and object name may not exceed 255 characters.
• Branches within a JS7 - Fork / Join Instruction are limited to 10 characters.
  • Such branches can be nested for up to 15 levels.