PlanetJ corporation
WOW Version and Feature Guide
Web Object Wizard |
Version/Edition Information
This
document describes WOW features by version.
WOW ships currently in four versions:
ENTRY, STANDARD, PROFESSIONAL, and
Id |
Item |
Entry |
Standard |
Professional |
|
Description |
1 |
(AS/400) ISeries Data Driver |
*1 |
* |
* |
* |
JDBC access to iSeries DB2/400 database. (Read Access). Entry provides 5-report limit. |
2 |
Oracle Data Driver |
* |
* |
* |
* |
JDBC access to Oracle database. (Read Access) |
3 |
MS SQL Server Data Driver |
* |
* |
* |
* |
JDBC access to MS SQL Server (Read Access) |
4 |
MYSQL Data Driver |
* |
* |
* |
* |
JDBC access to MYSQL (Read Access) |
5 |
JDBC-ODBC Data Driver to MS Access, MS EXCEL, CSV files |
* |
* |
* |
* |
JDBC access to MS Access, MS Excel (Read Access) |
6 |
IBM DB2 Windows Data Driver |
* |
* |
* |
* |
JDBC access to IBM DB2 (Read Access) |
7 |
Apache Tomcat |
* |
* |
* |
* |
WOW capable of running on Tomcat 4.x and high application servers. |
8 |
IBM WebSphere |
* |
* |
* |
* |
WOW capable of running on WebSphere 4.x and high application servers. (5.x and high recommended) |
9 |
High performance data cache |
* |
* |
* |
* |
Powerful caching of data for a user specified time period. |
10 |
Data Paging |
* |
* |
* |
* |
For large reports, the ability to return only a specific # of records and then allow the user to page down through the data. |
11 |
Customize field headings |
* |
* |
* |
* |
Ability to dynamically specify field headings for reports. |
|
|
|
|
|
|
|
12 |
File associations and drill downs |
|
* |
* |
* |
Ability to “link” and drill down from data set to data set. For example, drill down from summary data to details. |
13 |
Download to MS EXCEL |
|
* |
* |
* |
One click downloads to MS Excel in CSV format. |
14 |
XML conversion |
|
* |
* |
* |
Convert data into XML format. |
15 |
Dynamic runtime prompting for queries |
|
|
* |
* |
Ability to prompt the user at runtime for selection parameters. |
16 |
Possible value or pick list support |
|
|
* |
* |
Ability to specify pick list values from any database to be used as pick lists in selection or update operations. |
17 |
Dynamic drill down associations with user prompting |
|
|
* |
* |
Ability to drill down to data with dynamic selection criteria. |
18 |
Scheduled operations |
|
|
|
* |
Ability to schedule operations to execute in batch at a specific interval. For example, send a report to sales staff each evening at 11pm. |
|
Security: |
|
|
|
|
|
19 |
Require Operating System user profile |
|
|
* |
* |
Allow specification and automatic enforcement that a valid OS user profile is required to run an application. |
20 |
Local user only support |
|
|
* |
* |
Allow specification and automatic enforcement that users require an internal IP address. This can be used to secure INTRANET only applications from use over the public Internet. |
21 |
Secure operations |
|
|
|
* |
Ability to secure operations or queries to specific groups. For example, only management can view and execute this report. |
22 |
Field level security |
|
|
|
* |
Ability to dynamically assign authorized users to view or edit a particular field. For example, vendors can view the inventory quantity but can’t edit the value while customer support can both view and edit the value. |
|
Data Operations |
|
|
|
|
|
23 |
Data updates |
|
|
|
* |
Ability to update any database record(s). |
24 |
Data delete |
|
|
|
* |
Ability to delete any database record(s). |
25 |
Data insert/adds |
|
|
|
* |
Ability to insert or add any database record(s). |
26 |
Data copies to another system |
|
|
|
* |
Ability to copy data from one database system to another. For example, DB2 to Oracle. |
29 |
Auto-populate records |
|
|
|
* |
Ability to auto-populate a record based on a user selection. For example, automatically populate a vehicle record once a VIN # was specified. |
30 |
Auto increment field values |
|
|
|
* |
Ability to have a field automatically increment itself. For example, an order number may obtain the next numerically higher value and use that as the order number. |
31 |
Concurrent updates (Optimistic Lock) |
|
|
|
* |
Optimistic lock support by allowing specification of the behavior to enforce if database values have changed since the data was read from the database. |
32 |
Status Change request |
|
|
|
* |
Ability to change record contents when a field is changed. For example, if a purchase order is set to urgent, allow input of expedite data. |
33 |
Merge into pre-built MS EXCEL |
|
|
|
* |
Ability to extract and merge data dynamically into a pre-built MS Excel file. Allows layout of format, graphs, pivot tables and then runtime merging of data. |
34 |
Intelligent Field Behavior |
|
|
|
* |
Fields can be assigned a business behavior such as Social Security Number. Once set, complete validation and prompting are automated. Support provided for major field types. |
|
SELF SERVICE |
|
|
|
|
|
35 |
Database driven security |
|
|
|
* |
Ability to authenticate users by a secure database. Useful for securing B 2 B and B 2 C applications via data driven userid and password combinations. |
36 |
User specific value support |
|
|
|
* |
Ability to tie and restrict data results to a specific user. For example, when a financial customer signs on, they would ONLY see their account information. Useful and required for all “self service” applications. |
|
Extensions |
|
|
|
|
|
37 |
Custom user interface |
|
|
|
* |
Ability to customize the layout, look and feel, and graphics. |
38 |
Custom data pages |
|
|
|
* |
Ability to customize insert, edit, and view screens providing any level of user specific detail. |
39 |
Custom logic |
|
|
|
* |
Ability to override and extend logic using Java. For example, only updates, if the customer status is open. This provides the solution to any type of requirement. |
40 |
Integration with Eclipse and WebSphere Studio |
|
|
|
* |
Ability to import and extend WOW within the Eclipse and WebSphere Studio environments. |