These settings configure the placeholders.
Settings
The parameters consist of four blacklists and three flags governing constraint usage.
Blacklists contain entries excluded from use:
-
"Excluded personal identifier types" / "forbiddenAttrFormTypes":
Blacklist to exclude personal identifiers by type. Some types, such as Picture, would not be replaced by the actual image and are therefore excluded in the example. Other types, such as Job_Profiles, do not support a meaningful displayable value and/or are used only for internal purposes.
Bundle: "strSystemCertificatePlaceholderForbiddenAttrTypes" -
"Excluded personal identifier IDs" / "forbiddenAttrIds":
Blacklist to exclude personal identifiers by ID. This list can contain specific personal identifiers for which the type is generally permitted, such as text fields used only for internal purposes and/or not intended to be visible to learners.
Bundle: "strSystemCertificatePlaceholderForbiddenAttrIds" -
"Excluded meta tag types" / "forbiddenMtFormTypes":
Blacklist to exclude meta tag types. Similar to the above, the example excludes Picture, File, and Organization.
Bundle: "strSystemCertificatePlaceholderForbiddenMtTypes" -
"Excluded meta tag IDs" / "forbiddenMtIds":
Blacklist to exclude meta tags by ID. Note that the first meta tag in this example is Organization. Excluding the same personal identifier or meta tag by type and ID is valid, although it has no additional effect. As above, other excluded meta tags have no meaningful displayable value and/or are used only for internal purposes.
Bundle: "strSystemCertificatePlaceholderForbiddenMtIds"
The flags control the use of additional constraints governing which personal identifiers and meta tags are shown:
-
"Ignore meta tag permission constraint" / "ignoreMtAclConstraint":
If set to false (the default), only meta tags for which the certificate editor has ACL permission (any permission level is sufficient) are shown. If set to true, this constraint is ignored, and meta tags are shown independently of the editor's ACL permissions.
Bundle: "strSystemCertificatePlaceholderMtAclConstraint" -
"Ignore personal identifier permission constraint" / "ignoreAttrAclConstraint":
As above, but for personal identifier ACL permissions (default value: false).
Bundle: "strSystemCertificatePlaceholderAttrAclConstraint" -
"Ignore personal identifier person profile context constraint" / "ignoreAttrPpcConstraint":
Personal identifiers are constrained based on their ppc_id, that is, their person profile context (client). If set to true, the certificate editor can see only personal identifiers that either have a global context (ppc_id = 0, that is, are not bound to a specific client) or correspond to a context (client) to which the editor is also assigned. A person can be assigned to multiple clients.
Bundle: "strSystemCertificatePlaceholderAttrPpcConstraint"
These flags only limit what the certificate editor can see in the list of available placeholders. The constraints are not applied when a certificate is generated, for example by a learner, because the person generating the certificate may not have the required ACL or ppc but still needs the certificate.
Similarly, the certificate editor cannot see blacklisted entries in the list of available placeholders. If a placeholder value (for example, $10184$) is still used by entering it manually, the generated certificates do not replace this value.
This generic replacement occurs after all other replacements. If a standard or customer-specific placeholder, such as $LASTNAME$, exists, it is replaced first by the standard or customer-specific logic and is therefore not replaced by the generic replacer logic.