Global keyword replacements can be used within various assets in the system to show different information about the asset in the global context, the current site they are viewing or their user account if they are logged in.
For example, to show the name of the page the user is currently viewing as a heading in your Design, you can use the global keyword replacement
|If you find this page is missing information, that is because it is still under active development. Check back regularly to get updates and see progress.|
If an asset is going to be viewed by a user who is logged into your site, you can personalise the content through the use of global keyword replacements. For example, if the page you are creating can only be viewed by a member of your site who has signed in, then you can personalise the page using their attributes or metadata.
For attributes, the format of the global keyword replacement is
ATTRIBUTE is any attribute available on the user account.
Some examples include
%globals_user_attribute_first_name% which prints the first name of the user and
%globals_user_attribute_email% which prints the email address of the User asset.
For metadata, the format of the global keyword replacement is
FIELDNAME is the name of the metadata field you want to show.
For example, if you have applied a metadata schema to a user account that contains the field Hobbies, you can show the value that has been entered into this field by using the global keyword replacement
You can place these keyword replacements within the content of an asset. Matrix will then replace these keyword replacements with the correct information from the user account.
HTTP GET and POST variables
When using these keywords and printing their values directly onto the frontend, it is strongly recommended to use them in conjunction with the
SAML user attributes
The following global keyword replacements are available to provide access to a SAML user’s attributes after being authenticated by a SAML account manager.
Read SAML account manager for more information about SAML authentication in Matrix.
Persona keywords are used to evaluate if a persona is active or not. Persona assets are used to store custom keyword matching logic in which either evaluate the persona as true (active) or false (not active).
Read the Persona documentation for more information about setting personas in Matrix.