I just tested a new button/AL created in Dev Studio p2 on a ARS 7.5 p2 server. The dialog worked as expected. I tested it with both IE 8 and Firefox 3.5.2 against both MT 7.1 and MT 7.5. One MT server (7.1) is Tomcat 5.5.26 with an Apache 2.2 front end and the other MT (7.5) is just Tomcat 5.5.27.
Let me know what you find out. Jason On Mon, Sep 7, 2009 at 7:26 PM, Jason Miller <[email protected]> wrote: > It was all developed in 7.1 with the Admin Tool. The def was exported > using the Admin Tool and imported into 7.5 using the Dev Studio. I'll > create a quick Open Window as a dialog action in ARS 7.5/Dev Studio and see > if it behaves correctly. > > Jason > > > On Mon, Sep 7, 2009 at 4:48 PM, Joe D'Souza <[email protected]> wrote: > >> ** Hi Jsaon, >> >> Thanks for your quick response. >> >> Was the workflow that called your dialog box, created using the Dev Studio >> 7.5? Or was it a piece of workflow that was developed pre 7.5 upgrade using >> older versions of the Admin Tool? >> >> I have to test my stuff a bit more - I didn't quite have too much time >> left on my side when leaving work on Thursday but I'm pretty certain I had >> the right options selected on my Open Window option. I'll know a little >> more when I have a little more time to test my code. >> >> Joe >> >> -----Original Message----- >> *From:* Action Request System discussion list(ARSList) [mailto: >> [email protected]]*on Behalf Of *Jason Miller >> *Sent:* Monday, September 07, 2009 5:47 PM >> *To:* [email protected] >> *Subject:* Re: ARS 7.5 Mid-tier Dialog boxes.. >> >> ** Hi Joe, >> >> I did a quick test with IE 8 and Firefox 3.5 against a 7.5 ARS/MT. The >> dialog popped up and I was not able to click on the main form in the >> background. With IE the main form darkened, with Firefox the main form was >> black and I could no longer see the fields (I have seen reports of this on >> the list before). >> >> Interestingly enough the main form layout is all messed up in the 7.5 MT, >> all of the fields are listed in one column down the left of the form. Our >> production MT is still 7.1 and using the 7.1 MT server the form layout is >> perfect (multiple rows, vert Nav bar on left, etc). I flushed the cached on >> the 7.5 MT without any change. This form was designed on a 7.1 ARS/Admin >> Tool and then imported into 7.5 ARS using Dev Studio. I am not sure that >> should make much difference since it works fine in the 7.1 MT. >> >> Jason >> >> On Mon, Sep 7, 2009 at 12:48 PM, Joe D'Souza <[email protected]> wrote: >> >>> ** I am on ARS 7.5 Patch 2 (ARS. Mid-Tier and the Development Studio >>> client) and I use IIS 6 as the Web Server on Windows 2003 and Tomcat >>> 5.5.25 as the Web Servelet engine. >>> >>> I am yet to investigate this in greater details but this is what I >>> noticed before breaking off for this long-ish weekend. >>> If I open a Dialog Box on the Mid-Tier client, (all workflow to do this >>> was defined using the 7.5 P2 client), the parent window from where the >>> Dialog Box was called from, does not get 'grayed out' as a background >>> window, and I can click into it.. >>> >>> I am yet to investigate this in details to check if this functionality >>> works correctly if developed in 7.1 and then upgraded to 7.5. >>> >>> Here is what I plan to do as soon as I get to work this coming week. I >>> intend taking a XML definition file of the Active Link to see what I see in >>> the open window action options in the definition.. I have a gut feeling that >>> somehow, I will see the wrong option there. From the development >>> studio interface I have already verified that I have the 'Dialog' window >>> type selected, and not Search or whatever.. Just for kicks I also intend to >>> set a temp field to $OPERATION$ and see what operation the Mid-Tier thinks >>> it has to perform... >>> >>> I was just wondering if any of you have experienced this behavior as >>> well?? I was planning to export that active link and import it into a test >>> 7.1 system and check on what I see there and if the definition looks bad >>> there, then correct it there and then import it into the later version and >>> see if it fixes anything.. >>> >>> Joe >>> >>> PS: I found this strange behavior towards the later part of my last day >>> at work last week, so didn't have the time to check if it worked on the User >>> Tool. Anyways this application that I am building will specifically be used >>> from the web interface, so even if it does work on the User tool I cannot >>> really use that as a workaround until a fix is found. However I will verify >>> if it does work from the User interface just for kicks.. >>> >> _Platinum Sponsor: [email protected] ARSlist: "Where the Answers >> Are"_ >> > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
