The ExtraView platform is extremely feature rich. Features that are impossible to configure in other products are standard in the off-the-shelf ExtraView versions. When other products need significant adaptation and enhancements to provide a feature, ExtraView most often provides the functionality with simple, point-and-click functionality. The following is not an exhaustive feature list, but gives an excellent indication of why ExtraView is the most powerful issue-tracking platform available.
There are two ExtraView versions. ExtraView Standard is available without license cost and capable of implementing simple to complex application solutions for any industry sector. ExtraView Enterprise adds additional features required to implement enterprise-wide applications and to meet the needs of regulated industries. ExtraView Enterprise also implements a unique structure that allows global companies to allow each user to operate within a single instance of ExtraView in their own language.
| Ease of Use |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶
|
Web-based tool for all clients |
|
|
| |
▶
|
Rich, intuitive, fast user interface |
|
|
| |
▶
|
No client-side software |
|
|
| |
▶
|
Unlimited number of role-based layouts, views, queries and options |
|
|
| |
▶
|
Stores individual user preferences: Text size, Language, Time zone, Date format, Notification options, Roles, etc. |
|
|
| |
▶
|
Real-time data entry validation |
|
|
| |
▶
|
Supports all time zones and date formats |
|
|
| |
▶
|
Supports data entry and presentation of data in all languages and alphabets (Unicode-based) |
|
|
| |
▶
|
Can simultaneously work on multiple issues |
|
|
| |
▶
|
Context sensitive help system |
|
|
| |
▶
|
Automatic drilldown capability on all summarized information to view details |
|
|
| |
▶
|
Inbuilt help system may be replaced with customized help |
|
|
| Configuration |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
All configuration is performed through a standard web browser - no client-side software |
|
|
| |
▶ |
Multiple Business Areas or functions within a single database |
3
|
Unlimited
|
| |
▶ |
Multiple Projects within each Business Area |
2 per Area
|
Unlimited
|
| |
▶ |
Multiple user roles can be defined |
5
|
Unlimited
|
| |
▶ |
Multiple user-defined fields can be created in the data dictionary |
100
|
Unlimited
|
| |
▶ |
Unlimited number of issues can be entered and tracked |
|
|
| |
▶ |
Unlimited number of users can be supported |
|
|
| |
▶ |
Unlimited number of business processes can be supported |
|
|
| |
▶ |
Field types: Checkbox, Custom, Date, Day, Decimal, Label, List, Log, Number, Radio button, Tab, Text area, Text, User |
|
|
| |
▶ |
Field types: Currency, Document, HTML, Image, Pop-up |
|
|
| |
▶ |
No programming necessary to add fields |
|
|
| |
▶ |
Add formatting attributes to fields on layouts: Alternate title, Modify format, Height, Highlight Value If, HTML Modifier, Max length, Style |
Limited
|
|
| |
▶ |
No programming necessary to add formatting attributes |
|
|
| |
▶ |
Add logical attributes to fields on layouts: Field required, Field not required if, Field required if, Field read-only if, Field required if, Field visible if |
Limited
|
|
| |
▶ |
No programming necessary to add logical attributes |
|
|
| |
▶ |
Complete control of placement and order of fields that appear on input and report forms |
|
|
| |
▶ |
Configurable Home Page for each user with customizable dashboards |
|
|
| |
▶ |
Configure attachments to be stored inside database or on filesystem |
Database only
|
|
| |
▶ |
Issue ID's can be automatically formatted to your specification |
|
|
| |
▶ |
Configure all GUI elements to provide your look-and-feel |
|
|
| |
▶ |
Define and maintain related issue hierarchies |
|
|
| |
▶ |
User names may be displayed in several formats |
|
|
| |
▶ |
Set default values for any field |
|
|
| |
▶ |
Remember the last value entered for any field on a per-user basis |
|
|
| |
▶ |
Metadata changes are modifiable in real-time, with no system outages |
|
|
| |
▶ |
Lists may contain any number of values: various formats to display short and long lists |
|
|
| |
▶ |
Lists may be single-valued or multi-valued selection may be enabled |
|
|
| |
▶ |
Lists may be enabled with auto-complete (type-ahead) functionality |
|
|
| |
▶ |
Different roles may have different views of any issue |
|
|
| |
▶ |
Full scripting language to extend point-and-click configuration with more complex workflow rules and conditions |
|
|
| |
▶ |
Define multiple levels of administrators, each with different permissions to access different areas of functionality or different Business Areas |
|
|
| |
▶ |
Support for multiple email addresses for each user |
|
|
| |
▶ |
Full WOA RESTful (Representational State Transfer) API - utilizes HTTP for the connection |
|
|
| |
▶ |
Full SOAP Web Services API with .Net interface |
|
|
| |
▶ |
Localization framework to translate all ExtraView messages into any language allowing each user to choose which language to utilize |
|
|
| |
▶ |
Localization framework allowing the administrator to localize all configuration metadata into any language so users can view the application in their language of preference |
|
|
| |
▶ |
Text in attachments may be indexed for high-performance searching |
|
|
| |
▶ |
"User Custom" Java API to extend the base functionality of ExtraView - without any changes being made to the base source code |
|
|
| Workflow and Process Management |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
Automatic validation whilst user enters data, using the logic configured in the layouts |
|
|
| |
▶ |
Allowed value combinations of parent-child fields are automatically validated |
|
|
| |
▶ |
Comments are automatically marked with the user ID and the timestamp |
|
|
| |
▶ |
Minimal screen refreshes whilst entering data, with extensive use of Ajax |
|
|
| |
▶ |
Text fields automatically resize as more information is entered |
|
|
| |
▶ |
Mass update operations supported on any subset of issues |
|
|
| |
▶ |
Automatically or manually assign issues |
|
|
| |
▶ |
Clone records with permission |
|
|
| |
▶ |
Each Business Area may have its own workflow or may inherit a global workflow |
|
|
| |
▶ |
Each Project may have its own workflow or inherit its workflow from its Business Area |
|
|
| |
▶ |
Each workflow may have an unlimited number of state transitions |
|
|
| |
▶ |
Unlimited number of file attachments may be added to any issue |
|
|
| |
▶ |
A different workflow may be defined for each role, for each Project, for each Business Area |
|
|
| |
▶ |
Relate issues together in an arbitrary fashion or in a strict logical fashion |
|
|
| |
▶ |
Relationships may be one-to-one, one-to-many or many-to-many |
|
|
| |
▶ |
Define and control access to individual issues by a user's company name. Different users at different companies may not see each other's issues |
|
|
| |
▶ |
Full reporting on related issues |
|
|
| |
▶ |
Issues may be split into sub-issues, each with their own workflow |
|
|
| |
▶ |
Import records from delimited files: Map any field values in the input file to any field values in ExtraView |
|
|
| |
▶ |
Import list and other values from spreadsheets to save time |
|
|
| |
▶ |
Full scripting language to extend point-and-click configuration with more complex workflow rules and conditions |
|
|
| |
▶ |
Visual display of workflow choices |
|
|
| |
▶ |
Newly entered issues are automatically date and time-stamped, along with the ID of the user who performed the operation |
|
|
| |
▶ |
All updates are automatically date and time-stamped, along with the ID of the user who performed the operation |
|
|
| |
▶ |
Users may "save and continue" while updating records |
|
|
| |
▶ |
Multiple users updating the same issue cannot overwrite each other's changes |
|
|
| |
▶ |
Import metadata from a portable format, simplifying the promotion of metadata from one system to another |
|
|
| |
▶ |
Export metadata to a portable format, simplifying the promotion of metadata from one system to another |
|
|
| |
▶ |
Provide automatic translation of text from one language to a variety of other languages |
|
|
| |
▶ |
Trigger electronic signatures on any field change, or any combination of field changes |
|
|
| |
▶ |
Enables full compliance with 21 CFR Part 11 and other regulatory systems |
|
|
| |
▶ |
Define and control access to individual issues with privacy groups. If a user is not a member of a specific privacy group, they have no visibility of the issue |
|
|
| |
▶ |
Issues within privacy groups may be kept private or be made public |
|
|
| Querying & Reporting |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
Create and save public reports; reports may be saved for use by a number of roles |
10
|
Unlimited
|
| |
▶ |
Create and save personal reports |
10 per user
|
Unlimited
|
| |
▶ |
Report types: Column reports, Summary reports, Matrix reports, Dashboard reports |
|
|
| |
▶ |
Report types: Aging reports, Container reports, Service Level Agreement (SLA) reports, Custom reports |
|
|
| |
▶ |
Column reports allow the selection of any fields to which the user has permission to be displayed |
|
|
| |
▶ |
Provide up to eight levels of totaling on column reports |
|
|
| |
▶ |
Column titles remain on screen when scrolling through long reports |
|
|
| |
▶ |
Summary reports allow up to ten levels of summarization, including the count, minimum, maximum and mean of each level |
|
|
| |
▶ |
Matrix reports allow any two fields that can be counted to be displayed in a grid format |
|
|
| |
▶ |
Dashboard reports display summarized reports or charts in a format for display on user's Home Page |
|
|
| |
▶ |
Aging reports display the time issues spend in all statuses, grouped either by hour or by day |
|
|
| |
▶ |
Container reports group together the output from several reports or charts onto a PDF - useful for weekly or monthly management reporting packages |
|
|
| |
▶ |
Service Level Agreement (SLA) reports that measure workflow performance against specific criteria |
|
|
| |
▶ |
Custom reports link to information external to ExtraView, or to custom built reports within ExtraView |
|
|
| |
▶ |
Reports may have any set of filters defined and stored with the report |
|
|
| |
▶ |
Reports may have runtime filters which prompt for information when a user runs the report |
|
|
| |
▶ |
Create and store report filters using either a simple interface or an advanced interface that supports Boolean logic |
|
|
| |
▶ |
Use any number of keywords within filters to search for text within issues |
|
|
| |
▶ |
Keyword searching for text within file attachments stored in the database |
|
|
| |
▶ |
Output reports to the browser, to Microsoft Word, Microsoft Excel, Adobe PDF, text and XML |
|
|
| |
▶ |
Output reports through the API's |
|
|
| |
▶ |
Schedule reports for delivery through email |
|
|
| |
▶ |
Automatic drilldown links wherever appropriate to see more detailed information |
|
|
| |
▶ |
Access any issue at any time through a navigation bar shortcut |
|
|
| |
▶ |
Include file attachments on reports |
|
|
| |
▶ |
Restrict reporting features based on user's role |
|
|
| |
▶ |
Quickedit report mode allows the editing of data on report output without needing to drill down into the issue |
|
|
| |
▶ |
Wide variety of chart types: Pie charts, Bar charts, Stacked bar charts, Area charts |
|
|
| |
▶ |
Chart over history to see trends, or by value to see current positions |
|
|
| |
▶ |
Relate issues in different Business Areas together to form hierarchies for reports |
|
|
| |
▶ |
Create predefined layouts for inbuilt reports, Business Area by Business Area |
|
|
| Audit Trails & History |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
Every change to every field of every issue is part of a full, visible audit trail |
|
|
| |
▶ |
Every change to every issue is timestamped and annotated with the name of the person updating |
|
|
| |
▶ |
Users may access the audit trail whilst updating a record or from reporting |
|
|
| |
▶ |
Color is used to differentiate between additions, updates and deletions to each field in the audit trail |
|
|
| |
▶ |
Views of audit trails are filtered for each role based on security settings |
|
|
| |
▶ |
Enables full compliance with 21 CFR Part 11 requirements and other regulatory systems |
|
|
| |
▶ |
All administrator access and changes to metadata are tracked with a full audit trail |
|
|
| Notification |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
Send notification in HTML or text format |
|
|
| |
▶ |
Automatic notification upon record updates |
|
|
| |
▶ |
Rule-based notification upon record updates |
|
|
| |
▶ |
Define unlimited number of interest lists - mandatory or optional |
|
|
| |
▶ |
Add new issues via email |
|
|
| |
▶ |
Update existing issues via email |
|
|
| |
▶ |
Fully configurable email contents sent to issue stakeholders |
|
|
| |
▶ |
Store and use configurable email templates to correspond with users |
|
|
| |
▶ |
Automatically escalate issues which have not received the appropriate attention in a given time frame |
|
|
| |
▶ |
Automatically escalate issues which are approaching a due date |
|
|
| |
▶ |
All email notifications are subject to field-level security permissions |
|
|
| Security |
ExtraView
Standard |
ExtraView
Enterprise |
| |
▶ |
Define a hierarchy of administrators who each have control over a selection of Business Areas |
|
|
| |
▶ |
Administrators may control access to any individual end user |
|
|
| |
▶ |
All fields are controlled with field-level security permissions by each role: read/write access, read-only access, no access |
|
|
| |
▶ |
All key program functions are protected by a role-based security key |
|
|
| |
▶ |
Definable password policies and expiration procedures |
|
|
| |
▶ |
Administrator may monitor current activity, license usage, active users |
|
|
| |
▶ |
Support for an unlimited number of roles, each with its own set of field and object permissions |
5 Roles Supported
|
|
| |
▶ |
Administrators may instantly disable any individual account |
|
|
| |
▶ |
Administrators may instantly disable an individual session |
|
|
| |
▶ |
Administrators are instantly notified of repeated failed log in attempts |
|
|
| |
▶ |
All end-user system access is logged |
|
|
