Visual LANSA Framework (VLF) EPC843

Date : 3rd August 2009

Visual LANSA Framework (VLF) EPC843 provides complete translations for French and Japanese of the current version and new features that improve performance, productivity, functionality and usability.

Get this EPC

Download EPC843 via the LANSA Support Portal

Product

Visual LANSA Framework (VLF)

Build Number

843

Pre-Requisite Details

LANSA systems must be at Version 11 SP5 - Service Pack 5 with EPC834 (or later).
For RAMP-TS applications Axes software must be at version 132 (or later).
Any newlook software used with RAMP applcations must be at version 8.0.5.14769 (or later).
If you upgrade Newlook software from version 7.0 to 8.0, new license codes may be required.

Future Planning Notice

Shipped demonstration material and examples will continue to be biased towards multilingual and RDMLX enabled LANSA partitions.

Valid Upgrade Paths

Your Current VLF Level	Can you upgrade directly to EPC843?	Additional Actions you need to take that are NOT described in this document
EPC793	Yes	Obtain copies of the EPC804.HTM and EPC826.HTM upgrade notices. Consolidate the Additional Actions they advise into your upgrade planning for EPC843.
EPC804	Yes	Obtain a copy of the EPC826.HTM upgrade notices. Consolidate the Additional Actions they advise into your upgrade planning for EPC843.
EPC826	Yes	Perform the Additional Actions in this document only.
EPC831	Yes	Perform the Additional Actions in this document only.
EPC839	Yes	Perform the Additional Actions in this document only.

Full Distribution

This is a full distribution. It may be used to install a brand new VLF or to upgrade an existing one.

Additional Actions

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.

If you are using RAMP then you may need to upgrade to the correct newlook version.

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 Notes

The 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 Updates

Updates 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
A new version of the "LANSA Interactive Training Resources" CD is associated with this EPC.

Major New Features in EPC843

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

LANSA050.chm - Visual LANSA Framework Guide

Corrections and Other Features in EPC843 [Click here to Show table...]

CCS id.	Description
136878	This change has been made to address a problem where command handlers appear momentarily when becoming enabled for a subtype. This problem only occurs when using the Hide Other Tabs option with subtypes that have different commands enabled.
137921	Problem has been corrected where a change in a script being automatically updated results in the total number of script lines increasing to more than 999. For example, adding/removing a target screen in the screen details.
137989	A problem has been corrected where the displayed command handler was not rerun after a switch to another business object with the same command.
138079	A problem has been corrected where a parent's command handler is not refreshed when the Allow Side by Side Display option is selected.
138190	This allows wams containing weblets that do not interact with their containing filter or command handler in the documented VLF way to operate as previously - without automatically opening a new window when clicked. However this is for backwards compatibility only. You should not design applications that do this. (as stated in the documentation)
138268	A problem has been fixed in RAMP-TS where when navigating to a Command handler the value objCommand.uAlphaArg1 is not retrieved correctly. The value of objCommand.uAlphaArg1 remains at the value for the previous Command Handler.
138270	An extra save file, VF_JPN01, will be shipped with EPC843. This will be built to restore to a V5R3 IBM i system.
138289	The way instance lists handle column data that is too wide to fit into the available space has reverted to the way it was before EPC839. Horizontal scroll bars are now used instead of wrapping.
138294	Corrects an issue that may occur on a slow PC using RAMP-NL and rapidly entering data. Data being entered into a non-newlook screen area (eg: a filter) may be lost when the keystrokes are temporarily redirected into the newlook panel area.
138313	A problem has been corrected in the RAMP-TS script editor where blank lines are temporarily added to the top of a script being changed.
138357	The Instant Prototyping Assistent no longer uses accented characters for the user object type of the business objects it creates when they appear in the given caption. The accents are now stripped and the unaccented characters are used.
138424	A problem has been fixed in VLF-NET where Column heading are garbled when instance list data is exported to a CSV file on a DBCS system. Column heading are now correctly exported.
138438	This change allows the shipped spooled files handler to work with DBCS spooled files.
138456	A problem has been resolved where running VLF-WEB applications run in Japanese (Language JPN) gave XML errors on start up.
138457	Build warning messages about some depreciated VLF_WIN components should no longer occur during deployment of a Visual LANSA Framework.
138478	Prevents a brief flash from appearing when a set of command handlers is maximized and you move from tab to tab.
138484	When sending an instance list to excel, the delimiter used has been changed to use the windows international setting for list separator, rather than always using a comma.
138494	This issue happens when you do not use the VLF for user profile management. In this case the VLF creates a temporary user object for the user that has been allowed access via the customer's own logic. If you then use an inactivity timeout, the message shows the user name as "New User".
138505	A problen has been fixed where Filters with no hints (Blank hints) will still show the hint bubble (even though it is blank).
138523	Improves the smoothness with which RAMP-NL navigations that end by hiding the RAMP-NL form are displayed.
138751	A problem has been fixed where the RAMP_TS Session busy warning message was coming up when switching to a instance level RAMP-TS command handler.
138808	A typographical error in the caption of generated RAMP-TS scripts has been corrected.
138825	The shipped User Imbedded Interface Point (IIP) UFU004 has been changed for heavy usage because of the number of time it potentially can be called. Comments also changed slightly.

Installation - Developer's Visual LANSA Workstations (VL-IDEs)

LOAD: Double-click on EPC843w.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.
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 EPC843 has been installed into the partition.
REPEAT: The preceding step for each LANSA partition that is to be installed or updated.
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.

Installation - Developer's Windows Servers

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.

Installation - Developer's System i / IBM i servers

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.

Installation - Developer's System i / IBM i servers - Language JPN (Japanese)

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.

EXTRACT: Locate the zip file VF_JPN01.zip in the \Imports\VLFramework\ folder of your LANSA system and extract the file VF_JPN01 to a folder in QDLS file system.
CONVERT: Use the XFLRTOSAVF command to convert the PC file VF_JPN01 to a save file of the same name.
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.
CHECK: When the import job finishes, check the import log and import job log for any fatal errors.

Installation - Production/End User Workstations and Servers

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 EPC843. If you are upgrading directly from EPC level 793, 804, 826, 831 or 839 additional considerations may apply. Refer to the "Valid Upgrade Paths" section earlier in this document for considerations.