Overview
This post is a continuation of Part 3 - Radiant Logic Install Instructions. Now that the infrastructure is in place, it is time to implement the use case from the previous blog article introducing this concept. As a reminder, the plan is to deliver a view of the HR, CRM and inventory systems, and to join the information into a common view. Once that is available, logic can be implemented to make determinations about activities that are required. We are going to identify salespeople on vacation with customers that have low inventory. Keep in mind that there are multiple ways to do this. I am leveraging this approach to simplify the configuration. This is not what I suggest for production implementations.
Table of Contents
Part 4: Implementing the Use Case
Implementing the Use Case
To create this example, I generated three proxy views that point to the underlying repository. No data is stored on the appliance itself in the scenario.
The first view is the proxy (customers) for the customer data. The purpose of this view is to bring in the customer list, the customer's sales representative and their current inventory of Mad Marauder t-shirts. To make the data easier to consume, I created a computed attribute which calculates the inventory for a customer and concatenates it with the customer name.
The second proxy (data) is the list of internal employees. A computed attribute has been created that creates the data needed for the sales dashboard by combining the salesperson’s name with the inventory attribute that was generated on the customer proxy.
The customerInventory attribute is made available by joining the data proxy to the customer proxy and returning that attribute and related values.
Similarly, the manager view proxy (managerview) is joined to the employee view to bring back the salesDashboard attribute and associated values.
For this example, the following screenshot shows the list of customers in the system. Note that this list is being dynamically generated in the proxy and is not a static representation of the information.
There are also two employees listed for this example. Ann is the employee on vacation and Steven is her manager.
Looking at the manager branch there are two things to consider. The first is that the users have been limited to only managers. Second, Ann is displayed in the salesDashboard attribute that was brought in through the join. Remember that join was the result of a join from the employees to the customers in order to get the customer inventory. Sample logic is also displayed to show that Ann is on vacation.
This data can then be leveraged by a web application to make it easily consumable.
By taking advantage of lower cost hardware that can be easily clustered, we were able to build a solution that gave Steven important insights into the company’s customers. He now knows that Global Inc has 0 inventory and their sales rep is out of the office. There are limitless other uses that can be found for such a device. Maybe you can come up with a couple as well.