Release Notes

Release Notes: RETS Connector Version 1.0.3.3

28777 - RETS Connector needs to work with FNIS server
Enhancement: We are continually improving the ability of RETS Connector to connect to non MarketLinx RETS servers. As issues arise, these are corrected.
29288 - RETS Connector: Metadata Browser
Enhancement: The Metadata Browser is a tool that allows you to visually explore and inspect the entire RETS metadata hierarchy within RETS Connector. This tool is extremely useful in troubleshooting metadata issues and in understanding precisely what data elements a RETS server is exposing to its client applications.
25972 - RETS Connector: Hourly and Monthly tasks display their schedules oddly.
Enhancement: Improved the readability of the display of scheduled tasks. This issue was reported by QA.

27627 - RETS Connector Settings are not matching up after initial loading.
BUG: Reported by QA. Corrected inconsistency in search criteria summary display.
28558 - RETS Connector Not able to enable the UI section of the Notifications TAB.
BUG: Email notification configuration has been fixed and is now described in the help file.
29209 - RETS Connector: Enhancement Request for All Data Option
Enhancement: This enhancement was requested by end-users. In order to avoid search errors caused by restricted data fields in RETS Pro, we are providing the ability to select all available data elements from RETS Connector.
27708 - RETS Connector: creating multiple successful logins when running queries.
BUG: Reported by QA and by Development. Successful Login and Unsuccessful Login statistics were not accurately tracked in RETS Pro reporting. This issue is resolved in conjunction with RETS Pro II HF 3.
29914 - RETS Connector: Slow rendering of lookup lists
Performance Improvement: Lookup lists with a large number of entries took a long time to render. This has been corrected.
29587 - RETS Connector changing fields after bad data alert and reset error.
BUG: Corrected an application reset error that occurred under specialized circumstances. This issue was identified within development and not reported by the end-user.