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 administrators, and are unique when generated. Because cell codes can be edited, they are not checked for uniqueness unless the flowchart configuration parameter AllowDuplicateCellCodes is set to "No," 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 Campaign Administrator's Guide. For details about configuration parameters provided by IBM® EMM, see the Marketing Platform Administrator's Guide.
Cell 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") but they can be overridden. 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 you have a Segment process that 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 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
Examples: cell renaming scenarios