I believe I have it almost working. The only problem I have left is if a user opens an instance from a results list, it opens a blank form in the in the view defined in the AL. I expected that it would open the ticket in the defined view, but it appears to want to open the ticket in the default view, which fire my AL, which open a blank form in the alternate view. Arggg.
Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 205-226-1805 Cell: 205-288-9140 SoLinc: 10*19140 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing Sent: Monday, March 10, 2008 1:34 PM To: [email protected] Subject: Re: Forcing Different Form Views To see what the VUI keyword is returning you could use a message box with that keyword as the text, would tell you what to look for in your run-if statement -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mayfield, Andy L. Sent: Monday, March 10, 2008 12:17 PM To: [email protected] Subject: Re: Forcing Different Form Views The $VUI$ keyword says its the "Label of the form view displayed in the active window". Would you use something like $VUI$ LIKE "Default Admin View"? I have tried this, but it does not seem to be working. Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 205-226-1805 Cell: 205-288-9140 SoLinc: 10*19140 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing Sent: Monday, March 10, 2008 12:43 PM To: [email protected] Subject: Re: Forcing Different Form Views About the easiest way I would prevent loops would be to only file the AL, if the view I'm trying to open isn't the one opening...you would do that with the $VUI$ keyword (that's what it's called, right?), and I personally would use GROUPID instead of GROUP, because of the age old problem with groups having similar names, or groups who's name is a subset of another's -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mayfield, Andy L. Sent: Monday, March 10, 2008 10:57 AM To: [email protected] Subject: Re: Forcing Different Form Views I believe this will work well for if I can figure out a couple things. First, if I fire on Window Open, how do you keep it from getting in a loop? I seem to be crashing the WUT when I try it with Open Window; After Submit works fine. Second, can anyone help me with the syntax for using the making sure the user belongs to a specific group? I assume you utilize the $GROUPS$ keyword, but I'm not getting the results I expected thus far. Thanks, Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 205-226-1805 Cell: 205-288-9140 SoLinc: 10*19140 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing Sent: Monday, March 10, 2008 11:04 AM To: [email protected] Subject: Re: Forcing Different Form Views You could write workflow that fires on window open that has whatever qualifications you want, that will open the window again in the view you want, and close the previous window, or you could create different entry points that open the form in different views, and only give permissions to the proper groups -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mayfield, Andy L. Sent: Monday, March 10, 2008 9:58 AM To: [email protected] Subject: Forcing Different Form Views Is there an easy way to have a form open in different views based on group membership? This is specifically through the WUT. We do not currently use the web-tier. I've been reading through the documentation and so far have not seen that specific question covered. ARS 7.0.01 Windows 2003 MS SQL Thanks, Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 205-226-1805 Cell: 205-288-9140 SoLinc: 10*19140 ________________________________________________________________________ ____ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ ____ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ ____ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
