Clarity: XOG Write Error 'could not insert a NULL value into BPM_DEF_ASSIGNEES.PRINCIPAL_ID'.

Article Id: 51681
Status: Published
Updated On: 14-02-2018 07:01
Legacy Id: TEC525180
Products:
CA Identity Manager , CA Identity Governance , CA Identity Portal , STARTER PACK-CLARITY PPM
Issue/Introduction:

Description

Error 'could not insert a NULL value into BPM_DEF_ASSIGNEES.PRINCIPAL_ID' when performing a XOG write action on Clarity Content.
Add-ins (just the processes) if your default language is set to something other than English.
This can happen during an upgrade of the PMO Accelerator or implementation of upgraded system content if the Clarity administration user account settings for the Language is set to a Non-English value. The upgrade activities are performing a XOG write action and if the 'admin' user does not have an English Language account setting, the action fails with this type of error message on some specific data being inserted into the database.

Steps to Reproduce:

  1. Upgrade the Clarity application.
  2. Verify that your default language of the Admin user is NOT set to English (ex; use French).
  3. XOG in the add_in Clarity content from Studio.

Expected: Content will XOG in without errors.
Actual: Error 'could not insert a NULL value into BPM_DEF_ASSIGNEES.PRINCIPAL_ID'.

Solution

WORKAROUND:
Set the XOG user's default language to English If the XOG user is 'admin', have the 'admin' user login and navigate to Account Settings and change the Language to English.

STATUS/RESOLUTION:
Use the identified steps to change the language of the administrator user before performing the upgrade to avoid this error.

Keywords: CLARITYKB, CLRT-21964, wnf, clarity13open

Environment:

Release: ESPCLA99000-13.2-Clarity-Extended Support Plus
Component: