Curiously, the Label parameter in the ARTask file *is* the VUI name, but it has absolutely no effect on how aruser.exe opens the form. For example, I can be working in the "Read-Only" view of a form, and when I send it to a friend using right-click --> Send --> Form --> Mail Recipient, I get something like this:
[Shortcut] Label = Read-Only Name = Foo Form Type = 0 Server = snoopy Join = 0 But when my friend tries to open the shortcut, her aruser.exe doesn't necessarily open the Read-Only view. It simply opens the form using the default VUI. So it's pretty much just window dressing. (Or is it "view dressing"?) Having said all that, there's at least one fairly simple way to get an ARTask shorcut file to launch a form in a particular view. 1. Create an active link with two actions: (1) Open Window and (2) Close Window. (I used a Submit or Search window type for the Open Window action.) 2. Create an active link guide that calls the active link. 3. Send the active link guide to a user a shortcut. (File --> Send to --> User(s) as Shortcut) The reason for the Close Window action is if you simply call the Open Window action, the User tool will open the form in the default VUI, and then perform the Open Window action, leaving you with two open form windows. Fortunately, the subsequent Close Window action affects the first window and not the new window that was opened in action 1. Presumably, aruser.exe expects the Open Window action to be fired from an existing window -- I guess they didn't think you'd ever want to open a window out of thin air. Yes, I agree... The window flicker is a little annoying. (Note using an Open Window type of Dialog doesn't seem to work. Neither the root window nor the dialog window is closed by the Close Window action.) The ARTask shortcut that forces the User tool to execute the active link guide on start-up looks like this: [Shortcut] Name=XXX-Open-Foo-as-ReadOnly Type=3 Server=snoopy Through trial and error you can begin to see what the different Type values mean. It's unfortunate that we don't have a definitive spec for ARTask, but I don't think that's necessarily because they're keeping it from us. I suspect that ARTask is not very well understood even among Remedy's developers, which could explain why the admin tool creates them one way (with no spaces around the equal sign) and the user tool creates them another way (with spaces around the equal sign). --Tim ----- Original Message ---- From: Misi Mladoniczky <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, November 24, 2006 1:07:07 PM Subject: Re: [ARSLIST] ARTask parameters Hi Steve, I did a strings (cygwin) on ARTask.exe, and did not find anything suitable. In ARUser, you are not able to specify the VIEW to be used when you do a table-drilldown in a Table-field or a form is opened. This is determined by the default settings on the user. You can use an Active-Link that does a Window Open to specify a view, but this would not be readily available here. The only thing I can think of is to create an Active Link that triggers on Display or something like that, that checks the $VUI$ name and if the view is wrong, it performs a Window-Open and finally closes the first window... Ugly! Best Regards - Misi, RRR AB, http://www.rrr.se > Does anybody know if there is a way to specify a view within a ARTask > shortcut? Would like to open a specific request and control the view that > is opened. > > Tried using 'VUI' and 'View' with no luck. > > Thanks. > > Steve > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
