Release Notes
|
| Return to the Index |
Contents |
Overview |
Version 4.0 is a major release of the IUIE application including new features and a tutorial overview. The most important enhancements include BARR printing capability, a search function, and the ability to schedule report objects. These changes are summarized below.
To meet user demand, the IUIE allows users to direct their PDQ output to Special forms BARR Printers. These are forms such as payroll checks, Degrees, official watermarked documents, etc. This option is available as a text-input field or a drop-down list.
An IUIE tutorial is available via the Tutorial button on the IUIE welcome screen, and via the HELP button.
An IUIE Training Manual is also available in the Master Catalog from the IUIE folder.
Users can locate Report Objects using a simple search that searches for Report Objects by label name or a descriptive phrase. An advanced search allows for more specific search criteria. Information Providers have the added ability to search within test or production publishing catalogs.
With the exception of Frozen (static) reports, all Report Objects now provide an option to send report output to a BARR Printer destination, using the same four-letter BARR printer code currently used in the Information Center, FDRS, or other applications.
Users can now schedule Report Objects to run daily, weekly or monthly at any specific time of the day during IUIE Online hours.
The scheduling feature can be accessed only after saving the report object settings/parameters a feature implemented in the last major release.
The Schedule submenu of Manage Jobs is now implemented from which users can edit scheduling parameters.
The registration form has been modified to include specific data access permission requests with new accounts.
A new category of user, "Non-IU" has been provided by departmental request.
Users can update contact information from the Preferences page, which has been streamlined to remove obsolete options.
The inbox in My Catalog has been removed.
All remaining catalog trees were modified to load faster after significantly reduced load times of the Master Catalog and My Catalog’s Index of Report Objects were noted in the last release with a new method of loading the catalogs.
A Request-Access form now loads if a user selects a Report Object they have not received permission to access.
Minor additions and enhancements were made to the IUIE to support the migration of FDRS report data.
The preference option that hides restricted Report Objects has been corrected and functions as expected.
Currently, the PDQ BARR printer output default can be changed to allow users to specify a special form BARR Printer.
Subject and campus are now required information when setting up a new user access or security group.
The dropdown widget for Datagroups has been enhanced to display a limited list of values.
Publishers can specify a where clause that will be appended to the Valid Values query, which restricts the rows to the subset that meets the conditions set forth in the where clause.
In terms of Lookup values, users can restrict the rows returned by specifying a code column pattern and/or description column pattern.
For indexed reports, a publisher now can specify the orientation and font size of a report.
Publishers can now concatenate multiple columns and add constant text to the returned values for the code and description column for valid values. This feature was dubbed "Pattern".
A blank Valid Values synonym is now available.
The Create New Report Object confirms creation using the label name instead of the technical name.
By default, Frozen Files retain 7 versions.
The Test Folder is fixed to properly use PDQ security (based on underlying Datagroup)
Now security of data is the same both in the production and test instances. Changes have been made such as assigning access in publishing has been changed so that separate Test and Production are no longer assigned – only one set of security now.
Only row-level user groups are listed in publishing when a Report Object is row-level secured.
Only subject areas related to the application code of the Report Object are listed in the “Subject Area(s)” section of publishing.
Only user groups related to selected subject areas for the RO are listed in the “Assign Access to Groups” section of publishing.
Publisher’s requests for Data Manager approval are not automatically routed to the appropriate Data Managers based on the groups assigned to the RO.