Brian, We are seeing the exact same behavior in 7.6.04, where the workflow will run and get a "cannot connect to ARServer" (something like that) error and will fail at that step. Exporting the definition as XML shows that the serverName value is being set to "*" for some unknown reason. The only way to correct it is to remove and re-add the workflow action, which changes it to "@" in the definition. This is very concerning and we have not found a better workaround yet. We will be submitting a support case on it, but it's less critical than others we have open on this version right now.
Regards, Tony Cesaro [email protected] http://amcpu.org On Wed, Apr 20, 2011 at 4:36 PM, Brian Goralczyk <[email protected]>wrote: > ** Quiz question for those smart than I. > > I ran into an issue where our server is using the variable * for > servername. I exported the active links into an XML file and found the > value: > <serverName>*</serverName> > Which is not what I expected to see. > <serverName>@</serverName> is what I expected to see. > > We are using 7.6.4 and just completed a conversion to custom on the > workflow. I wasn't to concerned until I pulled all the A/L's and came up > with over 5000 actions that use the *. I don't want to do a mass update and > re-import them, although I could, unless it is a serious problem/issue. > > Has anyone else seen this? > > Any suggestions or advice? > > Thanks, > > Brian Goralczyk > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
