|
|
 |
|
 |
|
|
|
|
System
|
|
The system domain contains the system configuration and management functionality and is mainly intended for IT personnel. |
|
Configuration:
|
|
Entities
Used to create new or edit existing entities, their related Entity Function Patterns and their attributes.
Query
The query functionality is used to manage the laboratory query templates. These query templates are then
available to users for searching
information throughout the
application.
Users can temporarily modify the
search criteria when running a query
template.
A query template could be created to search for samples of a given project logged in during the last year. This query template would then be available to the users in the sample screen, which would be able to alter the query to search for a different project or to change the timeframe.
The results of a search can be exported using the CSV (comma separated value) format, which is compatible with Microsoft® Word and Microsoft® Excel.
Report
Used to create the mapping between the Crystal Reports report template, the screen where the report appears and the stored procedure used to extract the data.
|
|
Condition
Notification conditions that are
defined for a resource include a
Plug-in that allows validating a
given condition. LabPlus is
provided with generic notification
conditions and comprises, when
installed, up to 8 resources for
which conditions can be configured. |
|
Security: |
|
Users/Roles
In the LAP-ACE architecture all permissions is applied to roles. The authentication and authorization services are in the business layer. These mechanisms provide enhanced system security and greatly reduce configuration and maintenance efforts for multi-user installations. In addition, a skills system is used to prevent assignment of analytical methods to analysists that do not have sufficient qualifications.
Pages
Used to provide permissions (read, add, update, delete, print) on a given page to roles. This provides enhanced security, integrity and traceability, by providing the ability to implement reduced privileges.
|
|
Encryption
Encryption function is used to generate the encrypted site-specific database username/password pair.
|
|
Built-in Security
The LabPlus application has a
built-in security. The application
can be used as a standalone or
integrated to Microsoft Active
Directory.
Only authorized users can access the
system, its pages, its functions and
the data. System, page, and
functional access are granted
through application roles and a
given user can be a member of
multiple roles. The LabPlus roles
are created using the application
security screens contained in this
section of the application.
It is also possible to define what
information is display in screens
for each role, which allows the
implementation of a need-to see
policy for data access.
If needed data transmission between
the server and client stations can
be encrypted using SSL. The LabPlus
security requires an encrypted VPN
through Secure Socket Layer (SSL).
Password:
The LabPlus application can be
integrated as Single Sign On with
Active Directory (AD) which provides
exhaustive password management
capabilities. In standalone (SA)
mode, it is possible to configure
password enforcement rules through
the use of LabPlus Plug-ins. |
|
Programming: |
|
Plug-ins - Workflow Modeler
Used to view, test and debug the
Plug-In. The Plug-ins are linked to entity events and can reference utilities, methods, objects and properties of the ACE and LAP libraries. The Plug-ins development screen offers a debugging tool and pre-compiles the Plug-ins to minimize the potential for runtime errors.
Debug
The debug function is used to manually synchronize the data caching and system metadata, which could be required during updates and database restoration activities.
Traces
The traces function is used to view the event log of the application. This log lists all the errors generated by the application and is useful for support personnel.
Archival
LabPlus provides comprehensive archival mechanisms.
|
|
|
|
|
|
