The following fixes, enhancements and changes have been made in version 5.0 product update 5.

Check out the updates in the previous updates:

• See what’s new in the initial 5.0 Release
• Fixes in Product Update 4
• Fixes in Product Update 3
• Fixes in Product Update 2
• Fixes in Product Update 1

• IMAN-2465 – OAuth2 – Fixes an error on OAuth 2 when token request settings/body is empty.
• IMAN-2464, IMAN-2466 – Writer/JSON Writer – Fixes several issues when rewriting the operation’s results to IMan dataset where there is a batch size specified i.e. not zero.
• IMAN-2461 – WebserviceLookup – Fixes an issue where changes to the Webservice Lookup would not be reflected during design time, requiring a restart to the Data/Preview Service.
• IMAN-2460 – WebserviceLookup – Fixes an error on the WebserviceLookup function when the last (the return path) was specified.

The following fixes, enhancements and changes have been made in version 5.0 product update 4.

Check out the updates in the previous updates:

• See what’s new in the initial 5.0 Release
• Fixes in Product Update 3
• Fixes in Product Update 2
• Fixes in Product Update 1

• IMAN-2458 – Script Task – Extends script timeout to 9999 seconds.

• IMAN-2459 – Licensing – Fixes several licensing issues where expired license or exceeded license limit would either fail silently or with a message unrelated to the actual license issue.
• IMAN-2457 – Scheduler – Fixes issue where schedule intervals were not saving/reverting to minimum values.
• IMAN-2456 – Sage300 Orders – Fixes an issue where updates to Miscellaneous Charge lines were silently failing.
• IMAN-2455 – WebserviceLookup – Fixes/improves handling of JSON lookups where the path results in an array of values. The lookup will now return the values in a delimited list like the JSON Reader.
• IMAN-2453 – Salesforce – Fixes an issue preventing the Salesforce Reader from loading.
• IMAN-2450 – LookupWhere Function – Fixes an ‘Object Reference Exception’ when the underlying lookup is marked as safe.
• IMAN-2449 – Lookups/Functions – Fixes an issue where changes to lookups and functions would be reflected in the designer, requiring the Preview Service to be restarted.

The following fixes, enhancements and changes have been made in version 5.0 product update 3.

Check out the updates in the previous updates:

• See what’s new in the initial 5.0 Release

• IMAN-2437, IMAN-2447 – OAuth 2.0 – Initial release to allow OAuth 2.0 authentication via the Authorisation Flow (3-Legged).
  

  This will be further improved in PU4 where the OAuth setup screen will be overhauled.

  

• IMAN-2446 – Admin Console – Fixes/workaround the bottom end of the form being cutoff on small screen resolutions.
• IMAN-2445 – Lookup Tables – Resolves issue where vales could not be edited.
• IMAN-2444 – Sage300 – Resolves install issue where the connector would report ‘Exception has been thrown by the target of an invocation’.
• IMAN-2442 – Salesforce – Improve error message on Lookups returning multiple records.
• IMAN-2438 – Lookups – Improve handling of ‘safe lookups’.
• IMAN-2436 – DB Reader – Fixes issue where fields removed from query would not be detected.

Product Update 2 contains an urgent fix to the Aggregate Transform.

• See what’s new in the initial 5.0 Release
• Product Update 1

• IMAN-2431 – Fixes two issues with Aggregate transform: incorrect caching of expressions would cause same aggregate transforms with multiple Calc records to use formula from first record; very last iteration would double calculate aggregate transform.

The following fixes, enhancements and changes have been made in version 5.0 product update 1.

This update is essentially to resolve some issues from the initial release.

Check out the updates in the previous updates:

• See what’s new in the initial 5.0 Release

• IMAN-2429 – Sage300 – Adds support to create/update Orchid EFT Customer, Vendor and Employee Bank details.

• IMAN-2427 – Some styling fixups.
• IMAN-2425 – WebAPI – Alter/improve behaviour for job email auditing.
• IMAN-2424 – WebAPI – Alter/improve behaviour for job concurrency handling.
• IMAN-2423 – WebAPI – Fixes an issue where the throttle would not be applied to a licensed IMan without the WebAPI feature.
• IMAN-2409 & IMAN-2421 – Fixes several issues when fields are deleted or triggered when meta-data detects when a field is deleted.
  

  This also fixes an issue where some Readers would generate an Object reference error on opening.

• IMAN-2420 – WebAPI – Add missing Grafana dashboard template to installer.

The following fixes, enhancements and changes have been made in version 4.2 product update 5.

This update formalises compatibility with Sage300 2021, improves usability with a new transform setup screen and a several smaller improvements to the Sage300 and SageCRM connectors.

Check out the updates in the previous updates:

• Product Update 4
• Product Update 3
• Product Update 2
• Product Update 1
• See what’s new in the initial 4.2 Release

• Product Update 4 introduced a security fix covering all Xml handling (reading, writing, webservices and webservice lookups) to prevent external DTDs from being loaded and processed.
  

  You will need to find alternatives in the unlikely event you have integrations relying on IMan processing external DTDs (see IMAN-1954 in PU2).

• This also altered behaviour for CSV Readers and CSV Writers using tabs as delimiters.

• This version add compatibility with Sage300 2021.

• IMAN-2020 – File Writer (IO Controller) – Adds the ability to create directories when writing files if they don’t exist. Previous versions raised an error if the directory being written to needed to exist.
• IMAN-2018 – Sage300 – O/E Orders – Allows Active orders to be created from existing Standing orders.
• IMAN-2017 – This product update changes the styling and layout of the transform setup screens by replacing the existing tabs are the top of the screen with a newer control.
  

  

  This provides several benefits: improved handling & screen resizing; resolution of numerous bugs; more screen real-estate to the preview area; and a small performance improvement.

• IMAN-2007 – SageCRM – Improves general processing performance.
• IMAN-1999 – Sage300 – Add capability to create Product Plan Forecast Entries for Auto-Simply.
• IMAN-1992 – JPath – An improvement to allow IMan to consume JSON data where the outermost value is an array. In previous versions the outermost object had to be an object. We’ve also improved the examples to show how you can query this type of data.
• IMAN-1991 – ShipStation – New Connector!
• IMAN-1988 – Sage300 – I/C Adjustments – Import now allows cost adjustment to specific lots and serials.

• IMAN-2016 – Webservices – Fixes an issue where a new Reader (JSON, Xml, CSV) targeting a webservice would not refresh.
• IMAN-2015 – FTP – Fixes an issue when connecting anonymously to an FTP server.
• IMAN-2011 – Fixes an issue where the incorrect date format was being logged on Job end success.
• IMAN-2007 – SageCRM – Fixes an issue where Territory fields were not being handled correctly.
• IMAN-2002 – SageCRM – Fixes an issue where emails were not being updated correctly on person records. This also fixes an issue with SageCRM 2018 and later.
• IMAN-1996 – Webservices – Fixes an issue where Control Length was not being set on empty Post requests.
• IMAN-1994 – Sage300 – Auto Simply – Manufacturing Orders – Fixes several issues for handling updates and posting.
• IMAN-1993 – Sage300 – Auto Simply – Receipts & Issues – Fixes issues when posting transactions would cause underlying views to be closed prematurely.

The following fixes, enhancements and changes have been made in version 4.2 product update 4.

This fix makes a big (overdue) update has been made to the way errors are reported by any reader, writer or lookup using webservices.

This Product Update also introduces the ability to use Expando fields in the File Task.

Check out the updates in the previous updates:

• Product Update 3
• Product Update 2
• Product Update 1
• See what’s new in the initial 4.2 Release

• This product update introduces a security fix covering all Xml handling (reading, writing, webservices and webservice lookups) to prevent external DTDs from being loaded and processed.
  

  You will need to find alternatives in the unlikely event you have integrations relying on IMan processing external DTDs (see IMAN-1954 in PU2).

• CSV Readers and CSV Writers using tabs as delimiters should also be checked to ensure functionality (see IMAN-1980 below).

• IMAN-1981 – File Tasks – Can now use Expando Fields in the Destination Path. Coupled with the ability to the ‘Create Directory’ feature added in 4.2, this allows you to dynamically move/copy files to dynamically created directories.

  For example, categorised library or document file stores can use a File Move or File Copy Operations with a field such as a reference or customer id.

• IMAN-1977 – Webservices – Improves the messaging and capability for handling errors returned from any webservice interaction. Any erroneous response from a webservice is now extracted and formatted to show more meaningful errors.

  If the webservice responds with consistent error messaging, this feature adds a property to the Webservice Behaviour to specify the JPath or XPath to any error messages.

  If the message returned from webservice is either malformed or just plain text, IMan will fallback and attempt to extract the most meaningful message.

  Further information about webservice error handling and this feature can be found on the Webservice Behaviour.

• IMAN-1980 – Fixes handling of tab delimited CSV files on both the reader and writer. The delimiter stored in the IMan configuration file is now the escaped version as opposed to the actual non-Xml-compliant tab character. If any integration uses tab delimited CSV Reader or Writers, it is wise to check the integration functions after upgrading.
• IMAN-1979 – Fixes an issue with the 1, 2 & 3 integration licenses where a task added to an existing integration would cause the designer to cause an internal error.
• IMAN-1978 – Sage300 – Orchid – Bin Tracking – Adds missing capability to create Bin Tracking documents not tied to source documents.

The following fixes, enhancements and changes have been made in version 4.2 Product Update 3.

This Update fixes some key Webservices issues (stoppers!) and a couple of small Sage300 issues.

Check out the updates in the previous updates:

• Product Update 2
• Product Update 1
• See what’s new in the initial 4.2 Release

This product update introduces a security fix covering all Xml handling (reading, writing, webservices and webservice lookups) to prevent external DTDs from being loaded and processed.

You will need to find alternatives in the unlikely event you have integrations relying on IMan processing external DTDs (see IMAN-1954 in Product Update 2).

No enhancements this time, just fixes.

• IMAN-1974 – Sage300 – AutoSimply – Fixes an issue on Bill of Materials for Resources and Tools to be multiplied by Batch Size.
• IMAN-1972 – Webservices – Fixes several issues: when tracing enabled a closed stream error would occur, fixes handling of errors when Error Code paging is enabled.
• IMAN-1969 – Resolve NullRefrenceException for HTTP requests without paging.
• IMAN-1968 – Sage300 – Add missing Account Status field to G/L Account import.
• IMAN-1967 – Fixed Width Text Reader – Fixes issue where parent was not saving when pressing Apply.

The following fixes, enhancements and changes have been made in version 4.2 product update 2.

The update expands some internal webservices functionality required for connector development. The product update also adds AutoSimply Issues & Receipts to the the Sage300 3rd Party module/pack.

Check out the updates in the previous updates:

• Product Update 1
• See what’s new in the initial 4.2 Release

This product update introduces a security fix covering all Xml handling (reading, writing, webservices and webservice lookups) to prevent external DTDs from being loaded and processed.

You will need to find alternatives in the unlikely event you have integrations relying on IMan processing external DTDs (see IMAN-1954 below).

• IMAN-1943 – Internal Enhancement – Webservices – Improve functionality on JSONSteppableReader to allow multiple pages to be iterated on GetEntryList. This provides full paging capabilities for connectors.
• IMAN-1941, IMAN-1944, IMAN-1946 – Internal Enhancement – Webservices – Mark methods as virtual on the HttpIOController, JSONSteppableReader, JSONWriter classes to allow connectors to override behaviour.
• IMAN-1937 – AutoSimply – Add the ability to create AutoSimply Material Issues and Assembly Receipts.

• IMAN-1966 – Form Url Writer – Update/change icon from placeholder.
• IMAN-1964 – Transform Setup Window – Fixes long standing issue where save would need to be pressed twice to save transform id.
• IMAN-1963, IMAN-1965 – Sage300 – AutoSimply Manufacturing Orders – Reinstate after merge issue.
• IMAN-1962 – Sage300 – PJC Timecards – Add missing Transaction Date.
• IMAN-1961 – Fixed Width Reader – Fixes several issues with setup of hierarchical files: footer setting is now being respected when detecting record types; fixes/prevents crash when zero is entered as the record type length; improves messaging for erroneous setups; improves internal handling of setup; fixes an issue where invalid setups would require a new connector to be added.
• IMAN-1959 – Webservices – Fixes several issues surrounding rewrite/consumption of response following a JSON request.
• IMAN-1957 – Designer UI – Reinstates existing behaviour by returning the palette to the transforms after a transform is dropped onto the design surface. This aids job creation since the connector/arrow is found on the transforms palette.
• IMAN-1956 – Internet Explorer – Now prevents Internet Explorer from logging in.
• IMAN-1954 – General Xml Handling – Fixes security by preventing external DTDs being being loaded. This also prevents xml load failures from invalid external DTDs.
• IMAN-1953 – XmlReader – Fix Object Reference exception when there’s no XPath on a record.
• IMAN-1952 – 4.2 Styling – Forces refresh of styling for 4.2.
• IMAN-1950 – FTP Server Setup – Fixes an issue where longer passwords would be truncated.
• IMAN-1942 – Job Configuration Upgrade – Fixes/improves error handling in specific circumstances when upgrading corrupted (and older) job configurations.

The following fixes, enhancements and changes have been made in version 4.2 product update 1.

This update is essentially to resolve some issues from the initial release.

Check out the updates in the previous updates:

• See what’s new in the initial 4.2 Release

• IMAN-1934 – OAuth 2.0 – OAuth 2.0 now has the capability to include several new tokenized values which can be sent either as a header or body value. This change also allows the actual the headers on the request to be tokenized.

• IMAN-1936 – Http Header Setup – Fixes an issue with html characters (<, >, &) preventing the control from saving.
• IMAN-1934 – OAuth 2.0 Setup – Fixes several issues with the Test button for OAuth 2.0 setup.
• IMAN-1932 – Designer – Fixes/allows annotations to be forward compatible.
• IMAN-1931 – Sage200 Connector – Reinstates authentication method for 2015.
• IMAN-1930 – Webservice Behaviour Setup – Fixes an issue preventing the screen from opening.
• LIC-2 – Fixes an issue preventing licensing.