Lock Icon Appears When Adding Staff / Resource

Products

• Clarity PPM SaaS

Issue/Introduction

Why does the 'Locked' icon appear when adding resources to the project staff?

1. Open a Project > Staff > Click 'Add Staff'
2. Select resource(s)

Actual : Modern project is locked. 

-Click Properties page, the lock icon is removed.
-Attributes can be updated.
-security.locks page does not show locks

Expected: The lock icon should not display long.

Environment

Release : 16.1.0

Cause

The following error appears in the APP log:

ERROR 2023-02-21 21:01:41,296 [clarity.cppm9125-dev::SchedulerWorkerThread-UpdateResourceAllocationService] union.persistence (clarity.environment:user:session:none) Undefined statement set: projmgr.resourceGeneralProperties_set

ERROR 2023-02-21 21:01:40,419 [clarity.cppm9125-dev::SchedulerWorkerThread-UpdateResourceAllocationService] broker.service (clarity.environment:user:session:none) 
java.lang.RuntimeException: com.niku.union.persistence.PersistenceException: statementSet not found projmgr.resourceGeneralProperties_set
    at com.ca.ppm.mercury.service.projmgr.UpdateResourceAllocationService.run(UpdateResourceAllocationService.java:96)
    at com.ca.ppm.mercury.rest.PPMServiceDelegate.run(PPMServiceDelegate.java:44)
    at com.ca.ppm.mercury.rest.PPMThreadPool$SchedulerWorkerThread.run(PPMThreadPool.java:675)
Caused by: com.niku.union.persistence.PersistenceException: statementSet not found projmgr.resourceGeneralProperties_set
    at com.niku.union.persistence.PersistenceController.<init>(PersistenceController.java:382)
    at com.niku.union.persistence.PersistenceController.processRequest(PersistenceController.java:342)
    at com.niku.union.persistence.PersistenceConversation.process(PersistenceConversation.java:505)
    at com.ca.ppm.mercury.service.projmgr.UpdateResourceAllocationService.getResource(UpdateResourceAllocationService.java:106)
    at com.ca.ppm.mercury.service.projmgr.UpdateResourceAllocationService.run(UpdateResourceAllocationService.java:41)
    ... 2 more

Other environments show:

ERROR 2023-02-21 18:21:22,065 [http-nio-80-exec-4] xql2.rule (clarity:user:session:PPM_REST_API) TeamRule.markResourceTotalAlloc() microservice not accepted.
ERROR 2023-02-21 18:21:23,190 [http-nio-80-exec-4] client.errorhandler (clarity:user:session:PPM_REST_API) Service invocation for service UUID 0B438E19-66F1-4AB1-BC61-04EAD191853D failed with status code = 500
ERROR 2023-02-21 18:21:23,190 [http-nio-80-exec-4] client.errorhandler (clarity:admin:8593040__B8A5A80B-D76D-4DB8-8577-492E844407B5:PPM_REST_API) Service invocation parameters={teamId=5093001, uuid=0B438E19-66F1-4AB1-BC61-04EAD191853D}
ERROR 2023-02-21 18:21:23,190 [http-nio-80-exec-4] xql2.rule (clarity:admin:8593040__B8A5A80B-D76D-4DB8-8577-492E844407B5:PPM_REST_API) AssignmentRule.markTeamAggrEtcAct() exception:
java.lang.RuntimeException: org.apache.http.conn.ConnectTimeoutException: Connect to localhost:9000 [localhost/127.0.0.1] failed: connect timed out
    at com.ca.ppm.rest.ppmbroker.api.ServiceInvokerImpl.throwException(ServiceInvokerImpl.java:457)
    at com.ca.ppm.rest.ppmbroker.api.ServiceInvokerImpl.execute(ServiceInvokerImpl.java:198)
...
ERROR 2023-02-21 18:21:23,190 [http-nio-80-exec-4] xql2.rule (clarity:user:session:PPM_REST_API) AssignmentRule.markTeamAggrEtcAct() microservice not accepted.

Resolution

This is resolved in 16.1.2. This was originally reported as DE68591.