Hello, I am getting an error as shown below when I am trying to execute the BeforeProvisioning rule while doing account move from one OU to another. I am not sure what could be the issue as I have all the null check.
[“RuleExecutionException (ruleName\u003dTest AD BeforeProvisioning): BSFException: BeanShell script error: Sourced file: inline evaluation of: \timport sailpoint.object.Identity; \timport sailpoint.object.ProvisioningPlan; \t . . . \u0027\u0027 unknown error: null : at Line: 13 : in file: inline evaluation of: \timport sailpoint.object.Identity; \timport sailpoint.object.ProvisioningPlan; \t . . . \u0027\u0027 : try { \n BSF info: Test AD BeforeProvisioning at line: 0 column: columnNo, caused by org.apache.bsf.BSFException: BeanShell script error: Sourced file: inline evaluation of: \timport sailpoint.object.Identity; \timport sailpoint.object.ProvisioningPlan; \t . . . \u0027\u0027 unknown error: null : at Line: 13 : in file: inline evaluation of: \timport sailpoint.object.Identity; \timport sailpoint.object.ProvisioningPlan; \t . . . \u0027\u0027 : try { \n BSF info: Test AD BeforeProvisioning at line: 0 column: columnNo”]
Hi Anuj,
Can you describe what you’re trying to accomplish in this rule? From what I can see, you’re trying to select the OU for the user and modify a few attributes. What I’m seeing in here can realistically be done with transforms and then using the Services Standard Before Provisioning Rule. It will make it less work for your team over time if you don’t need to maintain this rule for operations you can accomplish with other methods
There are certain validations which we need to do before changing the OU of a user, so doing those validations. I had AAA session with SailPoint and they suggested that in this scenario Services Standard Before Provisioning Rule cant be used as those are usually used as is or very minor changes.
I put it as we wanted to understand if there is issue with the rule at any place and after suggestion from SailPoint. But these lines doesn’t seem to be issue but issue lies somewhere else which we are not able to figure out