DataSplice Extended Product Features
The following features of DataSplice technology are what truly make it powerful. Clients can utilize these cutomization tools to craft a system that aids and supports a current CMMS workflow process.
- Event Processing
- Dynamic Attributes
- Data Entry Restriction and Validation
- Conflict Detection and Resolution
- ODBC Connectivity
- Plug-in Architecture
- Concurrent Licensing
- Administration Privilege Delegation
Event Processing
The DataSplice server can be configured to perform a wide range of actions in response to numerous data modification events, such as updates, inserts, deletions etc.
The corresponding action associated with an event is then preformed in one of two ways: before/after the associated data modification, or instead of the modification altogether. Multiple actions may also be chained together in response to the same event.
This enables business logic to be implemented in database procedures and other external code without creating triggers or other modifications that might affect other systems using the database.
Using event processing capabilities, users may:
- Call a database procedure and map current values to the parameters.
- Send an email with details about the current event to a team lead for necessary review.
- Call an external application, such as a report generator.
- Run code in external plug-in modules. (Currently Java and .NET platforms are supported.)
In addition, actions can be made conditional on certain information. For example, the system will send an email to a supervisor only if key measurements are out of range or other error conditions are met.
More information about Event Processing.
Dynamic Attribute Definitions
DataSplice attributes are a simple way to define variables that act as information placeholders. They may be referenced throughout the application to create flexible behavior for data and associated actions. Power to define variables makes DataSplice a dynamic, user-friendly solution.
Attributes in DataSplice are arranged in a data hierarchy. This means they can be defined at different levels in the system to customize behavior for certain users, groups, or views.
For example, an attribute could be defined at a system-wide level to generate a specific default behavior for all users. The network administrator can then define the same attribute to override the default behavior for certain users or groups.
In addition, attributes may be defined as static values (such as defining an attribute DEFAULT_STOREROOM with a value of CENTRAL) or as the results of queries using contextual information. For example, a query attribute could be used to assign the Crew ID for the current login to an attribute so it can be passed to database procedure calls.
Every performance feature in DataSplice can be customized using the attribute feature:
- Default values for fields.
- Filters designed to return relevant data for users and groups.
- Connection profiles so groups from different sites access the correct data source.
- Database procedures and emails used to perform events may include detailed information about specific data is changes.
More information about using attributes in DataSplice.
Data Entry Restriction and Validation
DataSplice allows the administrator detailed control over a user's data entry permissions for particular fields. This criteria is essential for ensuring data integrity in the underlying databases that manage enterprise data.
The Administration Client can be used to define lists of valid entries for particular data fields. Valid entries may be:
- Static lists of values, such as permissible status codes.
- Dynamic lists generated by queries to other views from the selected record.
Dynamic lists provide extremely powerful information management capabilities on the Remote Client. Users quickly access all the information they need through one selected record. Values lists can be configured to display as drop down lists or in a separate window to provide more contextual information.
All data validation rules can be set to restrict input to specific values, or to use the value lists as suggestions but still accept arbitrary input from the user.
Conflict Detection and Resolution
DataSplice is designed to interoperate with external applications using the same data. Therefore, it cannot lock data to prevent conflict because the same data is being accessed by users of other applications.
To compensate for this, DataSplice technology has powerful capabilities for detecting and resolving conflicts that occur when data has been modified externally. These capabilities are especially important when DataSplice is used offline.
DataSplice provides the network administrator total control over defining data conflict detection for views, including:
- No conflict checking. The system performs updates regardless of the current data.
- Utilizing timestamp fields and other rowstamp columns to detect concurrant modifications.
- Checking the entire contents of a current record against the database version for discrepancies.
- A dual-approach to data verification - checking for conflicts in important status fields but overlooking them others.
More information about conflict handling.
ODBC Connectivity
DataSplice connects to database servers via ODBC, a widely used API standard promoted by Microsoft. For more vendor information, see http://www.microsoft.com/data.
ODBC connectivity allows applications to connect to a wide range of database servers without the need for platform-specific coding. This capability is key to the DataSplice goal of enabling enterprise-wide access to data. Using ODBC, the DataSplice user needs no knowledge of the underlying database servers being accessed - DataSplice operates in exactly the same way regardless of the RDBMS in use. ODBC makes it very easy to configure DataSplice for new database servers as the need arises, with no custom programming needed.
The widespread acceptance of ODBC by major vendors attests to its robustness, flexibility and usability. Numerous benchmarks show that ODBC is as fast as major native interfaces, and in some cases, actually outperforms them.
Plug-in Architecture
The extensive plug-in architecture available with DataSplice technology allows the application to be customized to meet a variety of data needs for mobile users. Both the server and clients can load plug-ins.
- Event action plug-ins enable external business logic to be invoked in response to events.
- Authentication plug-ins delegate login tasks to external systems, such as NT Domains or MAXIMO® software authentication.
- Client-side barcode printing plug-ins, or other application-specific tasks that are not part of the basic Remote Client package.
Concurrent Licensing
Licensing is an important responsibility for system administrators and managers. Administrators need a simple and logical system for license administration, and a reliable method to maintain uninterrupted service for all licensed users regardless of system volume.
To avoid support headaches, DataSplice employs a concurrent licensing scheme. At login, each user obtains a license from an available pool. Clients release license tokens back to the pool when they are no longer needed. Licenses are not tied to handheld devices or other client workstations, and multiple connections from the same client or with the same login name are valid.
License starvation is a concern with many products. When all available licenses are consumed, not even the network administrator can log in to correct a situation unless a session is terminated or more licenses are installed.
To help clients address the issue, DataSplice offers license pooling. At least one license is always reserved for the Administrators group, regardless of how many other clients may log in. In addition, reserved pools of licenses can be assigned to any DataSplice user group, insuring critical users get first chance at access.
Multi-Level Administration Privileges
To maintain tight IT security standards, a company may designate a small number of DataSplice administrators as superusers. Superusers have full data privileges, and are able to change program settings at any time. They can also grant restricted administration privileges to other staff members, such as department heads or foremen. DataSplice offers customizable, multi-level administrator privileges to support client demand.
Initially, a built-in user called Admin is predefined as the sole DataSplice superuser. Admin has all available administrator privileges permanently enabled. Admin can then designate other users as DataSplice administrators simply by adding users to the Administrators group.
From there, Admin can grant full or limited administrator privileges to these additional administrators. For example, an added administrator might receive privileges to modify data views, but be restricted from creating or deleting views.
More information about DataSplice administration.
