What's New
This section outlines new features in the EPC132100 version of the Framework.
Also see Features No Longer Supported.
|
Unicode support The Framework can now handle Unicode data for certain parameters in certain methods. Unicode data can also be used in code tables, the Virtual Clipboard and in tracing. See Using Unicode Data with the Framework.
|
Tailor User/Authority reports It is now possible to tailor the User/Authority reports produced by the Framework. The output can be a .csv file or it can be written out to a database. The report structure and content is fully customizable. |
|
IBM i password management New options allow IBM i passwords to be managed from the Framework logon screen. IBM i user profile error checking (eg: wrong password, password expired) has also been improved. |
Reusable parts as code table data handlers Reusable parts can now be used as code table handlers. This simplifies coding because most default processing is done by the ancestor component. See Code Table Data Handlers Can Now Be LANSA Reusable Parts.
|
|
Overriding object captions You can provide additional information to the end-user by Temporarily Overriding Object Captions. |
The Programming Code Assistants feature has been updated All WEBEVENT code assistants have been removed. All images and screen shots have been updated to match the latest release of LANSA. The graphic quality of all images and screen shots has been improved. |
|
Indicate development status of objects Developers can now attach development status indicators and notes to Framework objects. The indicators and notes are visible when the Framework is run in development mode. See Development Status. |
Updated organizations business object instance list The shipped Organizations Business Object Instance List provides improved summary and preview information when you hover over an item in the tree. |
|
Improved security VLF-WEB/NET temporary state files are now encrypted. |
uQueryCanDeactivate reason codes You can now find out what the user is trying to do when the uQueryCanDeactivate check occurs using the optional Reason Code parameter. |
|
New theme The new 2014 clean theme is a low key, clean, crisp and flat theme that is designed to reflect the style used in later Windows products. The predominant color is white. See New Theme 2014 Clean. |
Instance list with Direct-X features The shipped Resources business object’s snap in instance list browser now uses (and requires) Direct-X features. |
|
Visual Styles can be changed at run time If you need a visual style to change at run time, you can swap in a new style or styles from any command handler, filter, or snap in instance list. See Change a visual style at run time.
|
Improved demo images The demo images have been improved. |
|
Option to enable WEBEVENT functions The ability to use WEBEVENT filters or command handler is a now a deprecated feature. If you have an existing Framework that already contains WEBEVENT filters or command handlers and you wish to add more, you can Enable Framework for WEBEVENT Functions on the on the Framework Properties tab.
|
Alternative find path algorithm in RAMP-TS Developers of large RAMP-TS systems using Axes 3.1 can now use an alternative Find Path algorithm, Find Path V2. The new algorithm is much faster, but may occasionally result in RAMP finding a different path between screens than it did with the old algorithm. So thorough re-testing of the RAMP application is required if changing from one algorithm to the other.If users in large RAMP systems are experiencing delays the first time they go from one screen to another, it is possible that the number of RAMP nodes in the session are making it difficult for the Find Path algorithm to find a path between the screens. Using the new version of the algorithm may solve this problem. To activate Find Path V2 use this statement in your login script:
GLOBAL_bUseFindPathV2 = true;
In the application trace, the line "Using Find Path V1" or "Using Find Path V2" will indicate which algorithm is being used.
|
|
Reusable parts as instance list relationship handlers Instance list relationship handlers can now be created as reusable parts. The code for the reusable part version is simpler, and similar to the code used by filters to write to the instance list. See Reusable Parts as Instance List Relationship Handlers.
|
|