Validation Framework: Bug in 7.2 Version

[Former Member]

Hi,

we are currently upgrading from SAP NW IDM 7.1 to 7.2 and encountered a problem with validation extension provided by SAP. Maybe this is a bug an should be filed as OSS message.

The Validation API delivers a list of IdmValueChanges to the custom validation class (I've provided an example implementation in the attachment).

I've now created an UI task containing

MSKEYVALUE

P_COMMENT (initially empty)

P_INITIAL_PASSWORD (already set, encrypted)

I've hooked up the debugger to get this:

You can see the instances of those IdmValueChanges. Each of those are holding an mOperation Attribute which indicates the operation performed on this attribute.

Also, there are constants defined in the class IdmValueChange:

OPERATION_REPLACE = 0

OPERATION_ADD = 1

OPERATION_DELETE = 2

OPERATION_PROPERTY_CHANGE = 3

OPERATION_DISAPPROVE = 4

So all of those attributes are considered to be an OPERATION_PROPERTY_CHANGE, although those should be like this:

P_COMMENT: OPERATION_ADD

P_INITIAL_PASSWORD: OPERATION_REPLACE

This is how it was in 7.1 version.

I've also added some debug code to see the operations:

Do you encounter the same problems?

best regards

Matthias

ValidationTest.java.txt.zip

[Former Member · Accepted solution]

I am also facing similar problem

IdMValueChange[] changes = validate.getChangeList();

            for (int i = 0; i < changes.length; i++) {

                IdMValueChange aIdmValue = changes[i];

                String aAttr = aIdmValue.getAttributeName();

                if (aAttr.equalsIgnoreCase("MXREF_MX_ROLE")) {

                    loc.infoT("Operation type :"+ aIdmValue.getOperation());

                }

          }

Here Operation Type always comes as 3 irrespective of if i add/remove role from UI.

Is it a bug ? Our environment is IDM 7.2 SP7

[Former Member · Accepted solution]

Thanks for your reply - we've currently opened an OSS message with SAP, they are currently investigating on this issue. I assume it's a bug!

best regards

Matthias

[Former Member · Accepted solution]

Hi Matthias,

Did you get any update from SAP confirming it as bug ?

Thanks,

Karthik