Treasury

Building features for Treasury customers is similar to building a feature for Retail with some small differences.

User Roles

The major difference between retail and treasury users is how entitlements are enabled. Treasury users are assigned a User Role, and entitlements are enabled/disabled using this, rather than assigned directly to the user. This allows for the same set of entitlements to be applied to multiple users without having to set up the users individually. Because of this, entitlements assigned to the User Role will supersede any entitlement assigned directly to the user.

Enabling Treasury in Shared Dev Environment

The Shared Dev environment does not come with Treasury enabled by default. The following SQL queries can be executed in the database to enable Treasury.

Enabling the main system property is the first step

UPDATE Q2_SystemPropertyData
SET PropertyValue = 'True'
WHERE PropertyID IN
(SELECT PropertyID FROM Q2_SystemPropertyDataElements WHERE PropertyName = 'EnableTreasury')

This will set the login url in the system. Make sure to replace the [environment] with the name of your environment.

UPDATE Q2_SystemPropertyData
SET PropertyValue = 'https://stack.q2developer.com/sdk/[environment]/ardent/uux.aspx'
WHERE PropertyID IN
(SELECT PropertyID FROM Q2_SystemPropertyDataElements WHERE PropertyName = 'OnlineUnifiedUxUrl')

This will disable a navigation node that is no longer needed.

UPDATE q2_navigationnode
SET devicebitflag = 0, enabled = 0
WHERE shortname = 'settings-policies'

This will enable the Treasury pages for end users

UPDATE q2_navigationnode
SET enabled = 1, devicebitflag = 7
WHERE shortname IN ('CompanyPolicy','UserRoles','recipients')

Lastly, an HQ bounce is required for the changes to be applied to the product:

$ q2 bounce_stack