I have entities on Visual Investigator. Let's say I have the following entities and relationships: Entities: Employee Supplier Invoice Purchase Order Purchase Request Relations: PurchaseOrder_to_Invoice PurchaseRequest_to_PurchaseOrder Employee_to_PurchaseRequest Employee_to_PurchaseOrder Employee_to_Invoice Invoice_to_Supplier PurchaseOrder_to_Supplier I want to write a rule using the Scenario Administrator. Let’s say our rule is as follows (and we don't have Intelligent Decisioning): If the invoice value is greater than 10,000, and the PO unit price is 50% higher than the unit price of other POs, and the Employee’s department is not procurement, and the Supplier has been registered within the last year, then generate an alarm. And generate the alarm on the supplier entity. In such a rule, I need information from the Employee, PO, Invoice, and Supplier entities all together. While writing a rule in the Scenario Administrator on VI, I can only use one entity at a time. I think I need to join these entities and create a new entity (scenario input table) to write this rule on VI. And if I create this entity, I would also need to define relationships between the scenario entity (scenario input table) and the other main entities to assign the alarm to an actionable entity. This method doesn’t seem very sustainable because, by doing so, the network might get cluttered, and I would be showing the same information to the end user under different entities. Am I thinking about something wrong here? What is the best practice for such a scenario? Should I find a way to generate the alarms in SAS Studio and send them to Visual Investigator via API? I am open to any suggestions, documentation, and training videos. Thank you in advance for your contributions.
... View more
