Hi @Mayt  We don't have an easy way to do this unfortunately as there isn't any reference stored between assets that use custom functions and the custom functions themselves, because they are just "text" in the codefile/ruleset/decision.  ... View more

Take a look at this post and see if it helps. ... View more

The Data Query node is designed to run a single query that will return the result either as a data grid or a list of scalar variables. You cannot run multiple queries.   Here are a couple of ideas to consider: You could look at using multiple data query nodes in your decision, with a single query for each type, then in a subsequent ruleset or DS2 code file you could combine the results from those data query nodes into one. Another possible option to consider is a Data Query node that does not query on type, and then in a subsequent node have some logic that splits the result based on the type returned. ... View more

Is the scenario you describe where two different users create a decision with the same name? or where two users are working on the same decision?   I'm assuming it is the former. I'm not aware of a feature to prevent what you describe. There is no separation of users in MAS. I tried a simple test and was able to overwrite a module published by another user. Can you ensure the other user does not enable the "Replace item with the same name" option to prevent publishing with the same name? or maybe work with different versions of the decision since the module name published to MAS will include the version and this may help to avoid collisions. ... View more

@alko13 The sas-model-repository pod fails to start on OpenShift. It is necessary to perform a workaround. Please try these steps and let me know if that works. kubectl edit clusterrolebinding system:openshift:scc:hostmount-anyuid added kind: ServiceAccount   name: default   namespace:     (put your namespace name here) Then scale down sas-model-repository pod and then scale back up. ... View more