From within the custom java cleanse code, you can call any APIs, including SIF. But what will be the use case for such a scenario? Are you trying to update the value from another base object?
Yes like said you can perform SIF within the Cleanse jar. But will be a fat jar with all dependent libs, also the connection props with env specific urls/hostport details in it need to be adjusted before deploying into each server.
A better approach could be to develop a DaaS webservice and call them in the E360 transformations. They have larger scope and much flexible.
They can simply be deployed in your appserver or ETL server or another process in the Avos workflows.
I came across this KB article which states that it is not possible to call the SIF from custom java cleanse function.
Not sure if this was the limitation in older versions of the product.
Yes, the KB holds true. It may or may not work. The custom cleanse functions are assumed to be performing logic that is not covered in our out of the box cleanse mappings, and purely should be used for a cleansing operation, also the underlying assumption is that they operate on the data that is passed to them, i.e., that they don’t make calls out to other jars.
What is your exact business use case here?