Context

You can use context to change the behavior of your application in specific circumstances.

Activity context

You can use context in an activity to:

• Change the text displayed or redirect to a different URL when a user submits an activity. For more information, see Apply conditional logic to activities.
• Force a reload of the CSS cache after a user has configured their display preferences. For more information see Style your application.
• Add values to the user session so that you can apply conditions to activities, widgets, and datasets. For more information, see Create conditions based on user session data.
• Impersonate another user so that you can evaluate conditions based on that user's attributes or send them notifications. This is useful for event activities, as these are not performed in the context of a user by default. For more information, see Impersonate users during an event activity

Casetype context

You can use the casetype context to change the default view for a casetype when certain conditions are met.

For more information, see Configure pages and views.

Platform context

The Platform context designer allows you to add values to the current user session and/or make changes to some platform-wide settings when certain conditions are met. This is useful when you want to change the default behavior of your application based on the domain used to access your application (for applications with more than one domain).

To use the Platform context designer:

1. From your Studio, open Platform > Platform context.
2. Add an If then block and add conditions to the If statement to define the circumstances in which you want to change the settings or add values to the user session.
3. Add a Context block to the Then statement.
4. Select the appropriate Context type, based on what you want to achieve:
   • User session data to:
     • Add custom values to the current user session, or
     • Modify the XXID settings.
   • Additional security profile to apply an additional security profile.
5. When you have finished, click the save icon. The context changes are applied whenever the conditions are met.

Note:

The impersonation context option is primarily useful when configuring event activities.

Custom user session values

You can define custom keys and store values in the current user session. You can then access these values using the user.User-session.custom.<key_name> template function in mappings or conditions. This is useful when you want to store a user's selection or preference temporarily, such as recently viewed products or selected filter criteria. You can also use the user session on public pages that do not require a user to log in.

To add a value to a custom key, select the User session context type and enter a name for the key in the Type field. In the Value field, either enter the value as plain text or use an inline template to identify the value you want to store from the current case.

You can access the values stored in custom keys from the user.userSession.custom template function. For example, if you have added a visitor key, you can access the value of that key using user.userSession.custom.visitor. You can add these template functions to mappings and/or conditions in activities, forms, and datasets. You can also add or update values stored in the user session via activities. For more information, see Create conditions based on user session data.

Tip:

Session information disappears after up to 30 minutes of inactivity, requiring a user to log in again.

XXID settings

XXID is the authentication layer and identity provider for the Grexx Platform. You can customize the supported identity providers, login options, and styling, for all users using security profiles and My Grexx.

You can use the Platform context designer to change some of the XXID settings when certain conditions are met. For example, you may want to change the styling or enable different identity providers based on the hostname.

To change the XXID settings, select the User session context type, enter one of the following keys in the Type field and then specify the relevant value.

Type	Description
platform.identityProvider	Override the XXID domain. For example, set the value to xxid-accept.grexx.today to use XXID on the Acceptance environment.
platform.name	Change the name of the platform displayed on the XXID login screen.
platform.brand	Change the styling. To use this option, first create a new XXID brand in My Grexx and then specify it here.
platform.logoutUri	On log out, redirect the user to a predefined URI instead of the XXID logout page.

Additional security profile

You can apply one or more security profiles to all users of your application, or to all users in a particular role. For more information, see Security profiles.

You can use the Platform context designer to apply further security profiles when certain conditions are met. For example, you might want to enforce additional security requirements based on the current hostname or release ring.

To apply an additional security profile, select the Additional security profile context type and then select the relevant security profile(s) from the list.