Settings here are used to configure the placeholders.
Settings
The parameters consist of 4 blacklists and 3 flags for constraint usage.
Blacklists contain entries that are excluded from usage:
-
"Excluded personal identifier types" / "forbiddenAttrFormTypes":
Blacklist to exclude personal identifiers by type. Some types, like Picture, would not be replaced by the actual image, thus they are excluded in the example. Other types like Job_Profiles do not support a (meaningful) displayable value and/or are only used for internal purposes.
Bundle: "strSystemCertificatePlaceholderForbiddenAttrTypes" -
"Excluded personal identifier IDs" / "forbiddenAttrIds":
Blacklist to exclude personal identifiers by ID. This list can hold specific personal identifiers, where the type is ok in general, e.g. some Textfields which are only used for internal purposes and/or should not be visible to learners.
Bundle: "strSystemCertificatePlaceholderForbiddenAttrIds" -
"Excluded meta tag types" / "forbiddenMtFormTypes":
Blacklist to exclude met tags by type. Similar to above, the example excludes Picute, File and Organization.
Bundle: "strSystemCertificatePlaceholderForbiddenMtTypes" -
"Excluded meta tag IDs" / "forbiddenMtIds":
Blacklist to exclude meta tags by ID. Oberserve that the first meta tag is Organization in this example. It is ok/valid to exclude the same personal identifier or meta tag by type and ID, though it has no added effect. Other excluded metatags have, similar to above, no meaningful displayable value and/or only internal usage.
Bundle: "strSystemCertificatePlaceholderForbiddenMtIds"
The flags control the usage of additional constraints concerning which personal identifiers/meta tags to show:
-
"Ignore meta tag permission constraint" / "ignoreMtAclConstraint":
If set to false (default value), only those metatags will be shown to the editor of the certificat, for which the editor has ACL permission (any permission level will suffice). If set to true, this constraint is ignored and the editor sees meta tags independent of their ACL permissions.
Bundle: "strSystemCertificatePlaceholderMtAclConstraint" -
"Ignore personal identifier permission constraint" / "ignoreAttrAclConstraint":
Similar to above, but for personal identifier ACL permissions (default value: false).
Bundle: "strSystemCertificatePlaceholderAttrAclConstraint" -
"Ignore personal identifier person profile context constraint" / "ignoreAttrPpcConstraint":
Constraints personal identifiers based on their ppc_id, i.e. person profile context (i.e. client). If set to true, the editor of the certificate can only see personal identifiers, which either have a global context (ppc_id = 0, i.e. not bound to a specific client) or correspond to a context (i.e. client) that the editor is also assigned to (a person can be assigned to multiple clients).
Bundle: "strSystemCertificatePlaceholderAttrPpcConstraint"
Please observe that these flags only limit what the editor can see in the list of available placeholders. These constraints are not applied, when a certificate is generated (e.g. by a learner), as the person that generates the certificate may not have the needed ACL/ppc, but needs the certificate (duh).
Similar for blacklists, the certificate editor can not see those entries in the list of available placeholders. If the placeholder value (e.g. $10184$) would still be used (by just typing it), then the generated certificates will not replace this value.
Please also observe that this generic replacement happens after all the other replacements. Meaning that if there would be a standard or customer specific placeholder, e.g. named $LASTNAME$, then this placeholder will get replaced by the standard or customer specific logic first (and will thus not be replaced by the generic replacer logic).