Skip to Content
author's profile photo Former Member
Former Member

Validation Framework: Bug in 7.2 Version

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 06, 2014 at 09:29 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.