System attributes [editor]

The Blueriq Runtime provides access to specific system properties via the system entity. This entity is created when the Runtime starts and contains attributes which may be used in expressions in your application. These attributes are owned by the runtime and should not be modified. The following attributes are available.

USER

system.user (Instance)

This attribute contains a relation to the active user instance (@User@). The active user contains the following attributes.

system.user.id (String)
system.user.Roles (List)
system.user.teams (List)
system.user.userName (String)
system.user.tenant (String)

CHANNEL

system.channel (String)

This attribute contains the current channel. This value can be unknown if no channel has been selected.

CURRENTPAGE

system.currentpage (String)

This attribute contains the name of the current page.

LANGUAGE

system.language (String)

This attribute contains the current language.

PAGEVALID

system.pagevalid (Boolean)

The value of this boolean is:

unknown if a page has never been validated
false if the page has been validated and it contains errors (and/or warnings that are shown for the first time)
true if the page has been validated and all validations are passed succesfully

The attribute value is recalculated with every refresh.

EVENT

system.event (List)

This attribute contains the current events, which can be set as parameters on an Event. This value is unknown if no event is triggered.

Current events could be defined on buttons or as special events on specific container types.

Furthermore, the type of button also sets these values:

Button Event Type	system.event value
Validate and Continue	no value
Continue	`_draft`
Cancel	`_void`

Also:

Button Refreshes	system.event value
True	`_refresh`
False	no value

ROLES

system.roles (List)

This attribute contains a list of the roles of the current user.

TODAY

system.today (date)

This attribute contains the current date (yyyy-MM-dd) from the runtime environment.

If you want to update System.User from the sessionScope you should use the ISessionScope.setUser(IUserData user) method. This will update the System.User instance and the underlying ActiveUser object which is stored in the SessionScope which is used in the AQ_StartProject and the AQ_Dashboard_ProjectWidget for sending the ActiveUser to the new session. This however does not mean that the two sessions still use the same underlying object it copies the values to the new session.

Space shortcuts

Page tree