Cell names and codes

Cell names and codes are important because they establish the links between processes that output cells or use cells as input.

Cell codes

Cell codes have a standard format determined by your system administrator, and are unique when generated. Cell codes can be edited. Therefore, they are not checked for uniqueness unless the flowchart configuration property AllowDuplicateCellCodes is False, in which case cell codes are enforced to be unique only within the current flowchart. There is no checking for uniqueness in the target cell spreadsheet (TCS). For details about cell codes and cell code generators, see the Unica Campaign Administrator's Guide.

Cell names

Note: Cell names have specific character restrictions. For details, see Special characters in Unica Campaign object names.

By default, cell names are based on the process from which they are generated. For example, if a cell is generated by a process named "Select1", then the default cell name is "Select1". You can change the cell name. If you change a process name, the names of cells generated by that process are automatically changed as well, both in that process and in any connected downstream processes within the same flowchart. If you change a cell name, you might also affect the links between that cell and any downstream processes using that cell as input.

For example, if a Segment process generates two output cells named Segment1 and Segment2, and these cells are used as input into two Mail List processes (Mail List 1 and Mail List 2), if you change the names of the Segment cells after you have already connected the Mail List processes, you need to understand how Unica Campaign handles the new cell names.

The following diagram illustrates a basic example of a Segment process that outputs two cells, each cell then becoming the input for downstream Mail List processes.

Example of a Segment process that outputs two cells