Release Notice for Customers Upgrading to EPC141006

Visual LANSA Framework (VLF)

141006

• Partitions must be multilingual and RDMLX enabled.
• VLF-ONE requires either Chrome (latest), Firefox (latest), MS IE10, or MS IE11 for developers and end-users.
• If you are using RAMP-TS then developers must have MS IE10 or MS IE11 installed.
• For RAMP-TS applications aXes software must be at version 3.11 or later, and aXes 3.11 patches Axes_ANY_Patch_VLFONE_155198 and Axes_311000_Patch_RAMP_155820 must be applied.
• Any Newlook software used with RAMP applications must be at version 8.0.5.14769 or later.
• If you upgrade Newlook software, new license codes may be required. 

If your VLF version is not listed contact your LANSA vendor for advice.

To find out your version start your Framework as a designer. Use the Help -> About menu options. Scroll to find VL Framework Build Number.

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

1. You must upgrade all partitions within a LANSA system.

2. On IBM i servers, when the VLF-ONE demonstration system is required, you should use the Partition Initialize administration option to import the PERSYS (Personnel demonstration system) material - even if you have already imported PERSYS prior to applying EPC141006.

3. All XML files (Framework definitions) should be opened and resaved.

4. Any VLF-ONE custom entry points derived from UF_OEXEC must be recompiled. If you have a #VLF_ONE.uTerminate method call you may need to add parameter Browserisclosing(True) to it.

5. Any VLF-ONE server custom logon components must be recompiled.

6. If you have created VLF tools or extensions that use private (ie: undocumented) VLF-WIN or VLF-ONE properties, methods, or events you may need to modify and/or recompile them.

7. Custom VLF-WIN developer or designer entry points may no longer function.

1. 1. 1. 1. * Administrator and end-user entry points will still function.
         2. * A custom designer entry point would have originated from copying UF_DESGN, a developer entry point from copying UF_DEVEL.
         3. * Upgraded entry points have an invalid method named ProcessHelpRequest that needs to be replaced with:

Mthroutine Name(ProcessHelpRequest) Options(*Redefine)
Set Com(#Handled) Value(False)
If_Ref Com(#Requestor) Is_Not(*null)
If_Ref Com(#uFramework) Is_Not(*null)
Invoke Method(#uSystem.uShowTopic)
Endif
Set Com(#Handled) Value(True)
Endif
Endroutine

You must perform this upgrade using a user profile that is QSECOFR, part of the QSECOFR group, or has *ALLOBJ and *SECADM special authorities.

See What's New in EPC141006.

1. If you have not already done so, upgrade LANSA to V14SP1 (EPC141000) level.

2. Then follow the installation steps On LANSA Developer PCs and Windows Servers for the rest of the steps required.

If you are using server-side components of the Visual LANSA Framework or are using RAMP, you need to update any IBM i servers you are using.

1. If you have not already done so, upgrade LANSA to V14SP1 (EPC141000) level.

2. If you use RAMP:

1. 1. 1. 1. * Do not upgrade until you are using aXes 3.11 (or later). See Checking which version of aXes is installed.
         2. * Apply or reapply aXes_ANY_Patch_VLFONE_155198.
         3. * Apply or reapply aXes 3.11 patch Axes_311000_Patch_RAMP_155820.

These patches can be requested from your local LANSA support team.

3. Then follow Installation On IBM i Servers for the rest of the steps required.