I love the new interface in 3.1.1, great usability improvements John. One thing that I noticed which I think has been there all along is that if a filter qualification used the TR or DB prefix on a field name that is not represented in the documentation.
ARInside shows: 'EMPL_STATUS_yang' != 'EMPL_STATUS_yang' Filter qualification: 'EMPL_STATUS' != 'DB.EMPL_STATUS' I was investigating some custom workflow and when I saw that qualification on the ARInside page I was puzzled as to why someone would use that in a qualification (or even how that could ever be true for that matter). When I opened the filter it was using the DB prefix as shown above. Is this a known issue that I missed? -Rick From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Luthgers, John Sent: Monday, September 01, 2014 7:14 AM To: [email protected] Subject: ARInside 3.1.1 released ** Hello List, today I’m announcing the release of ARInside 3.1.1. The 3.1.x version focuses on redesign of the documentation layout and more dynamic functionality. Currently only the schema page is redesigned but everything else will follow and will receive further improvements. And it has updated support for ARS version 8.1. You could find the download and the changes of this version at the ARInside website (http://arinside.org). -John- _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
