[8.3p3]
[We are having multiple end points for aggregation and I need response from first end point in the second aggregation but the oldresponsemap is null]
I assume you’re referring to a Beanshell rule and not to the $template$ type of variables. If so, you can dump out the Beanshell namespace like so:
for(String name : namespace.getNameSpace().getVariableNames()) {
if ("transient".equals(name)) { continue; }
Object value = namespace.getNameSpace().getVariable(name);
if (value == null) {
logger.warn(name + " = null");
} else {
if (value instanceof sailpoint.object.SailPointObject) {
sailpoint.object.SailPointObject objValue = (sailpoint.object.SailPointObject)value;
logger.warn(name + "(" + value.getClass().getSimpleName() + ") = " + objValue.toXml());
} else {
logger.warn(name + "(" + value.getClass().getSimpleName() + ") = " + value);
}
}
}
That will show you (in your logs) which variables are available. Once you do that, we can see whether that’s even the right variable to look at in the first place.
Yes, beanshell rule (before operation rule) on the second account aggregation which is in the available arguments.
According to SailPoint docs:
oldResponseMap - java.util.Map - The response object returned from earlier endpoint configuration of same operation type like Account Aggregation, Get Object, etc.
In the first account aggregation, the after rule prints the rawResponseObject and processedResponseObject without any issue
In the second account aggregation, I would need the response from first aggregation to process another entitlement attribute hence when I print oldResponseMap, the rule prints it as null.
Hi @jjpriya ,
Ensure that Account Aggregation - 1 is set as the parent endpoint for the Account Aggregation - 2 operation, so that the oldResponseMap is available in Account Aggregation - 2 operation.
