I am trying to integrate application which has a weird architecture. I am using the first endpoint to aggregate the users, and the second endpoint to aggregate the entitlements(id), and the first endpoint should be used as a parent endpoint for the second one( i need the ID of the user to get their respective entitlement). What I am trying to do is to come up with an afterRule that will slightly change the entitlement ID. The problem is my rawResponseObject and processedResponseObject are empty, even though they are supposed to contain my schema and all the elements in it. Is it because the second endpoint is a child endpoint? Is it the reason why my responses are empty?
Have you tried to pass your expected API calls in Postman first to ensure that you are getting the desired results?
I would also check and make sure that your variables are being passed correctly from one call to another to ensure that your payload is sending the correct information in order to get the desired response from the call.
You could also try to build this in the Rule Development Toolkit and see if your code is working like you expect it would.
Yes, everything is working in Postman, in fact I used the “logging” afterRule on my first endpoint(the parent) and it is populating the rawResponseObject and processedResponseObject. I checked if it was going to work with Group Aggregation Rule, and in fact it did work, however if the operation is a child, it is returning for both of this objects, and then loads the ids of entitlements, so I wonder if it is not going to work? I can send you the logs for comparison
I am using the after rule on the child endpoint, which I assumed will work and it will populate it with schema elements, but instead its empty. The first endpoint has 10 attributes and the child has only 1 attribute. The operations work, my schema element is correctly populated, no issues there. However, like I said I am not able to use the AfterRule because everything is empty
Yes, Mark, I did review it and if you can see it says that the Parent endpoint should contain child Resource Object, however, it is not true, at least in my situation
you could also try the After Provisioning Rule. I have a rule with one of my web services connector that pulls in data from source then builds the account object and sends a second API call to collect the manager information. That might also be an option to look into.
If you elimitate the second endpoint and aggregate the accounts with just the first one, do they appear ?
Are the mapppings for the endpoint one correct?
