Role and user

Adds current UBC Analytics role and user values.

Purpose

Writes the selected role and/or user into columns of every row. Used for responsible persons, approval routing and form fields. Works in UBC Data Bridge as part of UBC Analytics.

Inputs and outputs

One in input and out output; selected columns are added or overwritten in every row. Values are read again during active execution.

Parameters

Parameter	Settings and values	Options and limits
`connection_id`	The saved connection through which the block accesses the system.	Default: `empty` Up to 64 characters
`environment`	The UBC Analytics environment; select it before the object and fields.	Default: `empty` Up to 80 characters
`role_field`	The role-column name; an empty value disables adding the role.	Default: `Роль` Up to 256 characters
`role_code`	The selected role’s code.	Default: `empty` Up to 128 characters
`role_label`	The saved role label for the interface.	Default: `empty` Up to 200 characters
`role_value`	Write the role’s name or code.	Options: `name`, `code` Default: `name`
`user_field`	The user-column name; an empty value disables adding the user.	Default: `Користувач` Up to 256 characters
`user_id`	The selected user’s identifier.	Default: `not set`
`user_label`	The saved user label for the interface.	Default: `empty` Up to 400 characters
`user_value`	Write the user’s full_name, email or id.	Options: `full_name`, `email`, `id` Default: `full_name`

Step-by-step configuration

Add the block in a UBC Analytics environment and select its connection and environment.
Set the required role and its value format.
Set the user and choose full name, email address or ID.
Name the target columns; disable an unneeded part by leaving its field name empty.
Check the values and map them to the corresponding fields of the target form.

Rules and diagnostics

A deleted or disabled role causes CMS_ROLE_MISSING; a missing/inactive user causes CMS_USER_MISSING. Select a current record again.
The user ID is passed as text compatible with the relevant form fields.
An existing column with the selected name is overwritten in every row.
On an inactive route, the block passes the structure without contacting UBC Analytics.
In a standalone installation, this block does not provide access to UBC Analytics roles.
At least one column must be added. If both role and user are added, their target names must differ.

Configuration example

For requests, set role_field=ApprovalRole, role_value=code and the approver role; set user_field=OwnerID, user_value=id and the responsible user. Then map these columns to the form fields.