Release Notice for Customers Upgrading to EPC142005

Product

Visual LANSA Framework (VLF)

Build Number

142005

Pre-Requisite Details

1. VLF-ONE requires either Chrome (latest), Firefox (latest) or MS IE11 for developers and end-users.

2. If you use RAMP-TS, developers must have MS IE11 installed.

3. If you use RAMP, your aXes software must be at version 3.1.1 or version 4.1.0. Go to https://www.axeslive.com/support/updates.htm and check that you have applied the latest patches or fix packs.  

4. Any Newlook software used with RAMP applications must be at version 8.0.5.14769 or later. Note that if you upgrade Newlook software, new license codes may be required. 

 

 

 

Valid Upgrade Paths
Current VLF Version / Build Number

Can upgrade directly to EPC142005?  

Additional Actions you need to take

EPC868, EPC870, EPC130100 or EPC132100

Yes

Contact your product vendor for pre-requisites and additional actions required.

EPC140006

Yes

Review pre-requisites and complete the additional actions from:

Also perform any additional actions listed below.

EPC141006

Yes

Review pre-requisites and complete the additional actions from:

Also perform any additional actions listed below.

EPC141017

Yes

Review pre-requisites and complete the additional actions from:

Also perform any additional actions listed below.

EPC141034

Yes

Review pre-requisites and complete the additional actions from:

Also perform any additional actions listed below.

EPC141081

Yes

Perform any Additional Actions listed below.

To find out your version start your VLF Developer's Workbench or VLF-WIN in designer mode.

Use the Help -> About menu options. Scroll to find VL Framework Build Number.

Full Distribution

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

Additional Post Install/Upgrade Actions

You need to regenerate and redeploy your Framework’s XXXXXXXXXXX_LLL_VLFONE_Definition.DAT file(s) immediately after upgrading. See Improved VLF-ONE Start Up Times.

Note that you may need to adjust any customized logon screens because there have been Logon Layout Changes in Material Design Mode.

If you execute your VLF-ONE Framework in Material Design mode and have restricted access to the shipped themes or have created your own themes, your theme object must have the ForMaterialDesign property set to True. See New Themes for Material Design.

VLF-WEB users, please read Change to VLF-WEB System Definition File Names in the VLF-WEB and VLF.NET guide.

Developers of VLF-ONE applications need to regenerate their Server System Manager for each Framework if they intend to generate new components using the Common Activities.

The Server system manager is a reusable part called:  <<framework prefix>>_ServerSystemManager.

If your server system manager is unchanged from the automatically generated version, you can simply delete it, and it will be automatically created the next time you create a filter or command handler using the Common Activities.

If you wish to modify it manually, add the parameters in bold to InitializeServiceRoutine:

Mthroutine Name(InitializeServiceRoutine)

Define_Map For(*Both) Class(#Prim_dc.UnicodeString) Name(#PersistentString1)

Define_Map For(*Both) Class(#Prim_dc.UnicodeString) Name(#PersistentString2)

Define_Map For(*Both) Class(#Prim_dc.UnicodeString) Name(#PersistentString3)

Define_Map For(*Both) Class(#Prim_dc.UnicodeString) Name(#PersistentString4)

Define_Map For(*Both) Class(#Prim_dc.UnicodeString) Name(#PersistentString5)

Define_Map For(*INPUT) Class(#PRIM_ALPH) Name(#Persistent_EventDetails) Mandatory('<<NONE>>')

Define_Map For(*INPUT) Class(#PRIM_OBJT) Name(#Event_Component) Mandatory(*NULL) Help('The component issuing the event information. Use #Com_Owner in most circumstances.') Pass(*BY_REFERENCE)

 

And add the parameter in bold to the TerminateServiceRoutine:

Mthroutine Name(TerminateServiceRoutine)

Define_Map For(*INPUT) Class(#PRIM_OBJT) Name(#Event_Component) Mandatory(*NULL) Help('The component issuing the event information. Use #Com_Owner in most circumstances.') Pass(*BY_REFERENCE)

 

 

New Features

See What's New in the VLF in EPC142005 – Available May 2018.

 

Installation or Upgrade on Windows Systems  

1. If you have not already done so upgrade your LANSA system to V14SP2 (service pack 2) level.

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

 

Installation or Upgrade on IBM i Servers

 

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. You must perform all upgrade steps as user QSECOFR or as a user that is part of the QSECOFR group.

2. Make sure that no users or jobs are accessing your LANSA system. See https://www.lansa.com/support/tips/t0634.htm for how to check for active users or jobs.

3. If you have not already done so, upgrade LANSA on your IBM i server to V14SP2 (service pack 2) level.

4. RAMP users need to check that they have satisfied all the aXes version pre-requisites.

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