Architecture: DecisionCentric® Client Interface
From a technical perspective, the client component of the DecisionCentric business intelligence product is a “Smart Client.” The term Smart Client indicates that the it is both self-deploying and self-maintaining. For the IT staff, This is a big benefit. Because it is self-deploying and self-maintaining, the Smart Client limits the amount of time required of IT to support the business user during installation and when upgrading. Your IT staff need never even visit the business user’s desk.
Decision Technology designed the DecisionCentric client specifically around the needs of the business user. Because of this, the smart client reduces IT’s support workload. Also, the Client component of the DecisionCentric business intelligence product is written in Microsoft C#, is based on the .NET framework, and communicates with the server using Web Services. As a result, the Client and DecisionCentric as a whole are Service Oriented Architecture (SOA) “friendly” in many ways that other business intelligence products are not.
The DecisionCentric client software provides the user with access to various business intelligence tools, including Query, Reporting and Analytics. The wizard-based interface of the product guides users through a managed process to get the information they need—without knowledge of SQL or database organization.
In short, the smart client of the DecisionCentric business intelligence product provides the best of both worlds for end users and your IT staff. DecisionCentric is a business intelligence product that empowers end users to integrate, analyze and publish business intelligence. At the same time your organization’s IT staff reaps the benefits of centralized deployment and update that the smart client of the DecisionCentric business intelligence product provides.
Key Features
- Browse tables and columns and add them to the requests using a point and click interface.
- Access tables and views from any of the available and supported databases in a single request.
- Set parameters or “prompts” for specific fields (columns) for users to enter values while executing the request or by using predefined values.
- Save requests in user libraries for retrieval, scheduled execution or sharing between users.
- Set options to show the SQL generated for the request.
- Join database fields of same values but different data types from different tables.
- Compress and encrypt data (128 byte encryption) for transmission over the network for security.