For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Hello, We have been faced with a bit of a challenge trying to author rules based upon specific requirements. Essentially, Rules need to be isolated by owner (in this case, Team ABC and Team XYZ should only have access to their own rules). This is intended to be implemented via Inclusions To simplify the usecase, the user will enter their age and the rules will infer possible Offices that they should visit. Each office is accompanied by a 'location' value. Attempted Solution Rule Structure: The above structure is required because we need to isolate the rule files that will eventually be in separate rulebases (and then included in a Parent rulebase) as these will be managed by different sets of administrators (e.g. Team ABC and Team XYZ). Data Model: Relationships for the ABC offices and the XYZ offices have been created so that we can support the Rule File Structure above Rules: ABC_Office_Decision.xlsx XYZ_Office_Decision.xlsx The Problem OIA will not allow this implementation as the office's location is a multiply proven rule in two different files. Alternative Solutions
Hi James, If you make the office's location the identifying attribute for the office (delete the other attribute as it's no longer required) and then your rules can look like this: I'm not sure how you might infer other details about the office unless those could be shared rules. Best regards Ian
Thanks for that suggestion! In this case, I have used 'the office location' as an example entity attribute that needs to be populated. But unfortunately, the actually attribute are dates. So maybe something like the office's opening date. We also do need to maintain the identifier (XYZ1, ABC2, etc.). Therefore, don't think the proposed solution would work :(
Hello James, Personally I wouldn't use inclusions. I would use Decision Services. Then I can create two separate decision services, in separate Workspaces, give users permissions, use the Viewer role or the Author role to let people view or edit the Decision Services. Generally I have much more control over them. I would create references in the OPM project to each of the decision services And create entities to support ABC, XYZ and then the master entity to contain both Then I would merge the two entities into one and copy over the location to the master entity. Just my two cents Have a lovely day
Ah... Decision Services! Sad to say we're on Private Cloud 20C. Yes, this is probably the best solution for anyone looking to solve this issue. (I tried to mark this as answered but it seems I chose 'Discussion' instead of 'Question' for this post) As always, appreciate your contributions to the community, Richard!
Ah, I see. I was confused by you saying you had a test project in 21D. Happy to help, James. Whether it be a discussion or a question :)