| | Known Issues
Table Widget Editor
- should only accept table source inputs (allowed me to enter a file name) * Fixed *, there was no editting on the fields at all. Made AP & Process name required fields.
|
| |
- Incorrect process name displayed at Image level if you edit the Table Source process from here. * Fixed *
- Check online help
- There is no spec to enable/disable multi-select
|
|
>
> |
- There is no option to require that at least one record be selected by the user at runtime.
- There is no way to specify a child constraint for a table source process. This means that all of the records in the PCF must be read each time the table is populated.
- There is no way to prevent a table widget from being repopulated when returning from an optional child process.
- There is no ability to specify GUI options for column fields.
- There should be separate event points for Post Read, Pre-Select, and Pre-Display
- There should be an option intercept event point with the ability to intercept table events such as click, double-click, etc.
- There is no option to specify which column the table should be sorted on when initially displayed.
- There is no option to define column headings and their GUI attributes. Column heading text is taken from the data dictionary definition of the field.
- There is no option to specify that a field (column) should perform a data lookup. Consequently, there is no option to have a data lookup populate columns for fields from other files.
|
| |
Table Source Editor
- hitting enter in key entry mode does not bring up list. Read First is set, I can't see what the problem is. Child Constraints maybe? * Fixed ***
|
| |
- Token fields do not work properly, doesn't display the token text, I get some other character, or the table doesn't display at all.
- Does not consistently execute Pre-Display, etc, after option set, ie, the table widget sets option to USER 1, Opt Int executes and then Pre-Display should re-execute (since --- OPTION is not cleared), but it doesn't always do that. See ROLE SECURITY MAINTENANCE - ACL for replication.
- Same circumstances as above, table data is not reloaded.
|
|
>
> |
- The table widget is only suitable for displaying a relatively small number of records. Otherwise, the time needed to download the records to the client can get excessive. Records can only be loaded at a rate of about 2,000 records per second. Consequently, the table widget probably cannot be used as a record selector for larger records sets. For example, the time needed to load about 30,000 records is about 15 seconds.
- The table widget is always repopulated when returning from an optional child process. This can cause long pauses if the number of records included in the table is more than a couple of thousand.
- The mouse is the only way to navigate within a table widget. pgup, pgdn, cursor up, cursor dn, etc cannot be used.
- Columns sort based on the displayed value in a column, not the field values. For example, dates displayed as mm/dd/yy will not sort in date order.
- At runtime, a table widget never seems to keep the focus. When you select a record, the focus returns to the field which had the focus before you clicked to select a record.
|
| | Drag & Drop Editor
- There should be a flag on the --- WIDGET spec to indicate if the field can accept a Drop action. This should be available for the following Widget types: button, label, table widget, html viewer, and Window Background. Currently only works for Widgets attached to a field on the image. * Fixed * There is now --- WIDGET DROP TARGET that marks a widget as able to receive a drop action. It also looks at --- WIDGET FI CHOOSE MODE to see what kind of Drop should be supported. --- WIDGET FI CHOOSE MODE has values of ANY, FILE, FOLDER, TREE where ANY is a single file or folder name. Many more widget types now support being a drop target, but still require a field on the image.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.