CA Identity Suite: Bulk Load User Invitations Fail with Error "Missing Mandatory Attribute" After International Proofing Feature Implementation

Products

• CA Identity Suite

Issue/Introduction

After implementing a new attribute to feature to support international users for proofing in one of customized Tasks, the bulk load user invitations functionality began to fail.

The failure occurred because the underlying TEWS6 web service expected an additional, mandatory parameter that was missing from the existing WSDL definition used by the bulk load process.

The specific error encountered during the task submission was:

_ImsException caught

SOAP faultCode: Client

SOAP faultString: Error performing operation.

Exception

Name:

Code: 500

Description: Exception encountered during task submission: This method requires the presence of an attribute which was not provided. The attribute is named |NewFeatureConfigurationField|.

ProcessStep::DataValidate TabName: ERRORLEVEL::Error

Environment

Product: CA Identity Suite
Component: IDMGR 14.5.1 CHF01

Cause

The definitive root cause was a configuration mismatch in the production environment.
The required attribute, |NewFeatureConfigurationField|, was missing from the Roles and Tasks screen definition within the application. This missing checkbox prevented the task submission from completing successfully during the bulk load process.

 

Resolution

The issue was resolved by correcting the configuration mismatch.

1. Update Screen Configuration: Update the application's Roles and Tasks screen definition (specifically the AssignActivityAccessUserCustomTab or similar) to include the mandatory attribute |NewFeatureConfigurationField|.
2. Validation: After adding the missing checkbox, the bulk load batch file successfully executed, and the user invitations functionality was restored.

Additional Information

This is a customization. During the troubleshooting process, the following actions were also necessary due to changes in the IM screen definitions:
- It was determined that the IdM Web Service was configured without WS-I selected.
- A new Customized FILE.jar file had to be regenerated and successfully compiled using Axis (as standard methods like wsimport and Axis2 failed) because of the task/screen definition change introduced by the new international proofing use case.