What's New in 2022.3

The following enhancements are included in the VERA 2022.3 release:

Please review https://tx3.atlassian.net/l/cp/XREVy9XA prior to upgrading Vera.

Introduced Default Domain

Vera now includes a default domain. Projects will automatically be associated with this domain when a record is routed for approval from a project that is not associated with a domain.


The System Administrator can move a project to another domain by removing the project from the Default domain and then adding the project to another domain.

Improved permissions with New Roles

User Roles have been separated by System Roles and Domain Roles. System Roles are assigned to a User Profile by the System Administrator:

  • System Administrator manages users, system role membership, domains, assigns projects to domain, domain role membership, policies, approval roles, and settings

  • System Service Account provides the permissions for the Vera Jira Server App and Vera Jira Cloud App to integrate with Vera

Domain Roles are assigned to users in a domain by the System Administrator or Domain Administrator:

  • Domain Administrator manages user role membership in their domain and can view records their domain

  • Domain Viewer can view records in their domain

  • Approval Roles can complete approval tasks for their role in their domain (example: Technical, Business, Quality, ITQA)

Approval roles are defined in the Approval Policy.

See https://tx3.atlassian.net/l/cp/e6AGurrR for more information on Vera roles and permissions.

Manage Roles by Domain

Vera 2022.3 introduces managing approval roles by domain. Organizations can now fine tune approval roles based on domain instead of at the Vera site level providing granular approval roles instead of global approval roles. User Role membership can be delegated to Domain Administrators. View only permission can be granted using the Domain Viewer role.

Domain Management updates

The Domain Management > Role Management page now displays the Domain-level Approval roles, and the users assigned to each role. Domains now have an optional field to define a Domain Owner. The Domain Owner is a Domain attribute and not a domain or system role. It is provided as a way to designate which user should be contacted in case there are questions about the domain or user membership in the domain.

Domain User Role management

Any System Administrator, or a Domain Administrator assigned to the domain, can manage user role membership for a particular domain. All domains also include the default roles of Domain Administrator and Domain Viewer. These are not approval roles. but can still be assigned to users in the same manner. Domain Viewers are allowed to see domain records, but are not allowed to approve as any role for that domain.

Figure: Domain Role Membership on Default Domain

A Domain Administrator cannot remove their Domain Administrator role from their own user profile.

See https://tx3.atlassian.net/l/cp/w0FeHp1h and https://tx3.atlassian.net/l/cp/rVAr1D8j for more information on adding and remove users from domains and roles.

Define a Domain Owner

The System Administrator can set any Vera user as a Domain Owner when they create or edit a domain.

Figure: Create New Domain with optional Domain Owner field

User Management Updates

Role Membership was removed from the user profile now that approval roles are managed by domain and is replaced by the System Roles field and new Domains & Roles page on User profile.

System Role Management

System Administrators can modify System Roles for users in their User Profiles.

Figure: System Roles field on the User Profile Screen

Domain and Roles Management

System Administrators can manage domain and domain role membership for a user in their Edit Profile > Domain & Roles page.

Figure: Domain and Role Membership from the Edit User Profile Screen

Import User changes

System Administrators can now import users and their associated System Roles and Domain membership.

Figure: User Import CSV file with System Roles and Domain Membership

When the import file includes existing users, the System Role and Domain Role changes are appended to the user's current roles and do not overwrite any role assignments.

See https://tx3.atlassian.net/l/cp/Jz8B7HV1 for more detail

My Profile updates

Users can see their System Roles and their domain role membership in the Domains and Roles section.

Figure: My Profile page with System Roles and domain membership.

Removed Role Management Administration Page

The role management page was removed now that Approval Roles are managed by domain.

Upload Policy files for new installations

New Vera installations do not have policy files by default. The system administrator can now upload initial policy files via the Vera Administration > Policy Management page instead of loading the policy files into the Policies directory on the server.

Figure: Import New Policy File dialog.

Logging Improvements

Logging has been enhanced for nearly all modules of the Vera API Server. Now each module can produce its own log files making it much easier to diagnose issues as they come up. A new logging-settings.json file is also now available in order for clients to fine-tune their log settings.

The logging-settings.json file should be placed in the Configs directory for the Vera API Server before migrating to 2022.3. This is not required for the migration, but will make troubleshooting any issues with the migration easier. Attached below is an example settings file. Client’s who have concerns or need a custom settings file are encouraged to contact support.

Defect fixes

Various defect fixes to the Web Portal and API Server.