Error 'API-1007'' - Unable to navigate the custom object instance in MUX

Products

• Clarity PPM On Premise

Issue/Introduction

Steps to Reproduce:

1: Login to Classic UI

2: Create a master custom object  and make it API enabled

3: Enable Auto Numbering on ID and Name attributes of the created custom object

4: Grant the respective permission to the user with respect to the custom object i.e. create, copy, delete, edit, navigate, view and XOG

5: Try to create an instance of custom object from classic and MUX and you will be able to.

6: Open the Clarity DB and look for Sequence odf_ca_CUSTOM_OBJECT_CODE_s1 and set it to value 11899686656. (CUSTOM_OBJECT_CODE need to be replaced by object code given in step 2 while creating custom object)

Oracle query: alter sequence odf_ca_CUSTOM_OBJECT_CODE_s1 restart start with 11899686656;

7: Validate that the sequence is correctly set by checking the next value of sequence with below query

SELECT odf_ca_CUSTOM_OBJECT_CODE_s1.nextval FROM dual;

8: Clear the caches by navigating to the URL https://CLARITY_SERVER/niku/nu#action:security.caches and click on Flush All

9: On Classic UI navigate to Home > Custom Objects > Custom Object created in step 2 Create New instance > Save > Save . The Name and Id will be blanked out and clicking on save will return error.  

Note: Though the error is thrown the instance is created

10: Login to MUX and try to open the instance created above in MUX > Custom Objects > Custom Object created in step 2 and it will throw below error.

“API-1007 : You are not authorized to process request. Contact your system administrator for necessary security rights.”

Expected Results: The navigation to the object instance should be possible from MUX and Classic as the DB permit the sequence with that large number.

Actual Results:

• Unable to save the instance in Classic with an updated attribute's value.
• Unable to edit the properties of the created instance in Classic, as it navigates wrongly.
• Unable to navigate the instance in MUX and it result in API-1007 Error

Environment

Clarity: 16.2.1, 16.2.2, 16.2.3

DB: Oracle

Cause

DE166407

Note: The fix scope spans across product and fixing at individual level can have repercussions, so the fix will be part of future major release.

Resolution

Workaround : Reset the sequence to lower number it is only viable if there is no data in custom object table.