What about doing your check with Active Links instead?  That way, you can stop 
the save action before it gets to the server and change the status of the 
ticket in the display back to what you want.

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Larry Barnes
Sent: Thursday, March 11, 2010 9:58 AM
To: arslist@ARSLIST.ORG
Subject: Workflow newbie

**

Good morning,

I have created 2 Filters that run against any non-Standard Change Request.

  The first filters executes on "Modify" and the Run If statement is:  ( 
'Change Request Status' > "Planning In Progress") AND ('Change Type' != 
"Standard Change")

  If true it reads a filed from another from, "CHG:Associations" with a Set 
Fields If statement:
      ( 'Request ID02' = $Infrastructure Change ID$) AND ( 'Request Type01' = 
"Configuration Item")

     A temp filed called: z1D CI_RelationshipCheck is set to the value found in 
the $Request ID02$ field.


The second filter runs after the first (execution order is 1 higher) and also 
Executes on "Modify"
  The Run if statement is:
      ( 'z1D CI_RelationshipCheck' =  $NULL$ ) AND ( 'Change Request Status' > 
"Planning In Progress") and ('Change Type' != "Standard Change")


All seems to work well,  if a CI has not been related to the ticket then an 
error message pops up on the screen.

What I'm trying to do, and can't figure out is,

* Once the ticket is modified the Change Request Status Field gets changed from
  "Planning In Progress" to "Scheduled for Review"
* If there is no related CI then I want this field changed back to "Planning In 
Progress".
* The user is required to select the "Next Stage" option in the Progress Flow 
bar in
  order to have the status changed back.

             (This is what I'm trying to avoid having the user do)

Can this be done with in the second filter?  This is where I'm stuck, I would 
like to make this a better process than selecting the Next Stage option twice 
to reset this field value.



I come form the old days of programming and having requiring the user to select 
the Next Stage option twice to reset the Status filed seems like poor 
programming.

Thanks for your time in looking at my dilemma,

Larry B.
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_


 NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.



_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to