George, sure this problem is related to action 'set fields'? We have Al's only 
running Open window and we have to resave the al to get it to work ..for a 
while .../L ars

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of George Barsan
Sent: Thursday, September 07, 2006 11:37 AM
To: arslist@ARSLIST.ORG
Subject: Re: AL stopped working (no changes on AL)


Hi David,

I removed all fields from the set field and added them one by one..
The one causing the problem is the field SelectionCriteria which I use
later on as external qualification for the open window. The strange
thing is that it stopps not only the open-win AL firing next, it
blocks all open-win AL's running behind that form (even though it
doesn't run there)...

I tried the following combinations for SelectionCriteria:
  "( $NumericCaseID$ = 'NumericCaseID')"  // as used in another AL and
working fine there
  "$NumericCaseID$ = 'NumericCaseID'"
  "$NumericCaseID$ = 1"
  "'NumericCaseID' = 1"
  1 = 1
  1 = 2

None of them worked: the AL processing stops as described without any
error message.

Please also note that if I change the qualification to something
invalid (i.e. "$NumericCaseID$ = 'XXNumericCaseID'" or
"$XXNumericCaseID$ = 'NumericCaseID'" ARS correctly shows me a "There
was a problem expanding the EXTERNAL qualification" error message).

"If no requests match" is set to default message.

Any ideas would be greatly appreciated..

Many thanks,

George



On 9/6/06, David Sanders <[EMAIL PROTECTED]> wrote:
> Hi George
>
> Is the set fields action before the window open building a qualification for
> the report?  What are your settings in the open window to report action in
> the No Requests Match area?  If your qualification returns no matching
> records and you have your options set to 'Do Not Show Any message' and
> 'Suppress empty list', then the report window will just not open.
>
> Try setting the No Match options to 'Show Default Message' and see if that
> gives any clues.
>
> HTH
>
> David Sanders
> Remedy Solution Architect
> Enterprise Service Suite @ Work
> ==========================
> ARS List Award Winner 2005
> Best 3rd party Remedy Application
>
> tel +44 1494 468980
> mobile +44 7710 377761
> email [EMAIL PROTECTED]
>
> web http://www.westoverconsulting.co.uk
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of George Barsan
> Sent: Wednesday, September 06, 2006 5:17 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: AL stopped working (no changes on AL)
>
> No, not yet - but I'm going to do that..
>
> What I tried to do is to separate the actions from one large AL into 3
> smaller ones. The funny thing is, that I ended up with an
> open-window-AL (let's call it ReportInternal), for which I have a
> handy def file and it works fine. However, I need a set fields action
> running in front of it. I had two ideas:
>
> 1) I tried to add it to the ReportInternal-AL => open window fails
> 2) I tried to create a separate AL (called GetReportData) running with
> a lower order => open window fails
>
> Importing GetReportData-AL messes up all open window actions even in
> other AL behind that form, although they are running on totally
> different conditions. As soon as I delete the AL GetReportData, the
> open window actions are working again..
>
> Next, I exported both AL's as XML and copy & pasted the missing set
> field action in an editor and import the new XML.. Same result => open
> window fails :(
>
> I guess that there is a relationship between the set-field and the
> open window action... However, I've ran out of ideas..
>
> George
>
> On 9/6/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > George, have you checked the .arf files in the Home Folder on the clients,
> contains the al defintions I know, maybe a difference when the al is not is
> working and when it is working? Something corrupt in the arf file? /L ars
> >
> > -----Original Message-----
> > From: Action Request System discussion list(ARSList)
> > [mailto:[EMAIL PROTECTED] Behalf Of George Barsan
> > Sent: Wednesday, September 06, 2006 4:53 PM
> > To: arslist@ARSLIST.ORG
> > Subject: Re: AL stopped working (no changes on AL)
> >
> >
> > Hello Joe,
> >
> > Yep, the group names and ID's are equal.. We used a DB dump and
> > re-import to duplicate production to dev and only removed customer
> > related data (names, addresses & co)..
> >
> > George
> >
> >
> > On 9/6/06, Joe DeSouza <[EMAIL PROTECTED]> wrote:
> > > **
> > >
> > >
> > > Very basic question... Have you checked if the permission groups on both
> the
> > > dev and prod instances are identical - both group names and their ID's
> > > should be the same...
> > >
> > > Joe D'Souza
> > > Remedy Developer / Consultant,
> > > BearingPoint,
> > > Virginia.
> > >
> > >
> > >
> > >
> > > ----- Original Message ----
> > > From: "Kemes, Lisa" <[EMAIL PROTECTED]>
> > > To: arslist@ARSLIST.ORG
> > > Sent: Wednesday, September 6, 2006 9:15:27 AM
> > > Subject: Re: AL stopped working (no changes on AL)
> > >
> > >
> > > I had an AL just stop working all of the sudden and what I had to do was
> > > delete it and then re-import the AL from the Prod server.  Sometimes
> > > AL's get corrupted.  Now my AL has no more problems on my Dev server....
> > >
> > > If this does not work, at least it only takes a couple of minutes to
> > > do....
> > >
> > > Hope this helps
> > >
> > > Lisa
> > >
> > > -----Original Message-----
> > > From: Action Request System discussion list(ARSList)
> > > [mailto:[EMAIL PROTECTED] On Behalf Of Nyall McCavitt
> > > Sent: Wednesday, September 06, 2006 8:35 AM
> > > To: arslist@ARSLIST.ORG
> > > Subject: Re: AL stopped working (no changes on AL)
> > >
> > > Hi,
> > >
> > > Just a thought.
> > >
> > > Have you defined the Report Server option in the User Tool to point to
> > > the dev server. If so, does the report exist on the Report form on dev
> > > server?
> > >
> > > If I have misread this problem then please ignore this.
> > >
> > > Thanks.
> > >
> > > Nyall
> > >
> > > George Barsan wrote:
> > > > Hi Tim,
> > > >
> > > > Thanks for the quick answer. The DEV environment is a full copy of the
> > >
> > > > production, all forms exist there as well (although containing test
> > > > data!).
> > > >
> > > > The second AL having the same problems does the following actions:
> > > >
> > > >  0 push fields (update existing request in another form)
> > > >  1 set fields from another form
> > > >  2 open window (yep, that's the one!)
> > > >  3 set fields from another form
> > > >  4 set field locally
> > > >  5 set field locally
> > > >  6 set field locally
> > > >  7 commit changes
> > > >  8 close window
> > >
> > > ________________________________________________________________________
> > > _______
> > > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
> > >
> > >
> ____________________________________________________________________________
> ___
> > > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
> > >  __20060125_______________________This posting was
> > > submitted with HTML in it___
> >
> >
> ____________________________________________________________________________
> ___
> > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
> >
> >
> ____________________________________________________________________________
> ___
> > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
> >
>
> ____________________________________________________________________________
> ___
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org

Reply via email to