Feature #1070
Updated by Petr Michal over 6 years ago
When we use inserted script in attribute mapping, account management filter, etc., script call is generated based on script type, which often does not make sense. My common usecase: I have a simple script, that I want to use for transformation into idm and also like a transformation from idm. So I need to set the type of this script as Standard. Problem is, that I must to add attribute *attributeValue* into call always when I want to use this script in transformation. This is really non-intuitive. ------------------------ Another usecase: When I want to insert script into Account management filter in system mapping. The following code is generated: <pre> scriptEvaluator.evaluate( scriptEvaluator.newBuilder() .setScriptCode('xxxxxxxxxxx') .addParameter('scriptEvaluator', scriptEvaluator) .addParameter('uid', uid) .addParameter('attributeValue', attributeValue) .addParameter('entity', entity) .addParameter('system', system) .build()); </pre> Problem is, that filter does not include attributeValue like transformation. So unless you delete this parameter from generated code, you will end with null pointer.