This page provides documentation for issues and advisories which have been noted, fixed, have workarounds or are in the process of being fixed. This change log is for version 5.0 and later of Iguana.
Jump to:
- Change log for Iguana 5.6.20 – February 12, 2015
- Change log for Iguana 5.6.19 – January 22, 2015
- Change log for Iguana 5.6.18 – January 9, 2015
- Change log for Iguana 5.6.17 – December 19, 2014
- Change log for Iguana 5.6.16 – December 17, 2014
- Change log for Iguana 5.6.15 – December 5, 2014
- Change log for Iguana 5.6.14 – November 21, 2014
- Change log for Iguana 5.6.12 – October 31, 2014
- Change log for Iguana 5.6.11 – September 10, 2014
- Change log for Iguana 5.6.10 – September 5, 2014
- Change log for Iguana 5.6.9 – August 22, 2014
- Change log for Iguana 5.6.8 – July 15, 2014
- Change log for Iguana 5.6.7 – June 12, 2014
- Change log for Iguana 5.6.6 – May 12, 2014
- Change log for Iguana 5.6.5 – April 14, 2014
- Change log for Iguana 5.6.4 – March 24, 2014
- Change log for Iguana 5.6.3 – February 13, 2014
- Change log for Iguana 5.6.2 – January 16, 2014
- Change log for Iguana 5.6.1 – December 2, 2013
- Change log for Iguana 5.5.7 – October 18, 2013
- Change log for Iguana 5.5.6 – June 21, 2013
- Change log for Iguana 5.5.5 – June 12, 2013
- Change log for Iguana 5.5.4 – April 5, 2013
- Change log for Iguana 5.5.3 – March 6, 2013
- Change log for Iguana 5.5.2 – December 20, 2012
- Change log for Iguana 5.5.1 – November 9, 2012
- Change log for Iguana 5.0.14 – May 18, 2012
- Change log for Iguana 5.0.13 – April 5, 2012
- Change log for Iguana 5.0.12 – January 26, 2012
- Change log for Iguana 5.0.11 – January 20, 2012
- Change log for Iguana 5.0.10 – November 18, 2011
- Change log for Iguana 5.0.9 – October 27, 2011
- Change log for Iguana 5.0.8 – October 5, 2011
- Change log for Iguana 5.0.7 – September 8, 2011
- Change log for Iguana 5.0.6 – July 14, 2011
- Change log for Iguana 5.0.5 – July 4, 2011
- Change log for Iguana 5.0.4 – June 6, 2011
- Change log for Iguana 5.0.3 – May 17, 2011
- Change log for Iguana 5.0.2 – April 7, 2011
Iguana 5.6.20 Change-Log (top)
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed issue with race condition that could in theory cause Iguana to crash on heavy GUI activity such as having multiple users in translator sessions. This issue can be avoided in a production server by reducing unnecessary user activity in the GUI. [Affected Releases] Iguana 5.6.19 [Tracking Numbers] #25854 ************************************************************************** Changes ************************************************************************** 1) [Description] Changed Iguana to sanitize more GET parameters to prevent XSS and external redirects. This has not been seen in a production context but was raised as a potential issue by a customer. [Affected Releases] Iguana 5.6.20 [Tracking Numbers] #25851 2) [Description] Changed the SFTP Lua API to better handle white spacing in file names to remove the need for complicated escape sequences. [Affected Releases] Iguana 5.6.20 [Tracking Numbers] #25759 3) [Description] Updated and validated that it is safe to use Chameleon with Java 8. [Affected Releases] Iguana 5.6.20 [Tracking Numbers] #25859
Iguana 5.6.19 Change-Log (top)
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed bug that was preventing sessions from timing out under some circumstances. This a recommended patch if you are running 5.6.16, 5.6.17, or 5.6.18 if your configuration involves more than a million daily calls to Iguana's web APIs. This fix will optimize the memory consumption in this scenario. [Affected Releases] Iguana 5.6.16-5.6.18 [Tracking Numbers] #25767 ************************************************************************** Changes ************************************************************************** 1) [Description] Changed behavior of Iguana's APIs to immediately terminate temporary sessions after the API response is sent. This minimizes the amount of resources consumed for API calls. [Affected Releases] Iguana 5.6.19 [Tracking Numbers] #25767
Iguana 5.6.18 Change-Log (top)
**************************************************************************
Bug Fixes
**************************************************************************
1) [Description]
Fixed bug that was making api_query (log API) ignore URL parameters.
This issue was introduced in the 5.6.17 release.
[Affected Releases]
Iguana 5.6.17
[Tracking Numbers]
#25718
2) [Description]
Fixed bug that was forcing channels to always switch back to using
their latest milestone.
[Affected Releases]
Iguana 5.6.15, 5.6.16, 5.6.17
[Tracking Numbers]
#25745
3) [Description]
Fixed bug that was preventing Iguana's net.http lua module from
properly handling 302 redirects. This is long standing obscure issue.
[Affected Releases]
Iguana 5.6.x
[Tracking Numbers]
#25606
Iguana 5.6.17 Change-Log (top)
**************************************************************************
Bug Fixes
**************************************************************************
1) [Description]
Log Export fixed to correctly handle multi-menu select box with no selections.
[Affected Releases]
Iguana 5.6.x
[Tracking Numbers]
#25650
2) [Description]
Custom LLP Ack memory leak fixed.
[Affected Releases]
Iguana 5.6.x
[Tracking Numbers]
#25692
Iguana 5.6.16 Change-Log (top)
**************************************************************************
Feature Additions
**************************************************************************
1) [Description]
Added "rxmatch" and "rxsub" regular expression APIs to Iguana's
standard string library.
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25689
2) [Description]
Added "S" function to Iguana's standard node library to convert node
values to strings and remove the need for the node module.
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25690
3) [Description]
Added "split" function to Iguana's standard string library to remove
the need for the stringutil module when splitting strings on a given
delimiter.
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25691
4) [Description]
Added support for SQL Server's XML, sqlvariant, and time data types
when using the SQL Native Client ODBC driver.
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25591
5) [Description]
Added sessions API to gather information about active Iguana sessions
in a JSON format.
e.g. http://localhost:6543/session/list will return a JSON list of
all active session ID's
e.g. http://localhost:6543/session/detail?id=xyz will return details
about the session with ID xyz
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25630
6) [Description]
Added Iguana license API to gather or update license information in a
JSON format.
e.g. http://localhost:6543/license/detail will return a JSON object
with your current license details
e.g. http://localhost:6543/license/update?key=xyz will update your
license key to xyz and return a JSON object with your new
license details
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#25649
**************************************************************************
Changes
**************************************************************************
1) [Description]
Upgraded PCRE library to 8.36
[Affected Releases]
Iguana 5.6.16
[Tracking Numbers]
#23383
Iguana 5.6.15 Change-Log (top)
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Check for correct milestone attribute in configuration file when using use_most_recent_milestone set to true. [Affected Releases] 5.5.x thru 5.6.10 [Tracking Numbers] #25628
Iguana 5.6.14 Change-Log (top)
************************************************************************** Changes ************************************************************************** 1) [Description] Added support for SQL Server's DateTimeOffset data type. [Affected Releases] Iguana 5.6.14 [Tracking Numbers] #25004 ************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed bug in database error handler to prevent potential crashes when Iguana encounters unsupported database drivers. [Affected Releases] Iguana 5.6.14 [Tracking Numbers] #25004 2) [Description] Fixed bug that would occasionally cause Iguana to indicate a channel has a negative queue count. [Affected Releases] Iguana 5.6.14 [Tracking Numbers] #25507
Iguana 5.6.12 Change-Log (top)
************************************************************************** Feature Additions ************************************************************************** 1) [Description] Added limit parameter to Iguana's log API to restrict the number of messages being returned. e.g. http://localhost:6543/api_query?limit=10 will return 10 log entries. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25327 2) [Description] Added reverse and unique parameters to Iguana's log API. "reverse" will return logs in order from newest to oldest (vs the normal behavior of oldest to newest). "unique", when combined with type=Messages, will return only unique message logs (vs including ignored and resubmitted messages). e.g. http://localhost:6543/api_query?type=messages&unique=true will return a list of unique messages in order from newest to oldest. e.g. http://localhost:6543/api_query?reverse=true will return all logs in order from newest to oldest [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25404 3) [Description] Added environment variable IGUANA_MILESTONE_LISTING_LIMIT to allow users to restrict the number of visible milestones displayed after clicking the "View saved milestones" button in a translator. [Affected Releases] 5.6.12 [Tracking Numbers] #25392
************************************************************************** Changes ************************************************************************** 1) [Description] Limited number of nested elements annotations and autocomplete will display to improve user experience. Annotations will now only display elements nested up to 30 levels deep, and autocomplete will now only give suggestions 30 levels from the current level. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25314 2) [Description] json.serialize will now accept tables that include userdata objects with __tostring defined in their metatable. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25348 3) [Description] Removed LuaJIT from 64 bit Linux builds of Iguana to maintain a consistent Lua version across all platforms. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25436 4) [Description] Updated OpenSSL to 1.0.1j to fix the "POODLE" exploit identified by the OpenSSL team. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25380 ************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed bug in log browser that was preventing messages from being exported under certain circumstances. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #252561 2) [Description] Fixed bug preventing annotations from appearing when auto-execute is disabled. Annotations will now appear once after each manual code execution. [Affected Releases] Iguana 5.6.12 [Tracking Numbers] #25298
Iguana 5.6.11 Change-Log (top)
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed bug in the log viewer that was preventing messages from being exported from multiple inbound channels at once. [Affected Releases] Iguana 5.6.11 [Tracking Numbers] #24872 2) [Description] Fixed bug where Iguana's demo channels weren't being activated completely with version control. [Affected Releases] Iguana 5.6.11 [Tracking Numbers] #25176
Iguana 5.6.10 Change-Log (top)
**************************************************************************
Changes
**************************************************************************
1) [Description]
Optimized version control to reduce disk I/O and significantly improve
UI responsiveness on large Iguana installations.
[Affected Releases]
Iguana 5.6.10
[Tracking Numbers]
#24514
2) [Description]
Upgrade AIX build of Iguana to use OpenSSL 1.0.1i. This brings Iguana
up to 1.0.1i on all operating systems.
[Affected Releases]
Iguana 5.6.10
[Tracking Numbers]
#25111
Iguana 5.6.9 Change-Log (top)
************************************************************************** Changes ************************************************************************** 1) [Description] Upgrade Iguana to use OpenSSL 1.0.1i to fix new vulnerability in older versions identified by the OpenSSL team. [Affected Releases] Iguana 5.6.9 [Tracking Numbers] #25029 ************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Removed JavaScript logging to fix error on session timeout in Internet Explorer. [Affected Releases] Iguana 5.6.9 [Tracking Numbers] #25093 2) [Description] Fixed bug where importing sample data from Iguana logs was using the wrong GET parameter. [Affected Releases] Iguana 5.6.9 [Tracking Numbers] #24981
Iguana 5.6.8 Change-Log (top)
************************************************************************** Changes ************************************************************************** 1) [Description] Upgrade Iguana to use OpenSSL 1.0.1h to address SSL/TLS MITM vulnerability in OpenSSL cryptographic software library. [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24762 2) [Description] Changed net.http.post and net.http.put to no longer include the "Expect" header by default in order to increase execution speed. [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24883 3) [Description] Changed naming scheme of dbs Lua API to allow for more annotation space. [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24870 4) [Description] Translator sample data count now displays "None" through n message count while remembering the last message used by the current browser. [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24887 ************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fixed bug where file diff dialog potentially renders HTML & JavaScript [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24792 2) [Description] Fixed bug so filter VMD settings upgrade correctly from old TREe-based versions of Iguana (3.3.2 or older) [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24842 3) [Description] Fixed bug so demo channels load & run correctly when running Iguana with --working_dir flag. [Affected Releases] Iguana 5.6.8 [Tracking Numbers] #24843
Iguana 5.6.7 Change-Log (top)
************************************************************************** Feature Additions ************************************************************************** 1) [Description] Added method to Iguana Web API: /get_server_config to return Iguana configuration. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24686 2) [Description] Added option to view file diff in 'File has changed on disk' dialog [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24689 ************************************************************************** Changes ************************************************************************** 1) [Description] Change Iguana logging behaviour on filtered messages to match 5.5.7 showing unqueued messages. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24537 2) [Description] Change so that iguana.webInfo reports invalid host names in the ip attribute instead of throwing an error. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24516 3) [Description] Change so that enviroment variable IGUANA_WEB_SOCKET_IDLE_TIMEOUT_SECONDS can be used for fine grained timeout control on web socket closing. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #22763 4) [Description] Change so default behaviour on LLP listener now times out after 30 minutes of inactivity [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24595 5) [Description] Change and remove VB6 support so that Chameleon runs in Windows 8 [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24694 6) [Description] Ubuntu version now built on Ubuntu 12.04 [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24643 ************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fix JSON map alpha sort to provide annotation message when user attempts mixed key types. Supported key types integer and string can not be mixed within a map. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24478 2) [Description] Fix so that Iguana can run as a service in 32 bit Ubuntu. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24596 3) [Description] Fix so that 'File has changed on disk' dialog choices clearly identifies differences and choice for which version to use. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24689 4) [Description] Fix so that DICOM libraries inter-operate stably with Iguana on Windows, Linux and Mac OS X. DICOM shared library bundled in Iguana package. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24591 5) [Description] Fix to make Iguana more resistant to port vulnerability scanners. Iguana maintains better responsiveness after scanning. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #23054 6) [Description] Fix so Annotation visibility contained to Lua. [Affected Releases] Iguana 5.6.7 [Tracking Numbers] #24645
Change log for Iguana 5.6.6 (top)
************************************************************************** Feature Additions ************************************************************************** 1) [Description] Enable editing CSS, javascript, and HTML files in the Translator. [Affected Releases] Iguana 5.6.x [Tracking Numbers] #24528
************************************************************************** Changes ************************************************************************** 1) [Description] Default channel components for adding a channel are LLP Listener and To Translator. [Affected Releases] Iguana 5.6.6 [Tracking Numbers] #24615 2) [Description] Sample data now handles clipboard operations and \r\n. [Affected Releases] Iguana 5.6.6 [Tracking Numbers] #24581
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fix IE8 problem with Log message re-submitting so that 'Resubmitting ...' page completes. [Affected Releases] Iguana 5.6.x [Tracking Numbers] #24588 2) [Description] Fix IE8 problem with Dashboard link for queue count to correctly filter messages. [Affected Releases] Iguana 5.6.x [Tracking Numbers] #24599 3) [Description] Fix for plugin channel not starting when maximum licensed channel limit is used. Issue: If you have a 7 (or n) channel license and are running 7 (or n) channels, and you are running one or more plugin channels then one plugin channel will not start. [Affected Releases] Iguana 5.6.6 [Tracking Numbers] #24146
Change log for Iguana 5.6.5 (top)
**************************************************************************
Feature Additions
**************************************************************************
1) [Description]
Added method to Translator API:
filter.zip.deflate
Create a binary zip file image from a lua table.
[Affected Releases]
Iguana 5.6.5
[Tracking Numbers]
#24365
2) [Description]
Added method to Translator API:
iguana.channelConfig
Return an XML document containing the channel configuration.
[Affected Releases]
Iguana 5.6.5
[Tracking Numbers]
#24481
************************************************************************** Bug Fixes ************************************************************************** 1) [Description] Fix session timeout so that on user activity browser session reflects expected extension. [Affected Releases] Iguana 5.6.5 [Tracking Numbers] #24200 2) [Description] Fix Mac OS specific crash on replacing demo channel. [Affected Releases] Iguana 5.6.5 [Tracking Numbers] #24434 3) [Description] Apply libssh patch to skip sending permissions and fix Translator net.sftp API on file getting permission issue. [Affected Releases] Iguana 5.6.5 [Tracking Numbers] #24464 4) [Description] Fix crashing on Translator ftp.put. [Affected Releases] Iguana 5.6.5 [Tracking Numbers] #24477 5) [Description] Upgrade Iguana to use openssl 1.0.1g to address Heartbleed bug in OpenSSL cryptographic software library. [Affected Releases] Iguana 5.6.5 [Tracking Numbers] #24496
Change log for Iguana 5.6.4 (top)
**************************************************************************
Feature Additions
**************************************************************************
1) [Description]
Added get_milestone Channel API returning list of milestones for a
translator project.
[Affected Releases]
Iguana 5.6.4
[Tracking Numbers]
#24318
2) [Description]
Added methods to translator API set:
chm.fromXML
invokes a Chameleon style conversion of XML into HL7
chm.toXML
invokes a Chameleon style conversion HL7 into XML
filter.zip.inflate
returns a lua table containing decompressed files.
iguana.status
returns an XML summary of Iguana runtime state.
iguana.webInfo
returns a Lua table listing Iguana web server and HTTP channel
configuration.
[Affected Releases]
5.6.4
[Tracking Numbers]
#24408
**************************************************************************
Changes
**************************************************************************
1) [Description]
Log browser pop out that displayed data synchronized with main view
removed from GUI.
[Affected Releases]
Iguana 5.6.4
[Tracking Numbers]
#24210
2) [Description]
Sample data editor now escapes line feeds and represents them as \r\n
in MESSAGE text editor.
[Affected Releases]
Iguana 5.6.4
[Tracking Numbers]
#24411
**************************************************************************
Bug Fixes
**************************************************************************
1) [Description]
Passive LLP consumer plugin fixed by updating internal thread usage to
move request onto separate networking thread.
[Affected Releases]
Iguana 5.6.4
[Tracking Numbers]
#24185
Change log for Iguana 5.6.3 (top)
************************************************************************* Feature Additions ************************************************************************* N/A ************************************************************************* Changes ************************************************************************* 1) [Description] Mark plugin, database and To HTTPS channel components as Legacy to encourage Translator component usage. [Affected Releases] Iguana 5.6.3 [Tracking Numbers] #22914 2) [Description] Fast ACK input now matches output for MSH[11] Processing Id. [Affected Releases] Iguana 5.6.3 [Tracking Numbers] #24069 ************************************************************************* Bug Fixes ************************************************************************* 1) [Description] Iguana fixed so that XML based VMDs with escaped characters are correctly handled. [Affected Releases] Iguana 5.6.3 [Tracking Numbers] #24133 2) [Description] Iguana fixed From HTTPs channel component request buffer handling while under load. [Affected Releases] Iguana 5.6.3 [Tracking Numbers] #24108
Change log for Iguana 5.6.2 (top)
******************************************************************************** Feature Additions ******************************************************************************** 1) [Description] Added FTPS Explicit SSL connection mode support. [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23958 2) [Description] Improved logging capability to show events in Windows Event Log and on Posix into syslog. [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23535 ******************************************************************************** Changes ******************************************************************************** 1) [Description] Improved the recognition of SQL Server uniqueidentifier Data. [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23978 2) [Description] More informative external authentication error logging provided on unexpected response. [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23743 3) [Description] LLP Client Host Address field whitespace is now trimmed. [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23804 4) [Description] Improved the LLP listener idle connection iteration routine [Affected Releases] Iguana 5.6.2 [Tracking Numbers] #23919 ******************************************************************************** Bug Fixes ********************************************************************************
1) [Description] Iguana 5.6.1 Installer x64 fixed to install in proper default location [Affected Releases] Iguana 5.6.1 [Tracking Numbers] #23980
2) [Description] Iguana fixed in javascript layer so ToChannel destination tab (and FromChannel source tab) show correct Destinations (Sources). [Affected Releases] Iguana 5.6.1 [Tracking Numbers] #24022
Change log for Iguana 5.6.1 (top)
********************************************************************************
Feature Additions
********************************************************************************
1) [Description]
Added the ability to call queue.push{} multiple times within a message filter.
This facilitates creating more sophisticated workflows including splitting messages
for different destinations while maintaining message reliability.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#17387
2) [Description]
There is a native trace() function added to the Translator that enables the
user to observe the value of the arguments that are passed to the function.
This eliminates the user from having to declare an explicit trace() function
in each module.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#19889
3) [Description]
Added the ability to disable "No sample data" warning when attempting to
open a Translator instance that does not contain any sample messages.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21212
4) [Description]
A setNodeValue method has been added to the NODes API to enable easy
modification of the value of an individual node without the need to navigate
to that node from the parent.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21534
5) [Description]
Added the Channel API which provides the ability to create, update and manage channels through an API. See
http://wiki.interfaceware.com/1473.html for a Lua wrapper script that utilizes the API.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#22799
6) [Description]
Added the ability to connect to an external authentication source. This creates the choice to use the internal
mechanism to store users and passwords or to connect to another system for users and password.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23028
7) [Description]
Added the ability to process multiple HTTP requests concurrently in a single channel.
The feature is configured via the ThreadCount setting in a From HTTPs channel configuration.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23359
8) [Description]
Added the ability to call C/C++ functions in a DLL from Lua.
See http://wiki.interfaceware.com/1468.html for more information.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23459
9) [Description]
Added a Socket Diagnostic page detailing activity by address, port and handle
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#22777
10) [Description]
Added HTTP Basic Authentication to Iguana web request handlers
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#22243
11) [Description]
Added ability to restart built-in web server without restarting Iguana.
Usage: ./iguana --restart_webserver
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23625
********************************************************************************
Changes
********************************************************************************
1) [Description]
The wording of the timing of the filter application was changed to reflect
the use of queues.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21399
2) [Description]
iguana.logInfo can now take strings as a refid parameter.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21814
3) [Description]
Regular Expression search functionality has been removed from the Translator.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21931
4) [Description]
The Translator API functions cache.load() and cache.save() have been
deprecated.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#21189
5) [Description]
The Translator API function queue.push() will coerce its argument to a string if possible, and provide consistent returns.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23377
6) [Description]
The Translator Toolbar buttons feature a grouped set of script Play, Stop and Auto-Play buttons.
Show Empty Nodes in Trees, Show Annotations, Allow Auto-Completion buttons are removed.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#22798
7) [Description]
The Iguana Log Channel [Service Entries] now reports an error message when too many sockets are open.
The message indicates that FD_SETSIZE has been exceeded.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23529
8) [Description]
The Iguana Log Channel [Service Entries] now reports an error message when a socket could not be opened.
The message indicates that the socket connection failed.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23444
9) [Description]
The monitor_query API now reports SocketsOpen and SocketsLimit attributes in the IguanaStatus XML element.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23436
10) [Description]
Openssl is now statically linked which simplifies Iguana deployment.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#22143
11) [Description]
Lua and LuaJIT usage has been updated. Luajit 2.0.2 now used for Linux64.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23246
12) [Description]
Network socket library acceptor logic hardened to make more resistant to port scanning software.
[Affected Releases]
Iguana 5.6.1
[Tracking Numbers]
#23529
******************************************************************************** Bug Fixes ******************************************************************************** 1) [Problem] In some cases, NULLs in SQLite tables would be represented as 0. [Affected Releases] All versions of Iguana [Tracking Numbers] #22669 2) [Problem] Where an HTTP client passed an HTTP Content-Length header in non-conventional letter case the HTTP request would not be processed. Now that specific HTTP request is processed. [Affected Releases] All versions of Iguana [Tracking Numbers] #23595 3) [Problem] The Channel description text box would expand indefinitely on text character addition. Now the text box maintains an appropriate sizing. [Affected Releases] All versions of Iguana [Tracking Numbers] #23181 4) [Problem] The entitlements logic would prevent users with Administrative role from creating shared modules. Now users with Administrative role can create shared modules. [Affected Releases] All versions of Iguana [Tracking Numbers] #23447
Change log for Iguana 5.5.7 (top)
******************************************************************************** Feature Additions ******************************************************************************** 1) [Description] URLs in channel descriptions are now hyperlinked. [Affected Releases] Iguana 5.5.7 [Tracking Numbers] #22928
********************************************************************************
Bug Fixes
********************************************************************************
1) [Problem]
When attempting to access Iguana using Internet Explorer 10 with
Compatibility Mode enabled, the user would be denied access to Iguana with
the following message: "You are using an outdated browser."
[Affected Releases]
All versions of Iguana
[Tracking Numbers]
#23017
2) [Problem]
Adding a self-reference in a built-in module would cause the help system to
stop working.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#22968
3) [Problem]
Declaring a public "node" variable caused Iguana to crash with a
Segmentation Fault.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#22905
4) [Problem]
Overriding the global JSON module would cause Iguana to crash.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#23078
5) [Problem]
Iguana would fail to import sample JSON files containing hexadecimal values
with capital letters.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#23209
6) [Problem]
Certain UTF-8 character sequences in the channel description would cause
the Dashboard to not display anything.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#23316
7) [Problem]
Triggering a regular expression search in the Dashboard using the
forward slash ('/') character would cause Iguana to crash.
[Affected Releases]
Iguana 5.5.5 and above
[Tracking Numbers]
#23338
8) [Problem]
When opening the JSON link in the Annotations of the 4-Channel Demo in
Mozilla Firefox, the browser would download the file instead of displaying
it.
[Affected Releases]
Iguana 5.5.5 and above
[Tracking Numbers]
#22925
9) [Problem]
The Translator would not retain some changes to the first line of a script
when the user switches between multiple scripts within a project.
[Affected Releases]
Iguana 5.0.1 and above
[Tracking Numbers]
#22934
10)[Problem]
In certain scenarios, custom LLP delimiters in LLP Listener components would
not persist; causing the LLP delimiters to revert back to the previously
defined values.
[Affected Releases]
Iguana 5.0.11 and above, Iguana 5.5.1 and above
[Tracking Numbers]
#23393
11)[Problem]
When mapping the datatype "NUMBER" in Oracle with no specified precision or
scale, Iguana would treat it as integer.
[Affected Releases]
Iguana 5.5.1 and above
[Tracking Numbers]
#23419
12)[Problem]
When placing VARBINARY data from SQL Server in to a result set, Iguana would
lose one byte of data for every 4KB chunk of data due to an off-by-one error.
[Affected Releases]
Iguana 5.5.1 and above
[Tracking Numbers]
#23379
13)[Problem]
In cases where Iguana could not detect the proper IP address or hostname, it
would fail to report any information as part of the Monitor Query system.
[Affected Releases]
Iguana 5.5.1 and above.
[Tracking Numbers]
#23403
******************************************************************************** Changes ******************************************************************************** 1) [Description] Updated the node.lua and ran.lua modules that are included with the 4-Channel Demo to be consistent with the version of those modules that is packaged in Iguana. [Affected Releases] Iguana 5.5.7 [Tracking Numbers] #22817 2) [Description] Added improved warnings for Iguana users regarding license and maintenance expiry. [Affected Releases] Iguana 5.5.7 [Tracking Numbers] #22808
Change log 5.5.6 (top)
******************************************************************************** Bug Fixes ******************************************************************************** 1) [Problem] The timeout feature in the LLP component of a channel would not function if no data is transmitted over a connection. [Affected Releases] All versions of Iguana [Status] Fixed in 5.5.6
[Tracking Numbers] #22822 2) [Problem] Iguana would display a bogus error in the Dashboard in rare scenarios involving remote servers. [Affected Releases] Iguana 5.5.5 [Status] Fixed in 5.5.6 [Tracking Numbers] #22826
Change log 5.5.5 (top)
******************************************************************************** Feature Additions ******************************************************************************** 1) [Description] When performing Search/Replace in the Translator, the user can chain multiple replace operations until no more matches are found within the script. [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #21930 2) [Description] URL requests can now be parsed and directed to different 'From HTTP' channels based on a specified pattern. [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #19772 3) [Description] Iguana is now compatible with MySQL 5.6 and 5.7. [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #22575 4) [Description] Iguana is now compatible with Ubuntu Linux running kernel version 3.5. [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #22634 5) [Description] Added four demo channels that demonstrate some of the most common functionalities within Iguana (for first-time users). [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #22628
******************************************************************************** Changes ******************************************************************************** 1) [Description] In the Translator, the highlight colour for errors was changed from red to blue to improve visibility. [Affected Releases] Iguana 5.5.5 [Tracking Numbers] #22597
******************************************************************************** Bug Fixes ******************************************************************************** 1) [Problem] All "Other" files in the Translator displayed an error icon when no actual error existed. [Affected Releases] Iguana 5.5.4 [Status] Fixed in 5.5.5 [Tracking Numbers] #22523 2) [Problem] In rare scenarios involving hardware failure and corrupt filesystems, Iguana crashed when loading corrupt log files. [Affected Releases] All versions of Iguana 4.0 and beyond [Status] Fixed in 5.5.5 [Tracking Numbers] #22522 3) [Problem] Iguana could potentially crash when net.sftp attempted to list many files (2000 or more) from the server. This was caused by a bug in the version of the SSH library that was being used by Iguana. The SSH libraries have been updated to prevent this crash scenario. [Affected Releases] Iguana 5.0.14 and all versions of Iguana 5.5
[Status] Fixed in 5.5.5 [Tracking Numbers] #22467 4) [Problem] In rare cases, the SQL query that is generated for binding mode would not match the query that would effectively be executed against the database. [Affected Releases] All versions of Iguana 5.0 and beyond [Status] Fixed in 5.5.5 [Tracking Numbers] #22404 5) [Problem] Fixed a problem that could cause Iguana to crash when connecting to a database. Would would expect to see pConnection.get() != NULL in the logs. [Affected Releases] Iguana 5.5.4 [Status] Fixed in 5.5.5 [Tracking Numbers] #22715 6) [Problem] The Dashboard would not display any existing channels if the number of channels were equal to the number of channels that can be displayed per page. [Affected Releases] Iguana 5.0.1 and above. [Tracking Numbers] #22247
Change log 5.5.4 (top)
********************************************************************************
Feature Additions
********************************************************************************
1) [Description]
Users can now install Iguana on Microsoft Windows Server 2012 and
Microsoft Windows 8.
[Affected Releases]
Iguana 5.5.4
[Tracking Numbers]
#22303
********************************************************************************
Bug Fixes
********************************************************************************
1) [Problem]
Redefining native functions in the Translator crashes Iguana or causes
auto-completion failure.
[Affected Releases]
All versions of Iguana 5.0
[Status]
Fixed in 5.5.4
[Tracking Numbers]
#21945
2) [Problem]
The queue.push function returns nothing in either annotations or auto-completion.
[Affected Releases]
Iguana 5.5.1, Iguana 5.5.2, and Iguana 5.5.3
[Status]
Fixed in 5.5.4
[Tracking Numbers]
#22276
3) [Problem]
Sometimes, auto-completion does not include all relevant results.
[Affected Releases]
All versions of Iguana 5.0
[Status]
Fixed in 5.5.4
[Tracking Numbers]
#21517
Change log 5.5.3 (top)
********************************************************************************
Bug Fixes
********************************************************************************
1) [Problem]
Iguana crashes intermittently when multiple users access the same Iguana
instance with the same username, and at least one of the users is using
the Translator IDE.
[Affected Releases]
All versions of Iguana 5.0
[Status]
Fixed in 5.5.3
[Tracking Numbers]
#22200
2) [Problem]
A race condition causes Iguana to crash when certain conditions are met
in two instances of the Translator running in two separate channels.
[Affected Releases]
Iguana 5.5.1 and Iguana 5.5.2
[Status]
Fixed in 5.5.3
[Tracking Numbers]
#22273
Change log 5.5.2 (top)
************************************************************************
Feature Additions
************************************************************************
1) [Description]
Addition of syntactic sugar to the following functions:
* queue.push
* net.http.delete
* net.http.get
* net.http.parseRequest
* net.http.respond
* net.http.post
* json.parse
* xml.parse
The user can call these functions with just the required parameter using parentheses instead
of passing a table that is surrounded by curly braces.
[Affected Releases]
Iguana 5.5.2
[Tracking Numbers]
#21330
************************************************************************ Changes ************************************************************************
1) [Description]
Calling the remove function on a collection of tables will no longer remove the table from the collection;
rather it will completely clear the data that has already been mapped into that table.
[Affected Releases]
Iguana 5.5.2
[Tracking Numbers]
#21768
************************************************************************
Bug Fixes
************************************************************************
1) [Description]
The documentation for the date/time functions has been fixed.
[Affected Releases]
Iguana 5.5.2
[Tracking Numbers]
#21770
2) [Description]
In Iguana 5.5.1, db.merge and db.execute functions were live by default. This behaviour has been
fixed in Iguana 5.5.2. The live flag in both db.merge and db.execute is set to false by default.
[Affected Releases]
Iguana 5.5.2
[Tracking Numbers]
#21842
3) [Description]
Fixed an issue where lines in the Translator scripts would disappear when using Internet Explorer 9.
[Affected Releases]
Iguana 5.5.2
[Tracking Numbers]
#21132
Change log 5.5.1 (top)
************************************************************************ Feature Additions ************************************************************************
1) [Description]
The Translator editor now has a powerful, integrated help system, allowing you to view API
documentation, parameter descriptions, etc. while you are putting together your interface
script.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18680
2) [Description]
Any and all configuration errors and warnings are now more prominently displayed within Iguana:
* On the dashboard, the component icon shows a warning or error symbol for any component with
a configuration warning or error.
* In the individual channel control panel, the component icon shows a warning or error symbol for the
component with a configuration warning or error.
* The tooltip on the component icon on both the dashboard and the channel control panel displays the
text associated with the configuration warning or error.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#19392
3) [Description]
When using the Translator component, if you neglect to save a milestone, Iguana will now classify this omission
as a configuration error. Moreover, if you edit a Translator script but do not save the changes under a
milestone, Iguana will now classify this as a configuration warning.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#16994, #18429, ##19392
4) [Description]
Auto-completion now works on variables in the Translator editor.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18808
5) [Description]
When viewing annotations in the Translator editor, loop annotations have been significantly improved.
Instead of displaying annotations for all loop iterations on the same line, an inner annotation block
allows you to view iterations separately.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18344
6) [Description]
When exporting a Translator project to a zip file, you can now include sample messages in the zip file.
Additionally, when importing a Translator project from a zip file that contains sample data,
you have the ability to append the sample data to your current set, replace your current set of sample
data with this new set, or only import the project files without including any of the sample messages.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18279
7) [Description]
There is a new button in the toolbar in the Translator editor that allows you to toggle on and off the
auto-completion feature of the editor. This functionality was added to give more control over when the
script is run in the editor.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18925
8) [Description]
All data in dialogs displaying a 'tree' of information in the Translator editor, such as an HL7 message
or node tree, is now colour-coded for improved readability.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#19478
9) [Description]
While editing a script in the Translator editor, the annotation corresponding to the line you are currently
editing is now highlighted, making it easier to relate the current line to the matching annotation.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#19146
10) [Description]
The workflow for importing a Translator project from a zip file has been improved.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18278, #19198
11) [Description]
LuaCOM is now included with Windows versions of Iguana, allowing users to interact with objects that use
Microsoft's COM specification, such as Microsoft Message Queue, within Translator Lua scripts.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20557, #20718
12) [Description]
A function is provided in "From HTTPS" translator components that will provide information on the
connection details of the incoming request.
Calling net.http.connectionInfo() while in the context of a "From HTTP" channel will return connection
information.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20747
13) [Description]
The ability to drag and drop to reorder tabs (of annotation windows that have been docked)
has been added to Iguana.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18524
14) [Description]
Improvements have been made to the source control diff window. These include:
- The ability to select for copy, one side of the diff when doing a side by side diff.
- Horizontal scrolling of the diff panels to view diffs of wide source code.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20149
15) [Description]
When using any operation in the translator net modules which specify
a debug flag, the following improvements have been made:
- If the flag is true, and an exception occurs during the operation,
the exception will contain debug information.
- If the flag is false, the exception will not contain additional
debug information
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18144
16) [Description]
Exporting a translator project as a zip file now provides the option to
include sample data.
If a project zip file contains sample data, the user can choose to append or replace
existing sample data during an import.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18279
17) [Description]
Iguana's version information is now accessible through the
"iguana.version()" function.
Calling the function returns a table with the major, minor and
build numbers. A string representation can be obtained by calling
tostring with the table.
E.g.
tostring(iguana.version())
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#21108
18) [Description]
Improvements have been made to the sample message browser:
- Adding individual messages through the web interface has been
added.
- It is possible to delete individual or multiple messages.
- Messages can be associated with a name.
- Clicking the row of a message will select it for editing,
previously a small icon had to be clicked.
- The layout of buttons and other UI elements in the sample message
browser has been improved.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#18329
19) [Description]
It is now possible for email notifications to specify a custom URL
for the "Iguana Host Name for Email Links" field, instead of just a
hostname.
For instance, specifying http://externalip:9999 in the field will
make all links use that url as the base url for links. This will
allow the use of external proxy services to reach Iguana resources
from links in notification emails.
If the value in the field does not begin with http:// or https://,
then the previous behaviour is assumed, where the protocol and port
will be derived from Iguana's settings.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#21083
20) [Description]
The function 'unwind_protect' has been added to the translator's
global namespace, which provides the ability to call a cleanup
function if an action function fails due to an error.
See the built in help for unwind_protect for more details.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20790
21) [Description]
When opening multiple dialogs in a Translator editor
consecutively, the dialogs are now tiled in a manner that makes
them accessible.
Previous versions of Iguana would stack the dialogs, obscuring
older dialogs with newer ones.
[Affected Releases]
Iguana 5.5.1
22) [Description]
Iguana now supports the use of LuaCOM on Windows, a DLL that
provides an API to access components exposed through COM
interfaces.
The DLL is available in the installation directory as luacom.dll,
and can be used through the Lua command:
local luacom = require('luacom')
See the documentation for more details.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20557
23)[Description]
When the links for "From HTTPS" Translator channels appear (in
dashboard tool tips, or in configuration screens), it is now
possible to adjust the base URL of those links through an
environment variable.
Set the environment variable IGUANA_CHANNEL_BASE_URL to the desired
value, e.g. 'https://externalip.com:7889/'
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#21152
24)[Description]
New permissions "View Logs" and "Translator IDE" added to Roles.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#21511
25)[Description]
The following date/time functions have been added to the Iguana Translator.
* os.ts.time
* os.ts.date
* os.ts.difftime
* os.ts.gmtime
* os.ts.gmdate
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#20005
26)[Description]
Exposed the following API within the Translator to address common filesystem operations.
* os.fs.abspath
* os.fs.access
* os.fs.chmod
* os.fs.chown
* os.fs.glob
* os.fs.mkdir
* os.fs.rmdir
* os.fs.stat
* os.fs.utime
Refer to the os.fs - file system operations in the Iguana Wiki for further information.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#18944
************************************************************************
Bug Fixes
************************************************************************
1) [Problem]
In previous versions of Iguana, if you synced the Roles and Users
of one Iguana instance with another instance, the changes to the
Iguana configuration file would not be saved immediately, potentially
causing the sync to be lost if Iguana was restarted. In Iguana 5.5.1,
this problem has been resolved: Iguana's configuration file is saved
immediately after syncing Iguana's Roles and Users with another Iguana
instance.
[Workaround]
Make changes to other areas of Iguana's configuration after the sync,
such as adding or deleting a channel; these actions trigger an
automatic save of Iguana's configuration file.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20612, #20614
2) [Problem]
In previous versions of Iguana, it was possible to have a message be
processed by the Destination component of a channel, but not get
marked as 'Processed' in the Iguana logs. This had the potential of
causing that message to be processed more than once by the Destination
component. This has been fixed in Iguana 5.5.1.
[Affected Releases]
All previous versions of Iguana
[Tracking Numbers]
#19672, #19906
3) [Problem]
In previous versions of Iguana, if you configured two LLP Listener
channels to use the same port without configuring the channels for
port sharing, a warning message would appear in the channel
configuration page with a link to the conflicting channel; this link
did not work. This has been fixed in Iguana 5.5.1.
[Affected Releases]
All previous versions of Iguana
[Tracking Numbers]
#20647
4) [Problem]
In previous versions of Iguana 5.0, while in the Translator editor, if
you open a dialog and in the rare case where you click on the "Snap to
Dock" link before the contents of the dialog are fully displayed, a
Javascript error would occur. This has been fixed in Iguana 5.5.1.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20865
5) [Problem]
In previous versions of Iguana, the low-colour skin of Iguana causes
display issues. The low-colour skin has been removed in Iguana 5.5.1.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#19891, #19896
6) [Problem]
In previous versions of Iguana 5.0, when a node with extra whitespace
is displayed in a treeview the extra whitespace is erroneously
removed. This has been fixed in Iguana 5.5.1.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20035
7) [Description]
Executing the SQL statements
SELECT NULL
or
SELECT '';
resulted in the precondition failure:
Error (0)
Failed precondition: !NewColumnName.is_null()
This has been fixed in Iguana 5.5.1
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20308
8) [Problem]
When doing a diff of files in the Translator, files containing
unicode characters outside the ASCII range would result in
corrupted characters being displayed in the diff window.
This has been fixed in Iguana 5.5.1
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#18995
9) [Problem]
Some datatypes were not supported in Iguana for MySQL, SQL Server
and Oracle. Iguana now supports all known data types, with some
exceptions. See details below:
MySQL
* MySQL now supports binary types (in Translator, and only when
the MySQL library is v5.0 or better). String values are still
terminated by their first NUL character (to avoid possible
backward compatibility issues). Binary data can contain NUL
characters, which are now escaped correctly in generated SQL.
* Binary values are returned as strings when binary support is not
available (e.g. using Chameleon based channel components).
Consequently they are truncated at their first NUL character.
This is for backward compatibility.
* TIME values are returned as strings.
* YEAR values are returned as integers.
* BIT values are supported, and returned as binary data.
* MySQL no longer disconnects on every error, only when connection
errors occur.
* When inserting/updating values without bindings with ODBC (e.g.,
when unicode is enabled, or when executing raw SQL in
Translator) the database is queried to determine if any string
values need to be converted to binary values first. This works
on Windows only; it does not work with unixODBC/FreeTDS.
SQL Server
* 'timestamp' is not currently supported.
* 'sql_variant' is not currently supported, since mixed-type
columns are not supported.
* 'date', 'datetime2', 'datetimeoffset', 'hierarchyid', 'time',
and 'xml' are not currently supported.
Oracle ODBC
* 'bfile', 'timestamp with time zone', 'timestamp with local time
zone', interval day to second', 'interval year to month',
'XmlType', and 'UriType' are not supported.
* Fixed issue where column names may not appear correctly.
* NUMERIC bindings now consider their columns' digit count and
precision. Previously NUMERIC binding only worked when the
precision was zero.
* NUMERIC data is now returned as double values, instead of
integers; NUMERIC(*,0) values are still returned as integers for
Oracle.
* Binary data can now be bound from internal strings, allowing
users to use db.merge to merge binary data into their database.
Oracle OCI
* 'bfile','XmlType','UriType' are not supported.
* The following support has been added:
* Binary types (BLOB, RAW, LONG RAW)
* Additional string types (LONG, CHAR, NCHAR, ROWID)
* Timestamps with time zone information (but time zone
information will not be available in Iguana)
* Floating point types (BINARY_FLOAT, BINARY_DOUBLE).
* Time interval types (INTERVAL DAY TO SECOND and INTERVAL YEAR
TO MONTH).
* Corrected how NUMBER types were handled. Previously they were
converted to integers. Now only NUMBER(?,0) values are treated
as integers.
* Fixed an issue where an OCI fetch error would leave some
internal state corrupt for the next fetch attempt.
[Affected Releases]
All previous versions of Iguana
[Tracking Numbers]
#20229
10)[Problem]
Some versions of Cerberus FTP server software contain a bug in its
SFTP implementation that results in being unable to determine if a
remote file exists, if the file does not actually exist.
This results in being unable to upload files with either the
'Iguana To File' component, or the translator net.sftp.put function.
The bug should be fixed in newer versions of Cerberus. However,
changes have been added to Iguana to allow for uploads if this bug
is present, as long as the overwrite setting is set to true.
[Workaround]
Upgrade Cerberus.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#21325
11)[Problem]
In previous versions of Iguana, if a project zip file was uploaded,
and Iguana did not delete the zip file after importing it (due to a
crash or some other issue), subsequent importing of a zip file with
the same name would not work.
The user would see the error indicating that the file already
exists.
This has been fixed by always overwriting the existing file in
Iguana after uploading, before doing the import.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20950
12)[Problem]
It is possible to get an error in the Translator editor where the
annotations do not display the same state that corresponds to the
error.
An example would be, if an error was raised in the 3rd iteration of
a function call, the annotations may only display data from the
first iteration.
This has been fixed, by moving the annotations (and re-executing
the script if needed) to the correct iteration (if required), when an
error occurs.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20333
13)[Problem]
If an invalid project zip file was imported into the Translator
editor, no error would be raised. This can be confusing to the user
since no indication of error was made.
This has been fixed to raise an "invalid file" error if the zip
file being imported is not of the correct format expected by Iguana.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#20894
14)[Problem]
Very long user and role names would distort various pages in Iguana's
user interface.
This has been fixed by wrapping/truncating these names, and only
allowing names for new users/roles that are at maximum, 30 characters in
length.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#19439
15)[Problem]
When a user logs out of Iguana, threads that are executing
Translator editor tasks (such as annotations, or autocompletion)
did not stop and release their resources.
This could result in:
- Memory usage increasing over time as more users and translator
instances are added.
- Resources held by the translator instances (such as database
connections, network connections, etc) would never be
released.
This has been fixed, so when a user logs out, all translator editor
threads that the user was using (across all sessions for that same
user) are stopped, and their resources released.
Any open translator windows for a user (for sessions that were not
logged out) will require a refresh in order to restart the required
thread(s). A warning will appear in the translator editor to
indicate that this refresh is required.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#21274
16)[Problem]
When a block of code greater than 5 lines is pasted into the
Translator editor, the code would not be correctly colourized.
This has been fixed to ensure pasting in code blocks of any size
will result in correct colourization.
[Affected Releases]
All versions of Iguana 5.0
[Tracking Numbers]
#21225
17)[Problem]
When multiple channels exist with names that only differ by case
(e.g. MyChannel and mychannel), a precondition failure could occur
when removing one of the channels. This has been fixed.
[Affected Releases]
Iguana 5.0.14 and earlier
[Tracking Numbers]
#21151
18)[Problem]
When using protocols other than HTTP in translator
(e.g. net.sftp,net.ftp), it was possible to get an access violation
to occur due to a cached connection handle.
This issue is covered in detail here:
http://sourceforge.net/tracker/?func=detail&aid=3544688&group_id=976&atid=100976
The fix has been included in Iguana 5.5 and higher.
[Affected Releases]
All releases of Iguana 5.0
[Tracking Numbers]
#20904
19) [Problem]
The ordering of arguments for os.difftime did not correctly reflect the Lua
implementation of os.difftime. We have resolved this by changing
os.difftime(t1, t2) to os.difftime(t2, t1).
[Affected Releases]
Iguana 5.0.3 through 5.0.14
[Status]
Fixed in 5.5.1
[Tracking Numbers]
#17871, #20005, #21107
***********************************************************************
Changes
************************************************************************
1) [Description]
Iguana 5.5 of Iguana for Windows is built and shipped with
the latest version of OpenSSL, which is 1.0.0g. [Affected Releases] Iguana 5.5.1
[Tracking Numbers]
#19971
2) Iguana versions before 5.5.1 would execute translator code once per change in the code,
once per open dialog/tab, and once everytime the view mode changed within a dialog.
This could result in the inconsistent output between all dialog windows and annotation blocks.
In addition, scripts would execute multiple times under different conditions, resulting in unexpected behaviour,
especially if external resources are being affected (e.g. database tables).
Iguana 5.5.1 will now only execute the script once per change in the Lua code, regardless of the number of
open dialogs/tabs, and changing the view mode in open dialogs.
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#19736,#19770
3) [Description]
In previous versions of Iguana and Chameleon, if a large message is parsed with a VMD that is
configured to 'Disregard Segment Order', such as when parsing a large X12 message, parsing may
take a long time.
The underlying parsing algorithm has been significantly improved to reduce parsing time
in Iguana 5.0.15 and Chameleon 5.4.15.
[Affected Releases]
All versions of Iguana 4.5 and earlier
Iguana 5.0.1 through Iguana 5.0.14
All versions of Chameleon 5.3 and earlier
Chameleon 5.4.1 through 5.4.14
[Tracking Numbers]
#19965, #19976
4) [Description]
In order to provide help for the values contained within
iguana.project, the values have been converted to functions, which
return the same contents as the previous interface.
For instance
local value = iguana.project.guid
should be replaced with
local value = iguana.project.guid()
[Affected Releases]
All previous versions of Iguana
[Tracking Numbers]
#21251
4) [Description]
To streamline the usability of menu items in the translator, some
menu items in the project window have been combined.
The functionality of "Import from Other Projects", and "Import
Project from Zip File" in older versions can be accessed through
the "Import" menu item.
The "Download Project as Zip File" menu item has been renamed to
"Export".
[Affected Releases]
Iguana 5.5.1
[Tracking Numbers]
#21244
Change log for Iguana 5.0.14 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] For some customers that make extremely heavy use of Python in their VMDs, it has been observed that performance issues could occur. This is due to multiple channels being in contention for the Python 'global interpreter lock'. For customers facing this problem an optional switch has been added to Iguana 5.0 to allow parse execution to be serialized across all the channels in an Iguana instance. In some cases this can significantly improve performance. To use this lock, set the IGUANA_USE_PARSE_MESSAGE_LOCK environment variable to "yes" (without the quotes) and restart at least one channel whose destination component is To Database. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #16618, #20441, #20443 2) [Description] Iguana 5.0.14 no longer has a restriction on the number of times db.merge() can be called in a Translator script. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20217 3) [Description] isKey() has been added to the Translator API for table nodes. isKey() allows you to check if a column is a primary key for that table. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20338 4) [Description] db.close() has been added to the Translator API to allow explicit closing of database connections. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20099, #20241 5) [Description] Node values, such as HL7 segments or fields, or XML elements, can now be used as keys in Lua tables in Translator scripts. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20130 6) [Description] Iguana 5.0.14 allows you to call require() anywhere in a Translator script. Previous versions of Iguana 5.0 only allowed calling require() at the top level of your Translator script. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20282 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In previous versions of Iguana 5.0, when interacting with a database using a Translator script, database nodes with values of zero '0' or an empty string '' were incorrectly considered null. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20229, #20237 2) [Problem] In previous versions of Iguana, when using the Translator API to transfer files to or from an FTP, SFTP, or FTPS server, attempting to use the 'active' parameter would result in an 'unable to connect to server' error. This has been fixed in Iguana 5.0.14. The help text for the 'active' parameter has been improved to clarify the proper syntax for specifying ports, etc. [Affected Releases] Iguana 5.0.4 through 5.0.13 [Tracking Numbers] #20524, #20559 3) [Problem] In Iguana 5.0.10 and later, when using hl7.parse() in a Translator script, non-standard delimiters explicitly defined in the VMD file were ignored when parsing escaped values, and non-standard delimiters present in a message were being ignored when parsing escaped values. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.10 through 5.0.13 [Tracking Numbers] #20412, #20484 4) [Problem] Internal testing of Iguana revealed that when there were multiple channels using SSL to connect to external systems, and all these channels were attempting to make their connections in parallel, there was the possibility that Iguana would crash due to some of the data in libssh2 being improperly shared between threads. This issue was resolved in version 1.4.0 of libssh2; version 1.4.0 of libssh2 is included in Iguana 5.0.14. [Affected Releases] All previous versions of Iguana [Tracking Numbers] #18114 5) [Problem] Internal testing of Iguana revealed that when Iguana is running on a machine under heavy load and a task was being performed on it's main thread, if the session timed out while the task was being completed, upon logging back into Iguana there was the possibility of Iguana crashing. This has been fixed in Iguana 5.0.14. [Affected Releases] All versions of Iguana 4.0 All versions of Iguana 4.5 Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20520 6) [Problem] In previous versions of Iguana 5.0, when using a Translator script to create XML nodes and merge them into an existing XML node tree, there was the possibility that XML tags would become corrupted. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20562 7) [Problem] When using a Translator script, when a channel is running, Iguana checks out the script into a sandbox directory under the "run" subdirectory of Iguana's working directory. When the channel is stopped, Iguana deletes this sandbox directory. In previous versions of Iguana 5.0, while using a Translator script in a From HTTPS channel, a To Translator channel, or a From Translator channel, if Iguana failed to remove the sandbox directory for that channel when the channel was stopping, the channel would fail to completely stop, and become stuck in the 'stopping' state. This has been fixed in Iguana 5.0.14. When Iguana cannot remove the sandbox directory, a warning message will be logged, and the channel will stop properly. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20205 8) [Problem] In previous versions of Iguana 5.0, if you downloaded a Translator project to a zip file under Windows, if you attempted to unzip this file on a non-Windows machine, the directory structure of the project would not be properly maintained. This problem existed only when opening the Translator project zip file with an external application; importing the zip file into any other Iguana channel, regardless of platform, always worked. This issue has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20100 9) [Problem] In previous versions of Iguana 5.0, while editing a Translator script if you added a file to the workspace, your script would not automatically get recompiled, and annotations would not be be updated. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20206 10) [Problem] In previous versions of Iguana, while editing a Translator script, if one of the modules was modified externally Iguana would correctly detect the external modification, but upon reloading the module, the Translator script would not automatically be recompiled, which may have resulted in annotations containing stale information. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.1 through 5.0.13 [Tracking Numbers] #20339 11) [Problem] In Iguana 5.0.13, while using a Translator script, if there was no main() function in your script, or when using a Translator script with the From HTTPS component and you had neglected to call net.http.respond() in your script, Iguana would report an error similar to 'Could not load file. File "C:Program FilesiNTERFACEWAREIguanaeditadminshared.lua" does not exist.' Once this error was dismissed, the error reporting the actual problem, i.e., the lack of a main() function, or the lack of a call to net.http.respond() in a From HTTPS Translator script, would appear. This has been fixed in Iguana 5.0.14 such that you only see the error about either the main() function being absent, or the lack of calling net.http.respond() in a From HTTPS Translator script. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #20127 12) [Problem] In previous versions of Iguana 5.0, while using Internet Explorer version 8 or 9, if you were redirected to Iguana's login page because your session had timed out, or you had been logged out, when you logged in Iguana would report an error about no page being specified instead of bringing you to the page you were last viewing. This has been fixed in Iguana 5.0.14. [Affected Releases] Iguana 5.0.9 through Iguana 5.0.13 [Tracking Numbers] #19547 ************************************************************************ Changes ************************************************************************ 1) [Description] In previous versions of Iguana, when the LLP Listener component encountered a socket error, the specifics of the error message would not be reported in the logs. Iguana would log a debug message stating something similar to "Error on active connection from 10.244.75.11. Treating error as close operation." This behaviour has been changed in Iguana 5.0.14 such that a debug message is logged with the specifics of the socket error message to aid in troubleshooting connectivity issues with external software. [Affected Releases] Iguana 5.0.14 [Tracking Numbers] #20571, #20260 ************************************************************************ Known Issues ************************************************************************ 1) [Description] The 256 colour skin in Iguana causes display issues. [Workaround] Use the default colour skin. [Affected Releases] All versions of Iguana 5.0 [Tracking Numbers] #19891, #19896
Change log for Iguana 5.0.13 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] In Iguana 5.0.13, optimizations have been made to the backend to improve the performance and responsiveness of the Translator editor when using large sample messages. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #19869 2) [Description] In Iguana 5.0.13 and Chameleon 5.4.13, extensive optimizations have been made to reduce memory usage and fragmentation when Python is utilized within VMD files in both Chameleon and Iguana. [Affected Releases] Iguana 5.0.13 Chameleon 5.4.13 [Tracking Numbers] #18496, #18639 3) [Description] In Iguana 5.0.13, the rendering of XML in annotations in the Translator has been significantly optimized to improve performance. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #19864 4) [Description] iguana.project has been added to the Translator API. This gives programmatic access to information about the files in a Translator project. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #19885 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In Iguana 4.1.13, changes were introduced so that if external software locked Iguana's log files while Iguana was attempting to access them, Iguana would reattempt accessing the log files for 30 seconds instead of immediately going into a panic state and stopping all channels. In Iguana 4.1.23, 4.5.7, and 5.0.9 the retry period was extended to 30 minutes to further accomodate enterprise environments where it may be difficult to to adhere to the recommended best practice of omitting Iguana's log files from back-ups. Despite these changes, there were still some circumstances where Iguana would immediately go into a panic state when back-up software locked it's log files. This has been fixed in Iguana 4.1.24, Iguana 4.5.8, and Iguana 5.0.13. [Affected Releases] Iguana 4.0, Iguana 4.1.1 through 4.1.23, Iguana 4.5.1 through 4.5.7, Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19924, #19930 2) [Problem] In previous versions of Iguana 5.0, while using a Translator script for ACKnowlegment generation in the LLP Listener component, if you used queue.push() the Translator would not report that this API function is unavailable in this context. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.2 through 5.0.12 [Tracking Numbers] #19916, #19920 3) [Problem] In previous versions of Iguana 5.0, when using :setInner() in a Translator script, if the name of the element whose content is being set is longer than 11 characters, the contents of the element in the XML document may end up corrupted. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.7 through 5.0.12 [Tracking Numbers] #19923, #19927 4) [Problem] In previous versions of Iguana, when using SFTP to fetch files from an FTP server in either the From File component or in a Translator script, if the FTP server software was VanDyke VShell Secure Shell Server, Iguana would not fetch any files. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 4.5, Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19722, #20016, #20026 5) [Problem] In previous versions of Iguana, if you were connecting to an Oracle database, the OCI Data Type 187 (TIMESTAMP) was not supported. OCI Data Type 187 (TIMESTAMP) is now supported in Iguana 5.0.13. [Workaround] Cast the column to a different supported data type, such as DATE. [Affected Releases] All previous versions of Iguana [Tracking Numbers] #20034, #20095 6) [Problem] In previous versions of Iguana 5.0, if you were to compare two identical node trees for equality, the Translator would always report them as not equal. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #20130 7) [Problem] In previous versions of Iguana, when using the Windows ODBC driver to interact with a database, when an ODBC connection is closed, statement handles could be freed in an improper order causing Iguana to crash. [Affected Releases] All previous versions of Iguana [Tracking Numbers] #19879, #19899 8) [Problem] In previous versions of Iguana, when fetching files from a FTP, SFTP, or FTPS server, if the timestamp of the file was within the Daylight Savings Time range, when Iguana fetched the file, the timestamp of the file that Iguana created when saving the file would be off by one hour. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 4.5 Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #15091, #20026 9) [Problem] In Iguana 5.0.11 and 5.0.12, if you exported message(s) from the logs to a Translator channel, when you followed the "View message(s) in the Translator Editor" link, Iguana would not automatically select the first exported message as the sample data to use for annotations in the Translator editor. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.11 and 5.0.12 [Tracking Numbers] #19807 10) [Problem] In previous versions of Iguana, if you created any of the following with accented characters, Iguana would not display the accented characters correctly: * channel name * channel description * user names * role names [Affected Releases] All previous versions of Iguana [Tracking Numbers] #19539 11) [Problem] In previous versions of Iguana 5.0, if you created or added a module that had a space in it's name the module would always be marked as "new" even after saving a milestone. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19928 12) [Problem] In previous versions of Iguana 5.0, if you imported a project from a zip file into a Translator instance, you would not be able to view or edit any modules that are included in the project, but are not explicitly 'require'd in the main Lua script. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.5 through 5.0.12 [Tracking Numbers] #19137, #19197 13) [Problem] In previous versions of Iguana 5.0, while using the Translator component, if you attempted to call the built-in Lua error() function with an argument that was a non-string object, the Translator would call the object's __tostring() metamethod. If that metamethod was not defined, then no error was raised. Additionally, if you passed an empty string to the error() function, no error was raised. This has been fixed in Iguana 5.0.13 such the Translator will use the return value from lua_pcall() to determine if there was an error, and report it accordingly. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19836 14) [Problem] In previous versions of Iguana, if you are viewing a message in the log browser where you have the option of viewing the message in Table View mode, if you leave the message displayed for longer than 5 minutes, Iguana may have crashed if activity was resumed in this mode (for example, if you chose to view a different table in the Graphical Table View mode when there is more than one table to choose from). This has been fixed in Iguana 4.5.8, and Iguana 5.0.13. [Affected Releases] Iguana 4.5.1 through 4.5.7, Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19090, #19839 15) [Problem] In previous versions of Iguana 5.0, if you attempted to serialize a table that contains a function entry with json.serialize() Iguana would crash. This has been fixed in Iguana 5.0.13; Iguana will now report an error message. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19917 16) [Problem] In previous versions of Iguana 5.0, if you unzipped a Translator project that was downloaded from Iguana as a zip file, and then zipped it back up with an external zip tool such as WinRAR, or if you attempted to create your own Translator zip file outside of Iguana, when you attempt to import this zip file into Iguana, it would fail to import the project properly. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.1 through Iguana 5.0.12 [Tracking Numbers] #20015 17) [Problem] In previous versions of Iguana 5.0, if you created a module called 'main.lua' directly in the /edit/<user>/shared subdirectory off of Iguana's working directory, when in the Translator editor you would be able to add this module to a Translator project by adding a module to the 'shared' directory and choosing to 'select an existing module'. Because of the name of the module, this would then cause issues when attempting to switch between this module and the main Lua script in the Translator project. This has been fixed in Iguana 5.0.13 such that any modules in the shared directory named 'main' will be excluded from the list of existing modules. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19565 18) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if your code used nested functions and you edited the outer function in a manner that increased the line length causing the annotations to move to the right out of your way, only the annotations for the outer function moved, while the annotations for the inner function did not move. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19815 19) [Problem] In previous versions of Iguana 5.0, while using a Translator script, if you encountered an SSL error, the error would not always be displayed in the Translator editor. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #19602 20) [Problem] In previous versions of Iguana 5.0, while editing a Translator script when using Microsoft Internet Explorer 9, when autocompletion was triggered the editor screen would automatically scroll all the way up, and would continue to scroll up and down erratically as more characters were typed. This was a purely visual issue, and did not affect the functionality of the autocompletion feature in any way. This has been fixed in Iguana 5.0.13. [Affected Releases] Iguana 5.0.9 through 5.0.12 [Tracking Numbers] #19820 21) [Problem] In previous versions of Iguana 5.0, while Iguana is running, if you overrode the settings for the fossil executable that is used by Iguana to change which program is used to perform diffs, if you then attempted to perform a diff in the Iguana Translator UI, Iguana would hang. In Iguana 5.0.13, Iguana will reset the settings of the fossil executable prior to performing a diff so that Iguana will no longer hang. It is not recommended best practice to override the settings of the fossil executable that ships with Iguana. [Affected Releases] Iguana 5.0.1 through 5.0.12 [Tracking Numbers] #20023 22) [Problem] In Chameleon 5.3.2, Interbase was mistakenly removed from the list of databases in the DB tab of the Options window in the Chameleon GUI. Interbase is again available as a database in the DB tab of the Options window in Chameleon 5.4.13. [Affected Releases] Chameleon 5.3.2 through 5.4.12 [Tracking Numbers] #19881 ************************************************************************ Changes ************************************************************************ 1) [Description] In previous versions of Iguana 5.0, when viewing a node tree in the annotations in the Translator editor, the icon displayed next to a character field showed '[T]'. This has been changed in Iguana 5.0.13 to show '[""]'. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #20003 2) [Description] In previous versions of Iguana 5.0, while in the Translator editor, if you attempted to navigate a call-stack into a function for which the Translator cannot show the source you would get no feedback. In Iguana 5.0.13, you will now get a meaningful warning dialog indicating the source is unavailable for viewing. [Affected Releases] Iguana 5.0.13 [Tracking Numbers] #19602
Change log for Iguana 5.0.12 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] iguana.logError() has been added to the Translator API allowing you to log your own custom error messages in a Translator script. This functionality was added to complement the existing ability to add custom info, debug, and warning messages in a Translator script. These error logs are in addition to any error logs that the Translator automatically generates when there is an error in a running script. [Affected Releases] Iguana 5.0.12 [Tracking Numbers] #19111 *********************************************************************** Bug Fixes ************************************************************************ 1) [Problem] In previous versions of Iguana 5.0, while using the Translator component under Microsoft Windows, if you passed an invalid parameter to io.open() in your script, Microsoft's C Runtime would crash Iguana. This was a problem only under Microsoft Windows. This has been fixed in Iguana 5.0.11. [Affected Releases] Iguana 5.0 [Tracking Numbers] #19604 ************************************************************************ Changes ************************************************************************ 1) [Description] In Iguana 5.0.10, while editing a Translator script, any strings that were shown in the annotations were truncated at 32 characters. This has been changed in Iguana 5.0.11 to truncate after 90 characters so that it is easier to see meaningful contents of a string in the annotations without having to open the string in a separate dialog. [Affected Releases] Iguana 5.0.11 [Tracking Numbers] #19805
Change log for Iguana 5.0.11 (top)
************************************************************************
Feature Additions
************************************************************************
1) [Description]
The hl7.parse() function in the Iguana Translator API now returns an additional table containing a
list of all parse warnings for a particular sample message. Examples of parse warnings include
missing segments, missing required fields, etc.
This information is provided to make it easier to detect and systematically handle messages that
do not conform to an expected message grammar as defined in a VMD file.
These parse warnings correspond to the parse errors and warnings that would appear in the Chameleon
GUI if you were to use the same sample message and VMD file within Chameleon.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#16386
2) [Description]
In previous versions of Iguana, during startup if Iguana detected corruption in any of it's index or
meta log files, Iguana would abort it's startup sequence, report the corruption, and indicate which
file(s) needed to be moved out of the way to recover from the corruption before restarting Iguana.
In Iguana 4.1.23, 4.5.7, and 5.0.11, Iguana has been enhanced such that it will now attempt to
automatically move the corrupted files out of the way during it's startup sequence in an attempt to
recover from the corruption.
Iguana will report the corruption recovery as a Service Error in Iguana's logs upon successful startup,
as well as in it's ServiceErrorLog.txt file located in Iguana's working directory.
[Affected Releases]
Iguana 4.1.23,
Iguana 4.5.7,
Iguana 5.0.11
[Tracking Numbers]
#19657
3) [Description]
In Iguana 5.0.11, while interacting with a database in the Translator component, you can now
manually create and control transactions using the following functions:
* db.begin()
* db.commit()
* db.rollback()
These functions were added to be able to handle transactions when interacting with a database such
as Oracle that does not allow control of transactions through its SQL interface.
See the help for each function for usage specifics.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19720, #19730
4) [Description]
The Iguana Translator API now includes a set of functions that allows encoding and decoding of
data using uuencoding, namely filter.uuencode.enc() and filter.uuencode.dec().
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19588
5) [Description]
The LLP delimiters for the LLP Client component can now be customized to handle sending messages
to systems that use non-standard delimiters.
[Affected Versions]
Iguana 5.0.11
[Tracking Numbers]
#19507, #19522
6) [Description]
While editing a Translator script, you can now "get" and "replace" individual Lua files, making
it easier to share individual Lua files between Iguana channels.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19492
7) [Description]
In previous versions of Iguana 5.0, while using the Translator component, if you
attempted to index with or concatenate with bad value types (nil, a function, a table, etc)
you would get an error message of the form ""bad argument #n in '?'".
These types of error messages have been improved in Iguana 5.0.11 to give you better information
to determine the source of the error.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19382
8) [Description]
The net.smtp.send() function in the Iguana Translator API now no longer requires you to supply a
username and password. If you omit both parameters, or set both to empty strings, authentication
will not be used when sending the email message, allowing you to interface with SMTP servers that do
not make use of authentication.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19347, #19646
9) [Description]
The net.smtp.send() function in the Iguana Translator API now appends debug output to error messages to
make it easier to diagnose the source of the error.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19646, #19695
10) [Description]
All functions in the net.http namespace in the Translator API now include parameters to allow control
over how headers are handled.
When receiving response headers you can now specify how multiple values per key are handled.
When sending headers, functions now support taking a list of strings to support sending headers with
multiple values per key.
See the help for each function for specifics.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19645
11) [Description]
When editing scripts in the Translator editor, auto-completion functionality has been enhanced to make
it easier to select options in the list of possible matches using your keyboard.
Now, in addition to using the mouse or arrow keys, you can use the Tab key to move down the list, and
Shift+Tab to move up the list.
Additionally, once you have selected which option you want, if you hit Enter or the space bar, or type
a period ".", a colon ":", an equals sign "=", a comma "," or a bracket "{", "(", "[", "}", ")", or "]",
the selected option will be inserted into your script.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19488, #19677
12) [Description]
Optimizations have been made to Iguana's backend to improve the performance of auto-completion.
These optimizations are most noticeable when auto-completion is triggered on a single character
or set of characters that matches a large number of possibilities.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19578
13) [Description]
When editing scripts in the Translator editor, strings are now truncated after 32 characters
to make annotations easier to view in the editor.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19469
14) [Description]
When editing scripts in the Translator editor, which sample message you are currently using
against your script used to be tracked via a browser cookie. This information is now stored on the
Iguana server in order to reduce the network footprint of Iguana.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#18207
15) [Description]
When editing scripts in the Translator editor, when you switch between different Lua files in the
editor, cursor position is now maintained.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#18918
16) [Description]
Several improvements have been made to the dialogs in the Translator script editor:
* In both the File History dialog and the Saved Milestones dialog, there is now the ability
to diff the current version of the script against the original version of the script, and
also to diff the current version of the script against the previous version of the script.
* While saving a milestone, the text field where you enter the milestone name will now
auto-expand as needed.
* When using a long milestone name, the File History dialog will scale the milestone column
appropriately.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#18369, #18825, #18902
17) [Description]
While editing a Translator script, when auto-completion is triggered on a table or a repeated
object that has no rows or repeats, the suggestions will now include a table row or a repeat
of a group/segment/field, thus improving the auto-completion suggestions for these specific scenarios.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#18535
***********************************************************************
Bug Fixes
************************************************************************
1) [Problem]
In previous versions of Iguana 5.0, while using a Translator script to manipulate table
data, when you removed some columns from a table row after you had already mapped data
into other columns in the same row, in some circumstances you could get either a
precondition error or the column names of the table would get altered incorrectly,
resulting in the channel not running properly.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19519, #19558
2) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if a milestone was
created with unprintable characters, such as a tab character, you would not be able to edit
or run the channel.
This has been fixed in Iguana 5.0.11.
[Workaround]
Edit the fossil repository directly and remove the unprintable characters from the milestone
name. Contact us for more information on how to edit your fossil repository.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19576, #19582
3) [Problem]
In previous versions of Iguana, when configuring the To File component, when the component
was configured to write out separate files using a custom timestamp file mask, the
extension of the file was always changed to .hl7 regardless of how you initially
configured it.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
Iguana 4.5
[Tracking Numbers]
#19457
4) [Problem]
In Iguana 5.0.10, if you installed Iguana with the automatic Windows installer, or upgraded
an existing Iguana installation, when you first logged into Iguana you would be notified that
Iguana 5.0.10 was now available.
The new version notification feature has been modified in Iguana 5.0.11 to only notify about newer
versions.
[Affected Releases]
Iguana 5.0.10
[Tracking Numbers]
#19504
5) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if you had an item with a
metatable and a __tostring() function, and the __tostring() function calls a C function such as print(),
a stack overflow would occur in the annotations, preventing the script from running.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19515
6) [Problem]
In Iguana 5.0.7 and later, while editing a Translator script, if your script contained an
error and you navigated the error call-stack, when you navigated to a function that was in a module
other than the one you were currently viewing, the editor would switch to the correct module,
but the line you navigated to was not highlighted to show you where the call originated.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0.7 and later
[Tracking Numbers]
#19659
7) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if your script contained an
error, when you clicked on the link to bring you to the error location, it would not always bring you
to the correct iteration if the function that contained the error had multiple iterations.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19658
8) [Problem]
In previous versions of Iguana, under certain circumstances net.smtp.send() would erroneously fail
with the error "Failure when receiving data from the peer".
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0.2 and later
[Tracking Numbers]
#19646, #19694
9) [Problem]
In previous versions of Iguana 5.0, when using functions in the net.http namespace of the Translator
API, if redirects were followed during a fetch, the returned headers may be incorrect since all the
values for each response during the redirects would be merged together.
In Iguana 5.0.11, this has been changed to correctly use the values only for the last response when
using the "default" and "multiple" options for the new "response_headers_format" parameter.
[Affected Releases]
Iguana 5.0.2 through 5.0.10
[Tracking Numbers]
#19645
10) [Problem]
In previous versions of Iguana 5.0, when editing a Translator script, if you performed a diff of
a Lua script against any other version of the same script, if the last line of the script did not
end with a newline it would not be displayed in the diff.
This was a superficial display problem, and has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19682
11) [Problem]
In Iguana 5.0.8 and later, if you logged in as a user that had edit permissions on a
Translator channel but was not an Administrator, when editing the Translator script
you would erroneously be informed that you did not have sufficient permissions to edit
the script.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0.8 through 5.0.10
[Tracking Numbers]
#19517
12) [Problem]
In previous versions of Iguana 5.0, when editing a script in the Translator editor,
if you had typed some text that triggered auto-completion, when you deleted some of
your text in some circumstances the auto-completion would stop providing suggestions.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19493
13) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if you added a
Lua module that had the Lua path separator character (period ".") in it's name, when you
tried to add this module to a different project, it would show up in the Add Module list
with a slash in place of the period, resulting in some visual inconsistency in the editor.
Also, if you added a module with a period in it's name to one project, you would not have
been able to see this module in another project unless you first saved the module under
a milestone.
Iguana 5.0.11 consistently uses the period as the path separator throughout the editor,
and modules that contain a path separator no longer need to be saved under a milestone
to become visible to other projects.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19462
14) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if you turned off
annotations in the editor then proceeded to make changes to your script, if you turned
the annotations back on the contents of the annotations would be out-of-date.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19435
15) [Problem]
In previous versions of Iguana 5.0, while editing a Translator script, if you changed
the zoom level of the browser, under some browsers the annotation blocks would become
misaligned and in some cases overlap code.
This has been fixed in Iguana 5.0.11.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#19455
************************************************************************
Changes
************************************************************************
1) [Description]
While editing a Translator script, you can now no longer read from STDIN.
[Affected Releases]
Iguana 5.0.11
[Tracking Numbers]
#19552
Change log for Iguana 5.0.10 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] Iguana will now inform you when a new version is available for download. When you first connect to Iguana, you will be notified on the login page of the new version. This notification is also displayed on the dashboard. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #18113 2) [Description] You can now configure the To Database component to retry on specific non-fatal database errors. A new configuration option is available in the To Database component that allows you to specify the text of the non-fatal database error, and how often to retry when that error happens. This feature has been added to Iguana 4.1.23, 4.5.7, and 5.0.11. [Affected Releases] Iguana 4.1.23, Iguana 4.5.7, Iguana 5.0.10 [Tracking Numbers] #15045 3) [Description] node:isLeaf() is now part of the Lua API for Translator scripts. This function allows you to determine if a particular node has any children. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #19249 4) [Description] In Iguana 5.0.10, changes were made to Iguana's back-end to optimize memory usage when using the Translator component with very large messages. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #18326, #18815, #18863 5) [Description] When editing a Translator script, when viewing a HL7 message in it's node tree view, any segment groups, segments, or fields that repeat now show you exactly how many repeats there are in the message you are currently viewing. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #18095 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In Iguana 5.0.9, while editing a Translator script, if you attempted to add a file to your project when using Internet Explorer, depending on the security settings in the browser in some circumstances adding the file would fail with the error "Dependency name contains invalid character(s)." This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19329 2) [Problem] In previous versions of Chameleon, when using Microsoft Windows, the HL7 Listener and HL7 Simulator tools would under certain circumstances become unusable if you customized your desktop font size. This has been fixed in Chameleon 5.4.10. [Affected Releases] All previous versions of Chameleon [Tracking Numbers] #19172 3) [Problem] In Iguana 5.0.9 changes were introduced to the From HTTP(S) component to display the full URL path when using the Translator as part of this component. If you were using the Global Dashboard to view a channel on a remote Iguana that used the Translator as part of the From HTTP(S) component, the full URL path in the component tooltip would incorrectly show the URL as "localhost" instead of the name of the remote machine. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19268 4) [Problem] In Iguana 5.0.9, while editing a Translator script, if you attempted to export the database tables for a VMD file that is part of your project, the "Export Tables" dialog was too small and could not be resized to comfortably view the contents. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19203 5) [Problem] In Iguana 4.5.1 and later, if there was a message that contained a very long single line of text that happened to contain a large number of reserved HTML characters, in some circumstances there was the possibility that when viewing this individual message in Iguana's log browser, the message would not appear at all. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 4.5.1 and later [Tracking Numbers] #19189 6) [Problem] In Iguana 5.0.9, while editing a Translator script, when you performed a diff of a Lua file with the previous version of the file, the "Generating diff for main ..." dialog that appears prior to viewing the diff would never close. The only way to get the dialog to disappear was to refresh the page in your browser. This was a purely superficial issue and has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19317 7) [Problem] In previous versions of Iguana, if you logged in as a user with limited permissions and viewed the Users page for that user, the table that summarizes that user's permissions would be incorrect. This was a superficial display issue; that user's permissions were properly restricted. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0 Iguana 4.5 [Tracking Numbers] #19261 8) [Problem] In Iguana 5.0.9, while using Internet Explorer 8 to create a new Translator channel, once you chose to either import an existing project, or start with a new project, a dialog would immediately appear incorrectly indicating the Lua file had been modified outside of the editor. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19253 9) [Problem] In Iguana 5.0.9, while editing a Translator script, when a dialog displaying an expanded tree is docked or undocked, in some circumstances the expanded nodes would become collapsed. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18943 10) [Problem] In Iguana 5.0.3 and later, while editing a Translator script, if you had more than one shared Lua module with names that started with the same characters, for example one Lua module named "db.test" and another named "db.example", you may not have been able to switch between modules in the editor. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.3 and later [Tracking Numbers] #19388 11) [Problem] In Iguana 5.0.9, while editing a Translator script, if you performed a text search in the Translator editor and you were using Internet Explorer 8 or 9, there would in some circumstances be a significant delay between you entering the search text and seeing it appear in the search bar. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19282 12) [Problem] In Iguana 5.0.9, while editing a Translator script, if you performed a text search in the Translator editor and you were using Internet Explorer 8, the small "x" icon in the search field would not clear the search bar. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19024 13) [Problem] In Iguana 5.0.9, while editing a Translator script, if you were using Internet Explorer 9 and were editing a script that resulted in an annotation block that displays more than one iteration, the little arrows at the top of the annotation block that are used for navigation between the iterations did not appear at all. This has been fixed in Iguana 5.0.10. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19283 ************************************************************************ Changes ************************************************************************ 1) [Description] The default "Expect" header in net.http.put() in the Translator API has been changed from '100-continue' to an empty string ''. This change was made to compensate for some web servers not handling '100-continue' which would have resulted in a one second delay before sending the PUT data. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #19174 2) [Description] The behavior of node:remove() in the Translator API has been changed. In previous versions of Iguana 5.0, nodes and segments in an HL7 v2.x message can only be removed by using node.remove() if it's a repeating node or segment. In all other cases, if you tried to use node.remove() to remove the node or segment you would get an error. In Iguana 5.0.10, this has been changed so that using node:remove() on a non-repeating node or segment is equivalent to assigning nil to that node or segment. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #18592 3) [Description] When using a Translator script, when you convert a HL7 message from a node tree to a string a trailing carriage return character "r" is now appended to the last segment. This change was made to ensure that HL7 node trees that are converted to strings conform to the HL7 Standard. [Affected Releases] Iguana 5.0.10 [Tracking Numbers] #18929
Change log for Iguana 5.0.9 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] Microsoft Internet Explorer 8 and Internet Explorer 9 are now supported for use with Iguana 5.0.9. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18607 2) [Description] In Iguana 5.0.9 you can now configure Iguana to serve files using the HTTP(S) Channel Server. To see an example of how to use this functionality see http://help.interfaceware.com/kb/745. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18409 3) [Description] Iguana plugins and Chameleon stubcode can now be created using JDK 1.7. [Affected Releases] Iguana 5.0.9 Chameleon 5.4.9 [Tracking Numbers] #19081, #19105 4) [Description] In Iguana 5.0.9, when creating a new Translator channel a new option has been added to the "Import Project/Sample Data" wizard allowing you to import a project from a zip file. This makes the process of copying projects from other Translator channels into new channels more streamlined. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18278 5) [Description] In Iguana 5.0.9, while editing a Translator script, if you reconfigure the layout of the Translator editor screen by moving the splitter separating the editor pane and the project manager pane, or the splitter separating the editor pane from the dock, the location of the splitters is now remembered for your convenience. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18984 6) [Description] In Iguana 5.0.9, the channel configuration page for the From HTTP(S) component has been enhanced to show the full URL path when using the Translator as part of this component. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18664 7) [Description] Every function in the db namespace in Translator scripts now accepts a "use_unicode" flag that allows you to control whether or not database connections from Iguana are configured to use Unicode. This flag may be necessary if you are dealing with information that contains international characters. This flag is set to false by default in order to maintain backwards compatibility with older versions of Iguana 5.0. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #19201 8) [Description] In Iguana 5.0.9, in the rare circumstances when Iguana goes into a panic state and stops all channels, the red error message that is displayed on the dashboard that explains why Iguana went into the panic state has been enhanced to include a date and timestamp to make it easier to diagnose the problem. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18610 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In Iguana 4.1.13, changes were introduced so that if external software locked Iguana's log files while Iguana was attempting to access them, Iguana would reattempt accessing the log files for 30 seconds instead of immediately going into a panic state and stopping all channels. In Iguana 5.0.7, changes were introduced that caused Iguana to not retry accessing it's log files when locked by an external process, causing Iguana to immediately panic and stop all channels. This has been fixed in Iguana 5.0.9, and the retry logic has been enhanced to retry for 30 minutes. This is to accommodate enterprise environments where it may be difficult to follow best practices with respect to not having Iguana's index files included in back-ups. Note that the retry time period has been extended to 30 minutes in Iguana 4.1.23 and Iguana 4.5.7. [Affected Releases] Iguana 4.1.22 and earlier, Iguana 4.5.6 and earlier, Iguana 5.0.7 and 5.0.8 [Tracking Numbers] #19078, #19095, #19109 2) [Problem] In Iguana 5.0 and later, if external software locked Iguana's log files, Iguana's dashboard would be unresponsive while the log files were locked. Once the log files became unlocked, Iguana's dashboard would respond normally. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0 and later [Tracking Numbers] #19108 3) [Problem] In Iguana 5.0.3 and later, if you created a LLP Listener channel that used the Translator to verify acknowledgment messages, if you later deleted that channel the Translator scripts were not removed completely from the installation of Iguana. Similarly, in Iguana 5.0.5 and later, if you created a From HTTPS channel that used the Translator, if you later deleted that channel the Translator scripts were not removed completely from the installation of Iguana. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.3 and later [Tracking Numbers] #18920 4) [Problem] In Iguana 5.0.2 and later, if you used the net.http.put() function in a Translator script to send data larger than 16k, the Translator would incorrectly send the first 16k of data repeatedly up to the length of the original data. This has been fixed in Iguana 5.0.9. A workaround for this problem has been documented for use with older versions of Iguana. [Affected Releases] Iguana 5.0.2 and later [Tracking Numbers] #19021 5) [Problem] Internal testing of the From HTTP(S) component configured to use the Translator has revealed that in the scenario when the channel is very busy handling many HTTP requests from multiple connections there was the rare possibility that the channel would not handle all requests in a timely fashion. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.5 and later [Tracking Numbers] #19502 6) [Problem] In Iguana 5.0.7 and 5.0.8, while performing a search in Iguana's log browser, in some circumstances the text that was highlighted in the log preview did not match the search string. The incorrect highlighting of the search string was only applicable to the log preview messages. Highlighting worked properly when viewing individual log messages. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18921 7) [Problem] In Iguana 5.0.2 and later, while using a Translator script, if you attempted to pass binary data to the "body" parameter of net.http.post() it would not work. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.2 and later [Tracking Numbers] #19163 8) [Problem] In Iguana 5.0.7 and later, when viewing an individual log message, the tooltips on the toolbar buttons are missing. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.7 and 5.0.8 [Tracking Numbers] #19170 9) [Problem] In previous versions of Iguana 5.0, while editing a Translator script if your script attempted to use code from an unreachable Lua file, annotations past that point in the script would stop working. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0 and later [Tracking Numbers] #19049 10) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, under the very specific scenario of switching which Lua file you were editing when both the script took a very long time to run (due to a long blocking operation, or a sleep call, etc.) and while a line was marked as "dirty" there was a small possibility that the contents of one Lua file would have been overwritten by the contents of the other Lua file. This has been fixed in Iguana 5.0.9. Overall improvements to the annotations backend in Iguana were also done to improve performance when switching between Lua files in the Translator editor. [Affected Releases] Iguana 5.0 and later [Tracking Numbers] #18914, #19029 11) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if you had a slow connection to Iguana and you had some tabs open in the dock, when annotations were updated due to changes in your Lua script, sometimes some of the tabs would retain their "spinner" icons. This was a superficial display issue. The contents of the tabs were updated appropriately, the issue was that the GUI indicated that it was still waiting to refresh the tabs. [Affected Releases] Iguana 5.0.7 and later [Tracking Numbers] #18975 12) [Problem] In Iguana 5.0.7 and later, while editing a Translator script, if your script contained an error and you opened the error stack trace window for the error, and if the window containing the error stack trace was docked, if you popped out the entire dock into a window, and then later docked the entire dock again, the tab containing the error stack trace would not remain open. This has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.7 and 5.0.8 [Tracking Numbers] #19113 13) [Problem] In Iguana 5.0.8, in the Translator script editor, the splitter that separates the editor pane from the project manager pane would appear to overlay the dropdown dialog that allows you to import sample data from Iguana's log files. This was a superficial display issue, and has been fixed in Iguana 5.0.9. [Affected Releases] Iguana 5.0.8 [Tracking Numbers] #19056 ************************************************************************ Changes ************************************************************************ 1) [Description] In previous versions of Iguana 5.0, while editing a Translator script, accessing non-existent repeats of HL7 segments/fields or database result set rows would cause a script error. This behaviour has been changed in Iguana 5.0.9 to return a null segment/field or row instead of causing a script error. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18535, #19017 2) [Description] When using previous versions of Iguana 5.0 under Microsoft Windows, while editing a Translator script, if you passed invalid format parameters to the os.date() function, the function would return nothing. This has been changed in Iguana 5.0.9 to leave unknown format parameters as-is in the output to make it easier to diagnose such problems, and also to make the behavior consistent across all operating systems. [Affected Releases] Iguana 5.0.9 [Tracking Numbers] #18350
Change log for Iguana 5.0.8 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] While editing a Translator script, there is now the ability to stop the script after it has started to run in the editor. [Affected Releases] Iguana 5.0.8 [Tracking Numbers] #18203 2) [Description] While editing a Translator script, if you perform a text search in the editor you can now move to the next search result using the Enter key. [Affected Releases] Iguana 5.0.8 [Tracking Numbers] #18945 3) [Description] The following Translator API functions now give you the ability to override the default timeout period: * net.http.delete() * net.http.get() * net.http.post() * net.http.put() * net.smtp.send() * net.ftp.init() * net.ftps.init() * net.sftp.init() [Affected Releases] Iguana 5.0.8 [Tracking Numbers] #18584 4) [Description] While editing a Translator script you can now customize the location of the splitter that divides the editor pane from the Project Files pane. [Affected Releases] Iguana 5.0.8 [Tracking Numbers] #18850 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] While editing a Translator script on a 64-bit Windows platform, if the script was very long Iguana may have crashed. This has been fixed in Iguana 5.0.8 [Affected Releases] Iguana 5.0 [Tracking Numbers] #18879 2) [Problem] In previous versions of Iguana 5.0, if you had changed the sorting order of channels on the Dashboard, clicking on a component's icon may have brought you to the incorrect channel and component. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18835 3) [Problem] In Iguana 5.0.7, if SQLite was being used with db.execute() or db.query() in a Translator script, and you attempted to pass an empty SQL string to the database you would get a error about a precondition failure. This has been fixed in Iguana 5.0.8 to report the correct error about the SQL statement being empty. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18819 4) [Problem] While editing a Translator script in previous versions of Iguana 5.0, if the script was modified to include any text that contained non-ASCII characters, when performing a diff between the new version and a previous version that did not contain the non-ASCII characters, the diff tool would report that it was performing a binary diff instead of a text diff. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18768 5) [Problem] In Iguana 5.0.7, while editing a Translator script if you had a multi-line comment that contained Lua keywords indentation levels in the editor may have become incorrect. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18750 6) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, auto-completion would not suggest child nodes that weren't already initialized. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18983 7) [Problem] In previous versions of Iguana, with some versions of the Windows ODBC driver the driver would not properly handle deallocation of null handles, causing Iguana to crash when attempting to free a null database handle. This has been fixed in Iguana 4.1.23, 4.5.7, and 5.0.8 such that Iguana no longer asks the ODBC driver to free a null handle. [Affected Releases] Iguana 4.1.22 and earlier, Iguana 4.5.6 and earlier, Iguana 5.0.6 and earlier [Tracking Numbers] #19001 8) [Problem] In Iguana 5.0.7, while viewing a tooltip on the dashboard, dashboard refreshing would stop until the tooltip closed. Also, the contents of the tooltip would occasionally become out of sync with the information displayed on the dashboard. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18512, #18932 9) [Problem] In previous versions of Iguana, configuring a From HTTP(S) Translator script to skip a message when an error is encountered using iguana.stopOnError(false) did not work correctly. The From HTTP(S) component would always stop when an error was encountered, regardless of how it was configured. This has been fixed in Iguana 5.0.8. [Affected Releases] Iguana 5.0.5 through 5.0.7 [Tracking Numbers] #18861 ************************************************************************ Changes ************************************************************************ 1) [Description] While editing a Translator script, when saving a milestone the "Save" button is disabled while Iguana gathers information about what changed since the last milestone was saved. Once this information is gathered, the Save button gets enabled. This change prevents the situation where the Save button is used before Iguana has had the opportunity to determine what needs to be saved. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18740 2) [Description] In previous versions of Iguana 5.0, while editing a Translator script for a From HTTPS channel, if the script did not send a response using net.http.response() the editor would not report this lack of response as an error. This has been changed in Iguana 5.0.8 so that the editor now reports this condition as an error. This change makes the editor behavior the same as when the channel runs with the same lack of response in the Translator script. [Affected Releases] Iguana 5.0.5 through 5.0.7 [Tracking Numbers] #18832
Change log for Iguana 5.0.7 (top)
************************************************************************ Feature Additions ************************************************************************ 1) [Description] Translator scripts and the To Database and From Database components can now use SQLite for any database needs. Iguana makes use of the version of SQLite that is included with Iguana. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18383 2) [Description] Iguana 5.0.7 has the ability to read and edit DICOM files. Currently this is only supported under the following operating systems: * Microsoft Windows (32-bit and 64-bit) * Ubuntu GNU/Linux (32-bit and 64-bit) See Processing DICOM Files for details on how to use this functionality. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18303, #18671 3) [Description] While editing a Translator script, there is now the ability to step into and out of functions in the annotations. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18387 4) [Description] While editing a Translator script, any error that occurs now has a traversable stack trace, making it easier to track down the source of the error. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18430 5) [Description] While editing a Translator script, if an error occurs the dialog that reports the error message is now truncated for large error messages. All error dialogs can be clicked on so that they can subsequently be dragged around the editor screen; clicking on the error dialog will expand the error dialog to display the full text of the error message in cases where the text was truncated. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18428 6) [Description] While editing a Translator script, undo history is maintained for each Lua script until you navigate away from the editor entirely. In previous versions of Iguana, undo history was lost when moving between different Lua scripts in the editor. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #17864 7) [Description] While editing a Translator script, any dialogs that display string information now have the ability to change the view of the string data. In addition to the "Plain Text" view there is now an "Escaped Text" view and a "Hexadecimal" view. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18309 8) [Description] The underlying control for the Translator editor has been upgraded to CodeMirror 2. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18117 9) [Description] All dialogs in the Translator editor can now be docked at the bottom of the editor screen. The entire dock can also be popped out into a dialog that contains all of the docked dialogs. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #17304 10) [Description] Message, segment, and composite definitions from version 2.7 of the HL7 standard are now available in the HL7 2.7 library VMD in Chameleon. Iguana's log browser now uses the HL7 2.7 library VMD for the "HL7 Standard Library". [Affected Releases] Iguana 5.0.7 Chameleon 5.4.7 [Tracking Numbers] #18371 11) [Description] While editing a Translator script, when clearing a node by assigning nil to it, the annotations have been enhanced to explicitly state that this action is occurring. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #15717 12) [Description] While editing a Translator script, when using the autocompletion feature the "Page Up" and "Page Down" keys now allow you to scroll through the autocompletion suggestions. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #17342 13) [Description] XML parse errors in Translator scripts now give more context surrounding the error to make it easier to debug problems. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #16735 14) [Description] The logging system has been improved such that memory usage in high throughput environments is reduced. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18083 15) [Description] While editing a Translator script, if you click on an annotation that is already open in the editor, the relevant dialog or tab will blink to indicate it is already open. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18606 16) [Description] While editing Translator scripts, the Translator editor now has a search and replace field that allows you to search the entire contents of a Lua script. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18564 17) [Description] While editing a Translator script, every file has a "File History" that allows you to view the complete history of the file, as well as perform diffs between the current version and any previous version. This "File History" dialog is accessible from three locations in the Translator editor: 1. In the Project Manager pane of the editor, in the context menu for every file there is now a "File History" link 2. When saving a milestone, every file name can be clicked on to view it's history 3. When viewing saved milestones, every file name can be clicked on to view it's history [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18209 18) [Description] While editing a Translator script, the state of the "Show Annotations" and "Show Empty Nodes" toolbar buttons are now remembered between editor sessions. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18463 19) [Description] While using a Translator script, iguana.messageId() can now be used to get the message ID of the message that is currently being processed. iguana.logDebug(), iguana.logInfo() and iguana.logWarning() have been modified to take an optional "message_id" parameter so that you can now associate the log messages generated with these functions to a particular message. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18552 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In previous versions of Iguana, configuring a Translator script to skip a message when an error is encountered using iguana.stopOnError(false) did not work correctly in the From Translator component. The From Translator component would always stop when an error was encountered, regardless of how it was configured. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0.3 through Iguana 5.0.6 [Tracking Numbers] #18434 2) [Problem] In previous versions of Iguana 5.0, while editing a Translator script if your script had any errors in it, autocompletion would stop working regardless of the location of the error. This has been fixed in Iguana 5.0.7 so that autocompletion will work up to the the location of the error. [Affected Releases] Iguana 5.0 [Tracking Numbers] #16804 3) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if the data that is displayed in a dialog was deleted from the script while the dialog was open, Iguana would crash. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18416 4) [Problem] In previous versions of Iguana 5.0, while editing a Translator script annotations did not work properly for recursive functions. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18357 5) [Problem] In previous versions of Iguana, when using the From Database component and interacting with a database table where date/time information is stored in ISO-8061 format as a string, and the matching table column definition in the VMD file uses the DateTime format, when Iguana converts the string into the DateTime format it would in certain circumstances incorrectly report that the string was improperly formatted. This has been fixed in Iguana 5.0.7. [Affected Releases] All previous versions of Iguana [Tracking Numbers] #18702 6) [Problem] In previous versions of Iguana 5.0, if you called node:setInner() on an XML node in a Translator script the number of attributes the element had was incorrectly subtracted from the number of children that were successfully added. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18358 7) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if you cleared a script entirely and then added a new script, a dialog indicating the file had been edited outside the editor would incorrectly appear. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0.5 and 5.0.6 [Tracking Numbers] #18450 8) [Problem] In previous versions of Iguana, while performing a search in Iguana's log browser, in some rare circumstances the highlighted text of the log preview messages may have been truncated. This issue was a superficial display problem and only affected the log preview messages. This issue has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 4.5 and Iguana 5.0 [Tracking Numbers] #17472 9) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if you enabled the "Show Empty Nodes" toolbar button and then moved away from the editor screen, when you came back to the editor screen, empty nodes would still be displayed in dialogs but the button on the toolbar would show as being disabled. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18384 10) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if you had any dialogs open and the browser window was resized for any reason (e.g., you changed monitors, or resized the window manually), the dialogs would not scale with the size of the window. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18254 11) [Problem] In Iguana 4.1.13 and later, changes were introduced so that if external software locked Iguana's log files while Iguana was attempting to access them, Iguana would reattempt accessing the log files for 30 seconds instead of immediately going into a panic state and stopping all channels. In subsequent versions of Iguana, there was still the chance that Iguana would immediately panic when attempting to access log files that were locked by an external process. This has been fixed in Iguana 4.1.22, Iguana 4.5.6, and Iguana 5.0.7. [Affected Releases] Iguana 4.1.13 through 4.1.21, Iguana 4.5.1 through 4.5.5, Iguana 5.0.1 through 5.0.6 [Tracking Numbers] #17547 12) [Problem] In Iguana 4.5 and later, if Iguana was shutting down while it was in the middle of sending out an email, Iguana would not stop cleanly. This has been fixed in Iguana 4.5.6 and Iguana 5.0.7. [Affected Releases] Iguana 4.5.1 through 4.5.5, Iguana 5.0.1 through 5.0.6 [Tracking Numbers] #18724 13) [Problem] In Iguana 5.0.5 and 5.0.6, while using a Translator script in the From HTTPS component, when the channel was starting, the tooltip for the channel status on the dashboard would say "Unknown status". This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0.5 and 5.0.6 [Tracking Numbers] #18413 14) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, if a Lua module was added to the project manager that contained an ampersand '&' character in its name you would be unable to view or edit the script. This has been fixed in Iguana 5.0.7. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18443 ************************************************************************ Changes ************************************************************************ 1) [Description] In previous versions of Iguana 5.0, in Translator scripts node:remove() used zero-based indexes. This has been changed in Iguana 5.0.7 such that node:remove() now uses 1-based indexes in order to make it consistent with other functions. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18459 2) [Description] In previous versions of Iguana 5.0, using node:nodeType() in a Translator script on a node that is a field that repeats would return a type of "field". This has been changed in Iguana 5.0.7 to return "field_repeated". Similarly, in previous versions of Iguana 5.0, using node:nodeType() on a node that is a segment group that repeats in a Translator script would return a type of "segment_group". This has been changed in Iguana 5.0.7 to return "segment_group_repeated". These changes were made to make node:nodeType() more intuitive and consistent with other return types of node:nodeType(). [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #16822 3) [Description] Error messages reported in tooltips on the dashboard and in channel control panels now preserve line breaks that may be present in the error message, making it easier to read the contents of the tooltip. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #17715 ************************************************************************ Known Issues ************************************************************************ 1) [Description] While using Firefox 6 on Mac OS X to edit a Translator script, the right-click context menu does not work. This is a known issue with CodeMirror 2, the underlying control used in the Translator editor. [Workaround] Use the Firefox menu, or the hot-key combinations to perform the tasks found in the right-click context menu. [Affected Releases] Iguana 5.0.7 [Tracking Numbers] #18716
Change log for Iguana 5.0.6 (top)
************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In Iguana 5.0, while using db.merge() in a Translator script if the database connection failed during the merge call, any subsequent retries of db.merge() using retry logic in Lua would fail. This has been fixed in Iguana 5.0.6. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18341 2) [Problem] In Iguana 5.0, while in the Translator script editor if your script had any type of error, annotations would no longer be displayed alongside your script. This has been fixed in Iguana 5.0.6 so that annotations will be displayed up to the location of the error. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18354 3) [Problem] In Iguana 5.0.5, while editing a Translator script a dialog would in some circumstances repeatedly and incorrectly appear indicating the script you were editing had been modified outside of the editor. This has been fixed in Iguana 5.0.6. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18339, #18347
Change log for Iguana 5.0.5 (top)
************************************************************************ Additions ************************************************************************ 1) [Feature Description] In Iguana 5.0.5 you can now export all of the files associated with a Translator script into a zip file. You can then import this zip file into another Translator instance. This makes it easy for you to move a Translator script setup from one channel into another. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17954 2) [Feature Description] Iguana 5.0.5 now offers several built-in data filters in Translator scripts. The following filters are available: * encoding to and decoding from base-16 * encoding to and decoding from base-64 * encoding and decoding URI component text * encoding text for HTML documents * compressing and decompressing zip files (BZip2 and GZip) * encrypting and decrypting data with AES See http://help.interfaceware.com/kb/496 for more details. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18102 3) [Feature Description] In Iguana 5.0.5 the LLP Listener component now allows configuration of which characters to expect for the LLP wrapper. This allows for operation of the LLP Listener component with systems that use non-standard LLP wrappers. Additionally, the hl7simulator command-line tool now allows you to specify the LLP wrapper characters. This change was made to allow for easier testing of this new LLP Listener option. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17989 4) [Feature Description] In Iguana 5.0.5 chm.transform() is now available in Translator scripts, allowing the usage of VMD files that perform legacy scripted or graphical transformation to be migrated into Iguana 5.0. See http://help.interfaceware.com/kb/542 for more details. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17982 5) [Feature Description] In Iguana 5.0.5, any dialog boxes that are open in the Translator script editor that display information in a tree format now maintain their geometry if you change the sample data, log out and log back into Iguana, or when the page is refreshed. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17758 6)[Feature Description] In Iguana 5.0.5, items listed in all auto-completion drop-down selectors in the Translator script editor are now sorted alphabetically by name to make it easier to find and select the desired item. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17922 7) [Feature Description] In Iguana 5.0.5, anonymous functions, local functions, named functions whose bodies are defined inside of other functions' bodies, and functions that are named by non-string keys now have annotations in the Translator script editor. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17930 8) [Feature Description] In Iguana 5.0.1 through Iguana 5.0.4, db.merge() would not perform any database operations while editing a Translator script. db.merge() now accepts a "live=true" argument that will cause it to perform its database operations while editing a Translator script. By default this argument is set to false since the actions performed by db.merge() may have consequences you may not want to occur while you are editing a Translator script. Note that this argument is ignored when the channel is running. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17897 9) [Feature Description] In Iguana 5.0.5, you can now specify GET parameters as part of the "url" argument in net.http.get() and net.http.post() in Translator scripts. Any additional GET parameters specified in the "parameter" or "get_parameters" table arguments will be appended to any parameters specified in the "url" argument. Additionally, an error is now thrown if you attempt to use non-string keys in the "parameters" or "get_parameters" tables. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18123 10) [Feature Description] In Iguana 5.0.5 you can now use a Translator script in the From HTTPS component. Note that if you opt to use a Translator script in the From HTTPS component, you are required to use the dedicated web server for HTTPS channels (configurable via the Settings > HTTP(S) Channel Settings page). Additionally, Iguana 5.0.5 now allows you to use the dedicated web server without using HTTPS. See http://help.interfaceware.com/kb/537 for an example of how to use this new functionality. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17575 11) [Feature Description] In Iguana 5.0.5, every function in the net.ftp, net.ftps, net.sftp, and net.smtp namespaces in Translator scripts now accept a "debug" flag that allows you to get more detailed output from the function call. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17976, #18120 12) [Feature Description] In Iguana 5.0.5, iguana.channelName() now supplies the channel name in the annotations in the Translator script editor instead of the string '[channel_name]'. Also, iguana.channelName() no longer returns a second value indicating whether or not the first return value is real, since the first return value is now always the real channel name. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18078, #18187 13) [Feature Description] In Iguana 5.0.5, while editing a Translator script all function parameters and return values can now be clicked on for more detailed examination. In previous versions of Iguana you could only examine strings, tables, and trees in more detail. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18009 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] In previous versions of Iguana 5.0, if you were connecting to a SQL Server database in a Translator script, the following database types were not properly supported: * any binary type * UUID * money and shortmoney types These database types in SQL Server are now fully supported. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18079 2) [Problem] In previous versions of Iguana 5.0, if you had misspelled an optional parameter in any of the Translator API function calls in a Translator script there would have been no indication of an error. This has been fixed in Iguana 5.0.5. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18048 3) [Problem] In previous versions of Iguana 5.0, even if pcall was being used an exception would result in the termination of the script while within the Translator editor. Now the editor allows users to handle an error result being returned by pcall. This has been fixed in Iguana 5.0.5. [Affected Releases] Iguana 5.0 [Tracking Numbers] #17605, #17572 4) [Problem] In previous versions of Iguana, when Iguana and Chameleon were installed under 64-bit Windows the Iguana environment variables "chameleon_dir" and "CHM_PYTHON_LIB_PATH" were not set properly. This has been fixed in Iguana 5.0.5. [Affected Releases] Iguana 5.0 and earlier [Tracking Numbers] #17564 5) [Problem] In previous versions of Iguana 5.0, while editing a Translator script, in some cases using deep auto-completion on a Lua table which contained references to nodes (for example, HL7 message parts) would cause Iguana to crash. This has been fixed in Iguana 5.0.5. [Affected Releases] Iguana 5.0 [Tracking Numbers] #18165 6) [Problem] In Iguana 5.0.3 and 5.0.4, the dateparse module that ships with Iguana would not properly handle passing in the string "NULL" as the date to parse in Translator scripts. This has been fixed in Iguana 5.0.5. [Affected Releases] Iguana 5.0.3 and 5.0.4 [Tracking Numbers] #18264 7) [Problem] In previous versions of Iguana 5.0, if you were editing a script in two or more separate browser windows while logged in in all windows as the same Iguana user, there was the possibility that the changes made in one of the windows would overwrite the changes in the other windows without any indication of this happening in the Translator script editor. This has been fixed in Iguana 5.0.5. Now when you are editing a Translator script, if the script has been changed since the last time it was auto-saved in the window you are currently working in, the Translator editor will inform you that the script has changed and will allow you to load the latest version of the script. [Affected Releases] Iguana 5.0 [Tracking Numbers] #17454 ************************************************************************ Changes ************************************************************************ 1) [Description] In Iguana 5.0.1 through 5.0.4 the db.merge() function in Translator scripts had parameters "retries" and "reconn" to control database connection retries. In Iguana 5.0.5, these parameters have been removed. Users requiring retry logic should implement the logic in Lua directly since it gives significantly more control. See http://wiki.interfaceware.com/482.html for an example. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #17961 2) [Description] In Iguana 5.0.5, under Unix all .log files are now created with read-access granted to all users while allowing only the owner to write to them. Previous versions of Iguana created .log files with read/write access for only the owner. For more information on controlling access to Iguana's log files see http://help.interfaceware.com/kb/519. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18043 3) [Description] In Iguana 5.0.1 through 5.0.4 io.popen() was not available on Solaris or AIX in Translator scripts. In Iguana 5.0.5 io.popen() is now available for use on all supported platforms. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18189 ************************************************************************ Known Issues ************************************************************************ 1) [Description] When using the From HTTPS component, the icon on both the dashboard and in the channel control panel shows "HTTPS" regardless of whether or not HTTPS is being used. [Affected Releases] Iguana 5.0.5 [Tracking Numbers] #18296
Change log for Iguana 5.0.4 (top)
***************************************************************
Additions
***************************************************************
1) [Feature Description]
net.http.put() and net.http.delete() are now part of the
net.http namespace in Translator scripts.
Additionally, all functions in the net.http namespace
now accept an optional "method" parameter that allows you
to override what HTTP method is used, enabling you to use
HTTP methods not explicitly defined in the namespace.
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17845
2) [Feature Description]
In Iguana 5.0.2 and 5.0.3 the functions in the net.http
namespace in Translator scripts only provided the ability
to use basic authentication by supplying a username and password
as part of the URL.
Every function in the net.http namespace now offers
more extensive options for authentication, available
by using the optional "auth" and "ssl" parameters.
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17946
3) [Feature Description]
Every function in the net.http namespace in Translator scripts
now accepts a "debug" flag that allows you to get more
detailed output from the function call.
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17846
4) [Feature Description]
In Translator scripts net.ftp.init(), net.ftps.init(), and
net.sftp.init() now provide advanced authentication and protocol
options.
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17701
5) [Feature Description]
In Translator scripts db.merge(), db.execute(), and db.query()
now accept an optional "timeout" parameter for ODBC
database connections that allows you to limit the length of time
a database operation can take before being stopped with a timeout
exception.
This timeout parameter is supported only for database
connections done through ODBC where the database supports
this functionality, such as Microsoft SQL Server.
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17969
***************************************************************
Bug Fixes
***************************************************************
1) [Problem]
In Translator scripts iguana.logDebug(), iguana.logInfo(),
and iguana.logWarning() would create log entries that were not
associated with the message that was being processed when these
functions were called in a Translator script.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0.3
[Tracking Numbers]
#17962
2) [Problem]
On some 32-bit platforms the dateparse Lua module would
not handle dates prior to Dec 13, 1901; attempting to
parse a date prior to that would result in an "invalid
date/time" error.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0.3
[Tracking Numbers]
#18021
3) [Problem]
In Translator scripts functions in the net.http namespace
would escape all non-alphanumeric characters.
Iguana 5.0.4 has been fixed such that only unreserved
characters are escaped as per the URI standard
(RFC 2396, section 2.6).
[Affected Releases]
Iguana 5.0.2 and Iguana 5.0.3
[Tracking Numbers]
#18042
4) [Problem]
Annotations were missing for member functions for file handles,
TCP objects, and FTP objects in the Translator editor.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#18024
5) [Problem]
Clicking an argument/return-value to examine it in the
annotations in the Translator editor could, in some cases,
create an error and therefore show the error instead of the
could happen if the value being examined was a Lua table
value. This or a userdata object with an __index table defined
in its metatable.
[Affected Releases]
Iguana 5.0.3
[Tracking Numbers]
#15730
6) [Problem]
The Import Wizard in Translator channels that allows you
to import a project from other Translator channels or from
the examples that ship with Iguana would take a long time
to load, especially when there were a large number of
Translator channels in addition to the examples.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#17724
7) [Problem]
Auto-completion in the Translator editor did not work in files
that used the module() function.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#18025
8) [Problem]
Using iguana.setChannelStatus{} in an Iguana Translator
script to set the text of the channel's tooltip to an empty
string (to clear it) without also explicitly setting the
color of the channel status light,
e.g., iguana.setChannelStatus{text=""}, would result
in a bogus syntax error about missing function arguments.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0.3
[Tracking Numbers]
#17965
9) [Problem]
The X12 examples that shipped with Iguana for use in the
Translator, namely "Example 05 - X12 270 to Database" and
"Example 06 - X12 271 to Database", contained errors.
These examples have been removed in Iguana 5.0.4.
There is extensive documentation for handling X12 here:
http://wiki.interfaceware.com/126.html
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#17908
10) [Problem]
The random data generator example that shipped with Iguana
for use in the Translator, namely "Example 07 - Random Data
Generator", contained errors.
This example has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#17921
11) [Problem]
If you have any dialog boxes open while editing a Translator
script and you alter the script, after any changes are auto-saved
by the editor the contents of the dialog boxes may incorrectly
display an error message.
This has been fixed in Iguana 5.0.4.
[Affected Releases]
Iguana 5.0
[Tracking Numbers]
#17834
12) [Problem]
If one or more dialog boxes were open in the Translator editor
and you logged out of Iguana, if you logged in again as a different user
the same dialog boxes would remain open.
In Iguana 5.0.4, the dialog boxes that are open are now
saved based on username.
[Affected Releases]
Iguana 5.0.3
[Tracking Numbers]
#17759
***************************************************************
Changes
***************************************************************
1) [Description]
In Translator scripts util.time() was removed from the util
library since it's functionality overlapped with the native
Lua os.time().
[Affected Releases]
Iguana 5.0.4
[Tracking Numbers]
#17924
Change log for Iguana 5.0.3(top)
************************************************************************ Additions ************************************************************************ 1) [Feature Description] In Iguana 5.0.1 and 5.0.2, if you use the Iguana Translator in a channel component in which the script's main() function is expecting a Data parameter to be passed to it, annotations do not appear if no sample data is provided. In Iguana 5.0.3, if no sample data is provided, annotations are displayed and the Data argument is displayed as an empty string. A dialog box appears to warn you that you have not provided any sample data for your script. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #16991 2) [Feature Description] The fuzzy date/time parser is now included in the Iguana Translator module repository. In previous versions of Iguana, you needed to create this module yourself before you could use it. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17695 3) [Feature Description] Iguana 5.0.3 allows you to use the Iguana Translator to create a script that serves as an LLP client. A new module, llp, provides this functionality. This provides useful capabilities such as improved customization of acknowledgment message validation and the ability to handle non-standard LLP wrapper characters. For a description of the llp module, and details on how to use the Iguana Translator as an LLP client, see Using the Translator as an LLP Client. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17607 4) [Feature Description] Scripts created using the Iguana Translator can now use international character sets. When you import sample data into an Iguana Translator script, you can now specify the file encoding to use. This ensures that all international characters are displayed properly. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17702 5) [Feature Description] You can now use your browser's Back and Forward buttons to move between Iguana Translator screens. This is handy if, for example, you want to examine the script in a module and then return to the main script. In previous versions of Iguana, clicking your browser's Back button returned you to the Iguana channel component that contained the Translator script. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17087 6) [Feature Description] Many of the functions in the Iguana Translator's FTP, HTTP and SMTP API libraries, and the functions that update external database tables, now allow you to disable potentially undesirable operations while you are editing a script. All of these functions now require a "live=true" argument to perform their intended operation while you are editing the script that contains them. In all cases, the the "live" flag is ignored when the channel is running. The following functions are affected: * To perform any function that changes the contents of the FTP server - net.ftp.delete(), net.ftp.rename() or net.ftp.put() - you must first call net.ftp.init() with the "live=true" argument. You can use net.ftp.list() or net.ftp.get() even if "live" is not set to true, as these functions do not change the FTP server. * Similarly, you must call net.sftp.init() with "live=true" to activate the net.sftp.delete(), net.sftp.rename() and net.sftp.put() functions. You must call net.ftps.init() with "live=true" to activate the net.ftps.delete(), net.ftps.rename() and net.ftps.put() functions. * net.smtp.send() now requires the "live=true" argument to be set before it will send out an email message. * net.http.post() requires "live=true" before it will perform a POST operation. * net.http.get() requires "live=true" before it will perform a GET operation. * db.execute() and db.query() require "live=true" before either function will update a database. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17682, #17818, #17825 7) [Feature Description] In an Iguana Translator script, you can now obtain the name of the channel in which the script is defined. To do this, call the iguana.channelName() function. For more details on this function, see The iguana Namespace. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17860 8) [Feature Description] The iguana.setChannelStatus() function, new in version 5.0.3 of Iguana, enables you to change the color of the status square of a channel. This status square can be set to green or yellow. iguana.setChannelStatus() also enables you to add additional text to the channel tooltip. For more details on this function, see The iguana Namespace. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17606 9) [Feature Description] Three new functions enable you to create log messages from within Iguana Translator scripts: * iguana.logDebug() writes a Debug log message to the log file if your channel's logging level is set to Debug. If the logging level is Normal or Errors, no message is written. * iguana.logInfo() writes an Informational log message to the log file if your channel's logging level is set to Debug or Normal. * iguana.logWarning() writes a Warning log message to the log file if your channel's logging level is set to Debug or Normal. For more details on these functions, see The iguana Namespace. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17604 10)[Feature Description] In previous versions of Iguana 5.0, an uncaught error in an Iguana Translator script stopped the channel in which the script was running. In Iguana 5.0.3, you can use the iguana.stopOnError() function to control whether Iguana should continue processing messages after detecting and logging an error. For more details on this function, see The iguana Namespace. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17377 11)[Feature Description] You can now supply GET parameters to the net.http.post() function in Translator scripts. To do this, specify the "get_parameters" parameter. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17857 12)[Feature Description] The db.execute() and db.query() functions now return two values: * The last record set selected by the SQL statement (or nil, if no record sets were selected) * A table containing all record sets selected by the SQL statement (this table is empty if no record sets were selected) For more information, see Executing Raw SQL. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17818 13)[Feature Description] By default, Iguana only allows a preset amount of time for an Iguana Translator script to execute. Scripts that take too long are assumed to be blocked, and the channel is stopped. In version 5.0.3 of Iguana, you can use the iguana.setTimeout() function to specify the length of time to wait before stopping the channel. This enables your script to perform longer operations. For more details on this function, see The iguana Namespace. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17837 14)[Feature Description] The new JSON module contains functions that enable you to generate JSON data from Lua tables or parse JSON data and store it in tables. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17576 15)[Feature Description] The output generated by the Iguana Translator XML API is now easier to read. Any XML tag with no child nodes or a single child node that is text or CDATA is written as <a>TEXT</a> instead of <a>ntTEXTn</a>. This means that unnecessary line feeds have been removed. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17401 16)[Feature Description] The Iguana Translator's auto-completion and annotation capabilities now work with all Lua tables. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #15730 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] Iguana 5.0.3 now allows you to include subdirectories in any require() statement specified in the Iguana Translator. For example, the statement "require('json.decode')" accesses the json/decode.lua file. Previous versions of Iguana did not support this. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17560 2) [Problem] In previous versions of Iguana 5.0, any user could edit and save a Translator script, even if this user had not been granted Edit permissions for the channel. In Iguana 5.0.3, only users who have been granted Edit permissions can edit and save a script. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17277 3) [Problem] If you are editing a script in the Iguana Translator, and you type characters that cause the auto-completion window to be displayed (such as "PID."), the open bracket "(" character cannot be typed immediately afterward. This problem has been fixed in Iguana 5.0.3. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17696 4) [Problem] In previous versions of Iguana 5.0, when a dialog box containing a large amount of information is opened in the Iguana Translator, the dialog box may be only partially displayed in the Translator window, as it is too large to fit in the window. In Iguana 5.0.3, all dialog boxes are displayed properly in the Iguana Translator window. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17679 5) [Problem] In previous versions of Iguana 5.0, if you use backslashes as file/directory separators in a file path in an Iguana Translator script, the script may not be able to locate the file on some Unix platforms. This is because these platforms only accept forward slash characters as file/directory separators. In Iguana 5.0.3, on any platform, you can use either backslashes or forward slashes as file/directory separators. When searching for a file specified in the script, the Iguana Translator will automatically convert one to the other if necessary. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17749 6) [Problem] If you are using the Iguana Translator in Firefox 4, attempting to resize a dialog box does not work properly. Resizing is only possible if you change the size of the dialog box very slowly. This problem has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17673 7) [Problem] In previous versions of Iguana 5.0, there was a problem with the text in the popup login box that appears when Iguana is starting up or the session has timed out. This text incorrectly stated that Iguana was not responding, even though it was still running. This problem has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17566 8) [Problem] If you are using the Remote Iguana Settings screen to add a new remote server to the list of servers to be monitored from the Dashboard, the screen disappears when you click Add. A page displaying "true" or "false" appears, with the value dependent on whether the URL that was typed was in the correct format. Adding a remote server works properly if you type Enter after typing the URL. This problem has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17774 9) [Problem] When you import sample data for a script, and no sample data has been previously imported, the "Overwrite all existing samples" check box is not displayed. This means that you cannot overwrite the data samples that you have just imported unless you exit the Sample Data screen and then re-enter it. In Iguana 5.0.3, the "Overwrite all existing samples" check box always appears after sample data is imported. [Affected Releases] Iguana 5.0.1 and 5.0.2 [Tracking Numbers] #17197 10)[Problem] The zip file version of Iguana 5.0.2 for Windows (the version that does not include the installer) did not contain any sample data files for the included Iguana Translator scripts. The Unix, Linux and Mac OS X versions of Iguana 5.0.2 were not missing any files. The zip file version of Iguana 5.0.3 of Windows includes all Iguana Translator sample data files. [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17754 11)[Problem] In previous versions of Iguana 5.0, if two or more channels that use Iguana Translator scripts are started simultaneously, one or more channels may be stopped. The error message that appears when a channel is stopped reports that the "/run" directory already exists. This is an incorrect error message: a channel should only be stopped if "/run" does not exist. In Iguana 5.0.3, this has been fixed. The channel is now started successfully if the "/run" directory already exists. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17683 12)[Problem] In previous versions of Iguana 5.0, if you are using ODBC to connect to a database and your Iguana Translator script is calling any of the functions that interact with databases (which are defined in the db module), the text for ODBC-related errors may not have been displayed. This has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17818 13)[Problem] In previous versions of Iguana 5.0, if you refreshed a page while you were editing an Iguana Translator script and one or more dialog boxes were open, the dialog boxes would not appear in the refreshed page. In Iguana 5.0.3, open dialog boxes will remain open after the page is refreshed. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17759 14)[Problem] In Iguana 5.0.1 and 5.0.2, if a dialog box is opened while an Iguana Translator script is being edited, and the Iguana server is unable to retrieve the necessary information for this dialog box, you will see the following text: Unable to retrieve data. Please try refreshing the entire screen. In Iguana 5.0.3, error reporting has been improved. The error message that is displayed now tells you why the data for the dialog box could not be retrieved. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17757 15)[Problem] In previous versions of Iguana 5.0, if you are using the Iguana Translator to edit a script and one or more dialog boxes are open, the data in the dialog boxes is not updated when the sample data is changed. This problem has been fixed in Iguana 5.0.3. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17756 16)[Problem] In previous versions of Iguana 5.0, annotations were not displaying non-printing characters. In Iguana 5.0.3, these characters are now displayed using the correct escape sequences. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17662 17)[Problem] In previous versions of Iguana, the message counts in the Queued column in the Dashboard server list may be incorrect. In Iguana 5.0.3, for each server in the Dashboard server list, the value in the Queued column is the sum of the message queue counts for that server's displayed channels. It is important to note that only channels that are displayed in the Dashboard channel list are included in the Queued total. This means that a channel search will change the total displayed in the Queued column. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17714 18)[Problem] If your Iguana Translator script assigns nil to a node indexed by a number (for example, MyNode[1] = nil), the following error message may incorrectly appear: This node does not have named members. Conversely, if you are using node.remove() to remove a child node specified by name, the error message shown above does not appear even when it should. This problem has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17666 19)[Problem] In previous versions of Iguana 5.0, when the Iguana Translator detects an error in a module that you are not currently editing, the error message that appears at the bottom of the screen is correct but does not properly link to the module in which the error appears. The problem with the link has been fixed in version 5.0.3 of Iguana. [Affected Releases] Iguana 5.0.1 and Iguana 5.0.2 [Tracking Numbers] #17691 ************************************************************************ Changes ************************************************************************ 1) [Feature Description] Version 5.0.1 and later of Iguana no longer support HP-UX PA-RISC, as this environment is not in common use. New versions of Chameleon (version 5.4.1 and later) will continue to support the HP-UX PA-RISC environment. [Affected Releases] Iguana 5.0.1 and later, Chameleon 5.4.1 and later [Tracking Numbers] #17847 2) [Feature Description] Version 5.0.3 of Iguana for Windows is built and shipped with the latest version of OpenSSL, which is 0.9.8r. [Affected Releases] Iguana 5.0.3 [Tracking Numbers] #17811
Change log for Iguana 5.0.2(top)
************************************************************************ Additions ************************************************************************ 1) [Feature Description] The Iguana Translator now provides support for the HTTP, HTTPS and SMTP protocols. This means that Lua scripts written using the Translator can now fetch data from and post data to websites using the HTTP or HTTPS protocols, and can also send email messages. Complete details can be found in the "net" interface specification. Note: this link was out of date see the net interface module instead. [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17365 2) [Feature Description] Scripts written in the Iguana Translator can now use the FTP, FTPS and SFTP protocols. Using these protocols, scripts can perform the following tasks: * Send a file to the server. * Receive a file from the server. * Delete a file on the server. * List the contents of a directory on the server. * Rename a file or directory on the server. Complete details can be found in the "net" interface specification. Note: this link was out of date see the net interface module instead. [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17568 3) [Feature Description] If you are creating a channel with LLP Listener as the source component, you can now use the Iguana Translator to create a script to generate acknowledgment messages. ACK messages generated by the Translator can now not only acknowledge receiving the message, but can confirm that the message contained no errors. For details on how to generate ACK messages using the Iguana Translator, see The ack Module and Custom ACKs. To specify that an Iguana Translator script is to be used to generate ACK messages, click the Source tab, then select "Translator" from the ACK list box. In the ACK list box, the "Custom" option is now called "Legacy VMD". [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17592 4) [Feature Description] In Iguana 5.0.2, you can now access your Iguana Translator scripts more easily. You can access them directly from the Iguana Dashboard, as a link to the script defined for a channel component or filter is now included in the tooltip for that component or filter. To display a channel tooltip, position your mouse over the appropriate component or filter icon in the channel definition. For details on how to do this, see Accessing the Iguana Translator. [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17175 5) [Feature Description] If a script created using the Iguana Translator is running and is accessing database connections, these connections are now included in the count of the number of active database connections for the server. The count of the number of active database connections for each server is provided in the Dashboard server list display. For more details on this display, see Viewing Server Information. [Affected Releases] Iguana 5.0.2 [Tracking Numbers] #17264 ************************************************************************ Bug Fixes ************************************************************************ 1) [Problem] If you are using the Dashboard to attempt to access a remote Iguana server that is running version 4.5.1, 4.5.2, 4.5.3 or 5.0.1 of Iguana, you may be asked to log into the remote server the first time you connect to that server, even if your username and password are identical on that server. If your remote server is running version 4.5.4 of Iguana or version 5.0.2 or later of Iguana, this extra login is now no longer required if your username and password are identical on that server. [Affected Releases] Iguana 4.5.1 to 4.5.3 [Tracking Numbers] #17602 2) [Problem] In Iguana 5.0.1, the Iguana Translator did not correctly handle file names on operating systems in which these names are case sensitive (such as Microsoft Windows). For example, a file named "DEMO.VMD" was not considered equivalent to a file named "demo.vmd". This is because the Iguana Translator's change tracking capability was assuming that files are case sensitive. In Iguana 5.0.2, case sensitivity is enforced in the Iguana Translator for all platforms. This means that if you want to access a file named "demo.vmd", you must specify "demo.vmd", not "DEMO.VMD" (or any mixed-case equivalent). You also cannot add a file to a project if its case-insensitive name is identical to that of an existing file: for example, you cannot add a file named "DEMO.VMD" if "demo.vmd" is already included in the project. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17489 3) [Problem] In Iguana 5.0.1, if you are using the Iguana Translator to edit the last line of a script, changes that you have made to this last line might not be saved. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17581 4) [Problem] In Iguana 5.0.1, if you clear the entire script that you are editing, use the Project Manager panel to select other scripts to view or edit, and then attempt to return to the cleared script, the editor screen incorrectly displays the last script you were viewing before you returned to the cleared script. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17571 5) [Problem] In Iguana 5.0.1, if you have created a channel that uses the Iguana Translator as a source component, destination component or filter, and you stop the channel while it is still initializing, an error similar to the following may be added to the logs: Precondition failure: state() == DBDchannelComponent::COMPONENT_STARTING This error was found during internal testing, and has not appeared on any customer's server. The condition that caused this error has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17567 6) [Problem] In Iguana 5.0.1, if you have created a channel that uses a filter, and this filter uses scripts that you have created using the Iguana Translator, these scripts disappear if you disable the filter and then re-enable it. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17541 7) [Problem] During internal quality assurance high-volume stress testing, channels that use the Iguana Translator as the source component, destination component or filter would occasionally freeze while stopping, and the following error message would be written to the log file: Failed precondition: pMember->CommitInProgress == false This error has not appeared at any customer sites, and the problem that caused this error has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17523 8) [Problem] The behavior of the require() function, used in Iguana Translator scripts, has changed. In version 5.0.1 of Iguana, require() did not return a value. In version 5.0.2, if require() loads a module, the name of the loaded module is returned. If no module has been loaded, or the loaded module does not match the file name, "true" is returned. This behavior more closely matches the behavior of require() in other Lua environments. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17456 9) [Problem] In Iguana 5.0.1, a problem exists if you use the automatic installer to upgrade from a previous installation of Iguana 5.0. If you specify that you do not want to use your existing configuration files, the files that configure the Iguana Translator are not moved to the directory to which the other configuration files are moved. (This is the "oldconfig" sub-directory of the directory in which you are installing Iguana.) All other Iguana configuration files are successfully moved to this sub-directory. In version 5.0.2 of Iguana, all of the configuration files, including those for the Iguana Translator, are moved properly. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17311 10)[Problem] In Iguana 5.0.1, if you disable a channel filter when a filter script has been created using the Iguana Translator, save the channel, re-enable the filter, and then click the Edit Script link without saving the channel again, the Iguana Dashboard displays an error message. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17542 11)[Problem] In Iguana 5.0.1, if you attempt to access the Iguana Translator to edit a script, and the project files for the script have been corrupted, moved or deleted, a blank screen appears. This has been corrected in Iguana 5.0.2. If you attempt to edit a script whose project files have been corrupted, moved or deleted, an error message appears. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17537 12)[Problem] Iguana 5.0.1 crashes if an Iguana Translator script contains a table that directly or indirectly refers to itself, and the code attempts to print this table when the channel is running. For example: local T1 = {} local T2 = {} T1['t2'] = T2 T2['t1'] = T1 print(T1, T2) If you are editing this script, no problems appear. Attempting to print these tables when the channel is running causes infinite recursion, which causes the crash. In Iguana 5.0.2, infinitely recursing tables, such as the one above, are handled correctly if they are printed when the channel is running. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17465 13)[Problem] In Iguana 5.0.1, in the Iguana Translator, if you start typing a line of script code that the Translator is unable to successfully auto-complete, you may see an error message similar to the following: Auto-Completion: bad argument #-1 to '?' (if.node expected, got table) In Iguana 5.0.2, auto-completion errors have been fixed to make debugging easier. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17480 14)[Problem] In Iguana 5.0.1, if you import sample data from the log files into an Iguana Translator script, each message has carriage return and newline characters (r and n) appended. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17403 15)[Problem] In Iguana 5.0.1, user names or milestone names that contain non-alphanumeric characters may not be displayed properly. This problem has been fixed in version 5.0.2 of Iguana. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17485 16)[Problem] When you save a milestone while using the Iguana Translator, the Save Milestone dialog box that appears is resizable. In Iguana 5.0.1, if you change the size of this dialog box, the "Milestone name" text field is not expanded. In Iguana 5.0.2, the "Milestone name" text field expands when the Save Milestone dialog box is expanded. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17492 17)[Problem] In Iguana 5.0.1, when you use the Save Milestone dialog box to save a milestone, the default milestone name is today's date. This is inconvenient if you want to save more than one milestone on a particular day. In Iguana 5.0.2, the default milestone name is "Milestone <n>". <n> is a count of the number of milestones that have been saved for this project. [Affected Releases] Iguana 5.0.1 [Tracking Numbers] #17034
Pingback: OpenSSL "Heartbleed" Security Update - iNTERFACEWARE Blog