When using a process to lock attributes, you are able to select the object's Studio attributes you wish to lock in a browse window.
For the Change Request object, a number of attributes appear that are for internal use. Selecting these and then attempting to run this step of the process will result in a BPM error.
BPM-0522: Internal Process Engine Error. Contact your site administrator (Error executing action) java.lang.NullPointerException
Steps to Reproduce:
Expected Result: Only valid attributes for locking should be displayed.
Actual Result: Internal attributes such as these are included in the list: p_risk_issue_name, _parent, parent_risk_issue_id, pk_id, pk_unique_name, pk_name, table_name.
The reason this is happening is because user gets special attributes [parent attribute if object has parent] along with list of odf attributes associated with object and if user by any chance selects any one of the special attribute[s] for lock system action then at run time process throws NPE because special attributes are not real odf attributes and due to that, process can not get real odf attribute object to perform lock action.
If you have a process attempting to lock attributes like this, select and remove them from the list of selected attributes in the process definition.
Resolved in Clarity 12.1.3
solution to this problem is to stop special attribute[s] from showing up along with other odf attributes when user opens browse window to select them for lock action.
Keywords: CLARITYKB, CLRT-61385, clarity12resolved, clarity1213resolved.