Visual LANSA Framework (VLF) EPC868

Date : 16 May 2011

Visual LANSA Framework (VLF) EPC868 provides cross browser capability for VLF-WEB and new features that improve performance, productivity, functionality and usability.

ProductVisual LANSA Framework (VLF)
Build Number868
Pre-Requisite DetailsYou must be using a LANSA V12 Confirmed or Maintained platform.
See Supported Platforms Document
LANSA systems must be at Version 12 GA - with EPC859.
For RAMP-TS applications Axes software must be at version 2.10.004 (or later).
Any newlook software used with RAMP applcations must be at version (or later).
If you upgrade Newlook software from version 7.0 to 8.0, new license codes may be required.
Future Planning NoticeShipped demonstration material and examples will continue to be biased towards multilingual and RDMLX enabled LANSA partitions.
Valid Upgrade Paths
Your Current VLF LevelCan you upgrade directly to EPC868?Additional Actions you need to take that are NOT described in this document
EPC793YesObtain copies of the EPC804.HTM and EPC826.HTM upgrade notices.
Consolidate the Additional Actions they advise into your upgrade planning for EPC868.
EPC804YesObtain a copy of the EPC826.HTM upgrade notices.
Consolidate the Additional Actions they advise into your upgrade planning for EPC868.
EPC826YesPerform the Additional Actions in this document only.
EPC831YesPerform the Additional Actions in this document only.
EPC839YesPerform the Additional Actions in this document only.
EPC843YesPerform the Additional Actions in this document only.
Full DistributionThis is a full distribution. It may be used to install a brand new VLF or to upgrade an existing one.
Additional ActionsAll existing relationship handlers need to be recompiled and redeployed because of the new date/time columns in instance lists.

Existing VLF web browser applications must be (re)saved so as to (re)generate the associated HTML and JavaScript definition files before executing the application. The regenerated HTML and JavaScript files need to be (re)deployed to production environments as part of your upgrade plan. NOTE: VLF-WEB is now multi-browser capable. Existing hand coded JavaScript or HTML in WAMs, WEBEVENT functions or RAMP scripts may not be. You will need to test it.

If you are using RAMP then you will need to merge the shipped VF_Macro information (see below).

If you are install the server side components of the Visual LANSA Framework on a language JPN (Japanese) IBM i you must follow the extra steps given in the Installation Developer System i / IBM i - Language JPN (Japanese) section.
System i / IBM i Specific Special NotesThe System i / IBM i instructions are expedited procedures that assume a sound knowledge of OS/400.
You should perform upgrades under a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.
Document UpdatesUpdates to these guides are part of this EPC:
  • LANSA047.chm - Deployment Check Lists for Visual LANSA Framework
  • LANSA048.chm - Visual LANSA Framework Guide
  • LANSA049.chm - Rapid Application Modernization Process (RAMP) Guide
  • LANSA050.chm - RAMP-TS Guide
  • VLFNETSDK.chm - VLF .NET Snap-in Components Guide

Major New Features in EPC868

Refer to the "What's New" section in these guides:

  • LANSA048.chm - Visual LANSA Framework Guide
  • LANSA050.chm - RAMP-TS Guide

Detailed changes

CCS id.Description
130343Improves the way that the details of the user and date/time of a framework change are handled by the merge tool.
133146For IBM i servers, you can validate the password entered by the user exactly as typed.
136923This change allows programmers write snap instance list handlers that can signal SetCurrentInstance with a new option ExecuteDefaultCmd(FALSE). This causes the framework to not execute a command when the user clicks on an entry in the snap in instance list. This allows the end user to select the command they want, using the right mouse click menu, without automatically displaying a command handler.
137056A change has been made to the way messages are displayed in the VLF Message box at customers request. Longer messages will now wrap around to the next line and will not require the message box to be resized.
138464This enhancement introduces a new Framework level property, uUseWindowPattern, with a default value of FALSE. Setting this property to TRUE causes VLF secondary windows to be created using the same entry point form used to start the VLF.NOTE: The uUseWindowPattern property can only be set by editing the Framework's system XML file.
139134For PCs that display CRLF in a string field as strange characters, the note summary list in the demo notes example now shows the memo text with all the CRLFs replaced with spaces.
139363A problem with the DBCS character setting in RAMP-TS has been corrected. This problem was showing up as buttons displaying corrupted DBCS text in User mode.
139400Changes have been made to VLF visual styles to make the edit fields on the minifilter more visible when themes are used.
139511Corrects an issue with RAMP server IP addresses being truncated to 20 characters.
139602Corrects a date fast part (FP_RDATE) issue with odd-numbered days when storage format is set to YYYYMMDD. This change circumvents a .NET runtime version issue with the parsing of floating point numbers.
139790A new Framework Services property, avCmdPanelState, will return the current state of the Command handler panel in relation to the Framework. When the panel has been maximized this property will return MAX and NORM if it has not been maximized. This property is only available within command handlers.
140041This fixes a problem with RAMP Script checking in development environments when the partition execute directory is on a mapped drive, and the user's temporary directory is local. When a script was checked, in this scenario, it would cause an error to be issued like "line 1 invalid character" or "line 0 invalid character".
140237Problem trapping send keys when issued from a pop up has been corrected - the sendkey was being ignored.
140271A change has been made to what Business Objects appear in the Quick Find dropdown under 'Recently Used'. Business Objects that have been switched to but do not have 'Allow selection from Navigation Pane' option set are no longer displayed. Switching to Business Objects that do not have 'Allow selection from Navigation Pane' option set is not recommended.
140357An issue has been corrected where the use of comment lines defined by '//' as the first characters causes script errors in Design mode when they are the last line in an PAMP-NL Invoke script. It is recommended comments in scripts be enclosed within '/* */'.
140690A set of new script functions, LOCK_FRAMEWORK and UNLOCK_FRAMEWORK, has been add to RAMP-TS. Use these functions to lock a framework, specify the locking message to be displayed and subsequently unlock the framework.
140942If there are no objects in a framework, including the framework itself, that are allowed to be launched into another window the contents of the WINDOWS menu are now displayed which allows users to change the overall theme if they are allowed to do so.
141044A problem has been corrected for Business Objects that have subtypes. If the command panel is maximized it stays maximized when the new tabs are selected.
1411571. A new Java Script function called RESIZE_CURRENT_FORM() is provided to let you override a screen's sizing properties. 2. You should call this function from an ARRIVE script. Refer to the attached RESIZE_CURRENT_FORM.doc for usage details.
141921Framework entry point forms based on UF_EXEC, UF_ADMIN, UF_DESGN or UF_DEVEL can now optionally change the path used to load the virtual clipboards and/or include a unique name portion into the names used for the virtual clipboard files.
142201An issue with closing multiple VLF windows that contain RAMP-TS commands screen wrappers has been corrected. Users would not normally strike this problem.
142531An issue has been corrected with the command handler panel when floating. The caption on the floating command handler panel was not always correct. Also, the command title bar sometimes appears. Both these issue have now been corrected.
142593Rectifies a problem which may or may not result in a deleted screen to remain as a target of other screens sometimes occurring when navigating screens with automatic script updating turned on. As part of this fix a clearer indication that automatic script updating has been turned on is now displayed.
142866Commands can bypass Framework or RAMP locks in VLF.WIN applications. The Bypass Locks option can be used to allow certain instances of commands to execute even though the Framework or RAMP may be locked.
142925This correction prevents RAMP-TS screen flashing on button click when no field has the focus.
142943You can now add Date and Date/Time Columns to the standard shipped instance list.
142980An issue has been corrected in RAMP-TS where the MainLogin form would randomly not be recognised by RAMP causing the navigation plan to fail. In such cases the trace would show that the current form is blank
143506Each business object can have its own screen layout.
143571A problem has been corrected web filters generated with the Program Coding Assistant were giving errors when checked in for compile.
143606A new property, Allow Dynamic Overriding of Default Application Texts, has been added to the Framework Details tab in the Framework Properties dialog box. This property specifies whether default application texts (such as User Name & Password label in the Sign In dialog box) can be overridden dynamically in the production environment.
144034A problem has been corrected where the VLF .NET SDK install was giving errors even though Visual Studio 2010 had been installed as required.

Install Instructions

  1. LOAD: Double-click on EPC868w.exe to execute it. If you have multiple Visual LANSA configurations a dialog box will be displayed listing the available LANSA configurations on your machine. Select the Visual LANSA configuration to which the EPC is to be applied. When you have selected the correct Visual LANSA configuration and pressed OK the EPC will be loaded ready for installation.
  2. INSTALL: Start your Visual LANSA IDE. Select the LANSA partition to be updated with this EPC. On the Visual LANSA logon screen click on the "Partition Init..." button and select the "Visual LANSA Framework" option. When this operation completes EPC868 has been installed into the partition.
  3. REPEAT: The preceding step for each LANSA partition that is to be installed or updated.
  4. CHECK: That all Additional Actions from this and any other relevant EPC documents have been completed.

Note: If you are using RAMP, then you should repeat the merge of the shipped Newlook macro VF_Macro into your Newlook client. See "Installation and Configuration" -> "Merge Shipped Macros into Newlook" in the RAMP guide for details of how to do this.

If you are using server side components of the Visual LANSA Framework, update any additional (ie: non-local) development Windows servers you are using.
Refer to "Setting up your Framework Environment" -> "Windows Web Server" in the Visual LANSA Framework Guide for detailed instructions.

If you are using server side components of the Visual LANSA Framework or are using RAMP, then you need to update any development System i / IBM i servers you are using. Refer to "Setting up your Framework Environment" -> "Install the Framework on the Server" -> "System i / IBM i Apache Web Server" in the Visual LANSA Framework Guide (lansa048.chm) for detailed instructions. Note that if you are only using RAMP you do not have to complete the HTTP web server setup steps.

Note: It is strongly recommended that the System i / IBM i LANSA import step in these procedures is performed under a strongly authorized user profile such as QSECOFR, a member of the QSECOFR group or the appropriate LANSA partition security officer.

If you have installed the server side components of the Visual LANSA Framework on a language JPN (Japanese) system you must complete the steps in this section.

  1. EXTRACT: Locate the zip file in the \Imports\VLFramework\ folder of your LANSA system and extract the file VF_JPN01 to a folder in QDLS file system.
  2. CONVERT: Use the XFLRTOSAVF command to convert the PC file VF_JPN01 to a save file of the same name.
  3. IMPORT: Invoke LANSA using the chosen PARTITION(ppp) parameter. Then use the option Import objects into this partition from the Housekeeping Menu to import from save file VF_JPN01.
  4. CHECK: When the import job finishes, check the import log and import job log for any fatal errors.

Visual LANSA Framework components are deployed to production environments as a part of your own application deployment strategy because they are actually part of your application, not part of LANSA per se. Remember that web browser HTML and JavaScript files need to be (re)saved and (re)deployed as part of this process for EPC868. If you are upgrading directly from EPC level 793, 804, 826, 831, 839 or 843 additional considerations may apply. Refer to the "Valid Upgrade Paths" section earlier in this document for considerations.

© 2011 LANSA