Tweet
Version: 2.2.20100930.0
Release Date: 2010-09-30
About this Release:
This is the first general release of Valence 2.2. Please read this entire post before installing. Existing customers running Valence 2.1 can install this version and migrate their portal data using the provided conversion tool (see Upgrading from Valence 2.1 below).
More Info on Valence 2.2:
Bug Fixes Since Last Valence 2.1 Release:
New Features Since Previous Update Release:
System Requirements:
If you need assistance with installing this release please email support@cnxcorp.com.
Release Date: 2010-09-30
About this Release:
This is the first general release of Valence 2.2. Please read this entire post before installing. Existing customers running Valence 2.1 can install this version and migrate their portal data using the provided conversion tool (see Upgrading from Valence 2.1 below).
- New Installations - Visit the Valence Store to download Valence 2.2 under the free Community Developer License or to purchase a Professional Developer License. See the Licensing page and the FAQ page for information on the current Valence licensing methods.
- Upgrading from Valence 2.1 - Existing customers running Valence 2.1 can install this version and migrate using the provided conversion tool. Valence 2.2 will install into library VALENCE22 and ifs path /valence-2.2 so it will have no effect on your current VALENCE21 or /valence-2.1 installation. Once Valence 2.2 is successfully installed, call program VVCNV22 from a green screen session and follow the prompts to migrate select data from your Valence 2.1 installation. See section 2.8 Migrating from Valence 2.1 in the Valence Manual for more information.
- Upgrading from Valence 1.X - Existing customers running Valence 1.X should contact CNX at support@cnxcorp.com for information and guidance on upgrading to version 2.2.
More Info on Valence 2.2:
Bug Fixes Since Last Valence 2.1 Release:
- Small Integer bug in vvOut – Previously small integers field types were not handled properly. This has been corrected.
- Exit Program library dependency resolved – The exit program triggered at login would only work if the program and its files resided in the Valence library.
- Resolved performance issue caused by SRTSEQ = *LANGIDSHR – This sort sequence was previously applied by default to all SQL commands processed through vvOut to support case-insensitive searching (i.e., “test” and “TEST” would work interchangeably). On certain systems this setting could cause indexes to be ignored and result in long delays in record retrieval on larger database files, so it was removed. It is instead recommended you use upper casing options and functions to handle case-insensitive searches and sorts (i.e., use TOUPPER on the vvIn procedure, and UPPER(fieldname) in the SQL command).
- Retain leading spaces in vvOut – Replaced all %trim functions with %trimr so that deliberate leading spaces are retained when responses are sent to the front-end.
- Terminal CGI error caused by error-trapping routine – When a trapped error condition occurred and an attempt was made to send an email notification, an error encountered in the process of sending the email would cause the CGI job to terminate. This has been resolved – a failed email send attempt will now simply abort the routine.
- vvIn problem with special character – Resolved issue with vvIn failing on select characters. This fix also resulted in improved performance across all vvIn procedures.
- Password encryption issue on certain character sequences – When using Valence login mode with Valence encrypted passwords, certain character sequences would result in an encrypted value that ended in a blank space and would be trimmed. This has been corrected.
- IBM i user reset when copying users – Previously the IBM i user field was copied over when using the “Copy” functionality with the Users application. This field is now initialized to blanks.
- SQL count bug in grouped statements – When a “group by” clause was used in the vvOut_execSqlToJson procedure, the total count calculation could be incorrect.
- Double byte character support in charting functions – All special characters can now be rendered properly in the Fusion Charts and Widgets components built through Valence.
- Empty portal folders omitted – Folders with no visible nodes (options) due to user authority restrictions are now properly omitted from the portal navigation tree.
- UTF16 bug in tree nodes and folders – Certain four-letter sequences of characters could be rendered incorrectly when run through the tree node decoding routine due to their hex values. This has been corrected.
New Features Since Previous Update Release:
- Kerberos and EIM Single Signon Support - New options in the Valence Portal for automatic login with Kerberos or full EIM. These existed in Beta form in the latest release of Valence 2.1; they are now officially supported features within Valence 2.2.
- New “hybrid” Valence/IBM i login option – You may now set up Valence users to log in with the password of their corresponding IBM i profile (rather than a Valence-specific password).
- Default login user ID feature – You may now configure the “User ID” on the Valence login page to default based on the last user ID specified at the PC being used.
- File Upload - New file upload capability through the VVUPLOAD program and vvIn_file procedure. This was “Beta” in Valence 2.1 and now officially supported with Valence 2.2.
- Buffered Output to browser option – New vvOut_buffer procedure (and a new vvOut.buffer parameter in the vvOut data structure) allow for sending multiple sets of data to the browser together in a single pass. This feature is demonstrated in a new example program called “Multi Store Load.”
- Support for long SQL field names – The vvOut procedures will now support long SQL field names when vvOut.longSqlNames flag is set to “Y.”
- Support for semicolon-delimited CSV files – You may now override the default comma separator to a semicolon, as is commonly used in the EU.
- Support for Ext JS form.submit – When the new vvOut data structure field vvOut.formResponse is set to “Y” then the vvOut response will be formatted in a way that the form.submit expects.
- Option to skip recordset count in SQL loads – When using vvOut.execSqlToJson, you may now set a new vvOut.skipCountCalc data structure field to “Y” to bypass the logic that counts the records in the SQL response, which will speed up the processing when the count is not needed.
- Support for non-standard form sizes in vvPDF – The vvPDF_newCustomDocument procedure was introduced as a variant of vvPDF_newDocument to support different sized forms (i.e., 11x17).
- New functionality in vvCall – The VVCALL back-end program will now accept option names in lieu of option IDs.
- Added password expiration logic – Sites using the “Valence” login method may now set select users to have an expired password. An expired password will require the user to reset their password upon logging in.
- Option to restart Valence from within portal – When changes are made to “Settings” or “Environments” you are now given the option to immediately restart the Valence instance
- New RPG testing routine – An application for testing back-end program calls was added to the Valence Portal “Development” folder
- Added purging logic – a new Valence Setting controls the amount of data retained in error and option access logs.
System Requirements:
- Any hardware running the IBM i operating system V5R4 or higher. Existing customers on previous versions of Valence at V5R3 will not be able to upgrade to this version until they are at V5R4 or higher.
- A personal computer running Windows XP/Vista/7, MacOSX or Linux (for installation only). Only the Windows version is available for download from the Valence Store. If you would like a Mac or Linux installer please email support@cnxcorp.com.
- A compatible browser on client computers. This version of Valence has been extensively tested with Internet Explorer 8, Firefox 3.6 and Safari 4.0. Google Chrome is also very likely to work fine, but we do not currently QA test Valence with Chrome.
- 5722ST1 is required to use AutoCode, and for the ability to recompile many of the Valence core programs.
- If you would like to use the PDF and/or Email capabilities of Valence then you need 5722JV1 *BASE and option 6, Java Developer Kit 1.4. This is installed on most systems by default. After installing this version of Valence, just try to run the PDF and email examples. If they work then you know for certain your system has the correct configuration. Note that even though Java is required, you do not need to know or use Java to develop PDFs or send emails with Valence. You will use the Valence RPG Toolkit procedures, which use certain Java functions behind the scenes.
If you need assistance with installing this release please email support@cnxcorp.com.
Comment