Polski
Q&A - Data Safety and Integrity
1. Does the system guarantee a partial, safe and ordered access to data?
2. Does HumanWork guarantee integrity of data during their exchange with other applications?
3. Does the system guarantee the certification within SSO for AD (Active Directory) and 'Single Sign On' logging?
4. Does the system provide programming interface for self-integration with customer systems (API)?
1. Does the system guarantee a partial, safe and ordered access to data?
HumanWork is a safe and stable system equipped with safety mechanisms based on secure and tested standards. The key safety features include:
Access Rights
Defining HumanWork access rights is flexible and allows to identify each access type to data.
Individual access rights are grouped in sets and then assigned to access right groups of system users. HumanWork administrator can assign users to previously defined groups and also can create new groups independently.
Edition Blockade
HumanWork database can operate on blockade mode which means that during the edition of specified data by one user, this data is blocked for other users.
Document Version Management
HumanWork supports storing and management of documents (any file type) and constantly monitors their changes performed with the use of other applications (i.e. text or graphic editors). After the document edition has been finished, the changes are automatically loaded and saved in HumanWork.
Conventionally, successive changes are overwritten in current document version. Yet, they can also be saved as separate versions of the same document. If a document has been changed by two or more persons at the same time, the author of those changes receives a task to solve the problem of conflict versions. Document version history allows to browse previous versions and to set any version as the current one.
Safety Mechanisms
HumanWork is equipped in safety mechanisms based on tried and tested standards. Data authorisation and authentication is performed with the use of MD5 algorithm. Depending on server capacity, encoding of the saved data is also possible.
Controlled Way of Server Fail
In case of server incapability, back-up copies are regularly done (according to standard procedures of MySQL and MSSQL Data Base Servers) in order to enable data restore.
In case of server failure, user units release a suitable announcement. As the entire information transformed by the system is only stored in database (user units and server application use access files only), so a regular, for example, 24 hour database backup in connection with safety system mechanisms will allow for the maintenance of a high safety level of the archive data.
Database Failure Restoration
HumanSTORE engine, which HumanWork is based on, enables database restoration after its failure. Owing to the fact that each database operation is recorded in transactions, it allows for its withdrawal in case of failure. The engine has its own transaction management, independent of database transaction procedure.
Data safety execution (impersonation, information disclosure, data substitution, data modification, getting super-user rights)
On the assumption of the inner line transmission safety, data is protected inside of the objects on a very low level. The reading or edition trials (if there was a right to read) generates an exception of ACCESS DENIED, which does not make a particular piece of information flow out of the internal data or substitute its value.
Data encoding during system access by WWW browser
During an access to HumanWork by an internet browser, data is transmitted in an encoded data transmission network with the use of SSL (Secure Socket Layer) algorithm. Owing to that, it is possible to access all available information in the system via internet, without a risk that it will be ‘overheard' or distorted.
2. Does HumanWork guarantee integrity of data during their exchange with other applications?
HumanWork was created on the basis of our own HumanSTORE programming platform, which means that we have a full control over its integrity algorithms. Those algorithms enable data transfer between HumanWork and external applications through Web Service (XML, SOAP and WSDL). It is a very flexible solution which enables HumanWork to integrate with different system types regardless of the technology they were created in.
We offer the following strategy of data exchange between HumanWork and other applications: instead of the unnecessary doubling of competences, both systems carry out tasks they have been created for. Data exchange stops at the stage of data transmission, which enables the identification of elements used by both systems.
3. Does the system guarantee the certification within SSO for AD (Active Directory) and 'Single Sign On' logging?
HumanWork can use database logging in Windows mode. The user is identified in the same way as it occurs during logging into the operating system. All safety rules offered by Windows are also valid. Such working mode is particularly important when operating with external files managed by HumanWork, however saved on file server. Access to particular user catalogues is determined by a defined access level on the operating system level (i.e. with the use of Active Directory).
The use of that logging mode is compatible with SSO. Using one login and one password in the operational system (within a particular domain), the user has a possibility of logging both into the database as well as using all other system resources subscribed to the user within a chosen domain (LDAP).
Apart from ‘Windows mode', HumanWork enables a direct logging to database. In that case, the information about both login and password is saved in the database. During logging, the user is identified by database server on the basis of a particular entry in system table. Each user is subscribed to a chosen access group, on the basis of which they receive an access to particular database records.
Yet, it is worth indicating that using a direct logging to the server database; the functionality of simultaneous access restrictions to other data, different from those in the resource system database (i.e. operating system catalogues or other resources subscribed to the user within the domain) is not available. That does not occur with the use of ‘Windows mode.'
4. Does the system provide programming interface for self-integration with customer systems (API)?
HumanWork can work with external systems on the basis of a number of technical variants. An optimal method is selected individually depending on requirements and available tools on the side of the external system.
Middleware standard programming
HumanSTORE allows for integration with the standard use of middleware programming (e.g. Sybase Orchestrator). It consists of a set of enabling services that allow to send and receive data between HumanWork and external systems with the use of Web Services (XML, SOAP, and WSDL). Middleware application as based on for example Web-services allows for independence from modification in the third system. At the same time parallel modifications on the server side are possible which provides data or downloads it to/from an offered solution.
HumanWork as an integration platform for other systems
HumanSTORE can use any integration mechanism (e.g. Middleware or Web Services) to assimilate with other systems (e.g. SAP). Such a solution allows for a wide spectrum of data reception as the entire functional interface of our system is already prepared for data exchange.
Integration with external data warehouses
The elasticity of technology in which HumanWork has been made, allows sending data to external data warehouses. The realisation of this function lies in defining when data exchange should occur (in certain moments of system operating or after using dedicated operations) and writing proper operating functions (handlers).
Integration with scanners (e.g. Xerox)
The consecutive versions of external document which are the result of scanning can be directly enclosed from any locality (source catalogue). There is also a possibility of a fixed connection between one of HumanWork's document boxes and any folder available at user's computer (including network folders). In that case, the system creates an external document for each file occurring in a particular folder. This operation can be done on demand or automatically. Owing to that, documents can be later processed in any way as well as defined with any number of attributes and inserted in work and document flow according to HumanWork business processes.
Integration with fax systems
HumanWork can work with each fax server allowing for communication with user applications. A simple interface, integrated with API, is sufficient to send documents. [We assume that API should provide a possibility of document printout and, in case of fax reception, gives access to its image].
Integration with mail systems
HumanWork gives an access to the full service of electronic mail with an unlimited number of email accounts. Sending and receiving of mail takes place the same way as task transmission. Electronic information gets to particular inboxes according to fixed mail filters. The filters sort out incoming mail and enable to define a task or a business procedure which a particular type of message is to start. Owing to that, the entire incoming documentation can be directly incorporated into the whole system and then transformed. HumanWork can operate both with mail systems based on SMTP/POP protocol as well as MS Exchange Server.
Integration with OCR programming
There are two integration variants:
|
System Tuning
HumanSTORE (business application generator in which HumanWork was founded) has a developed system of an internal profiling. There is a possibility to examine the duration of each operation as well as counting up a number of elements transformed in particular queries.
Profiling mechanism can be switched on at any time. For this process it can be defined the functionality, which is going to be examined as well as the range of data the transmission of which are going to be measured. In case of the examination of complicated processes, it is possible to create profiling or testing scripts (OCL, BASIC).
HumanSTORE has a built-in control mechanism of its actual activity, which is presented by a special indicator projected in the corner of application window. Owing to that, it is possible to find out what the system is up to at the moment (readout, data record, processing of basic query etc.) All of those allow for a fast and efficient analysis of the state of application at any time.
Self-modelling and process verification
HumanWork supports users within process modelling and functionality processing. The simplicity of creation and verification of business processes allows for an easy and independent development of system by people with no IT knowledge. Process modelling and modification takes place without the necessity of application code change or formation. Owing to that, the designer can independently model, correct and optimise all the procedures.
System personalisation
HumanWork system interface can be freely personalised by the users according to their preferences.
The personalisation consists in:
|