Tokens | Description | %PCONT_NAME% | Token to include parent container name. Note: This cannot be used at the root level like the parent as there is no container level on top of it. E.g., For LN tank, it cannot be used for the parent freezer, LN Tank. This can be used for the child containers | %PCONT_UID(n)% | Token to include a sequential number for each child container within a parent. This can be used for the child containers (n) - Specify the number of digits. For example, if (2) is used, the numbers generated will be 01, 02, 03, etc. | %PCONT_ALPHA_SEQ% | Token to include a unique alphabetical sequence within the parent container | %SITE_CODE% | Token to include the container's site code which helps to make containers unique across sites. This code is set while creating sitesUsers have to set this Code while creating Site. Note: It is necessary to add site code to ensure the uniqueness of the container. | %SITE_UID(n)% | Token to include a sequential number for each root container within the site. (n) - Specify the number of digits. For example, if (2) is used, the numbers generated will be 01, 02, 03, etc. |
Examples: Freezer level: If the format '%SITE_CODE%_F%SITE_UID(n)%' is set, the container name generated is 'BCS_F1'. 'BCS' is the site code for the site selected as the parent site. Sub container level like rack: If the format '%PCONT_NAME%_R%PCONT_UID(2)%' is set, the container name generated is like 'BCS_F1_R1'. This is the first rack within the freezer.
Similarly, the formats can be set for different levels of the container. From V9.1 onwards, an additional field as 'Display Name' has been introduced, allowing users to mention a user-friendly name to the container as per their requirement. This field do not have uniqueness constraint and thus it is possible that multiple boxes can have same Display name. |