Kevin,
Uh... a Push action in a filter that fires on Submit should have the
Entry ID value to be able to push to the target form.
However, if you make that filter non-phased then it will NOT have the value.
Is it possible that for submit you have made this push action non-phased?
--
Carey
and their is a record on the DB to push to.)
However, sometimes these things are actually better dealt with via
other processes. Can you be specific about what your doing and why you
think you need the 'Entry ID' value during Submit Filters?
--
Carey Matthew Black
Remedy Skilled Professional (RSP
System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black
Sent: Wednesday, February 28, 2007 3:45 AM
To: arslist@ARSLIST.ORG
Subject: Re: Entry ID on Submit
Kevin,
Another approach is to do a push to the current record and include a
signal that allows the modify
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin Thornley
Sent: Wednesday, February 28, 2007 10:59 AM
To: arslist@ARSLIST.ORG
Subject: Re: Entry ID on Submit
So I think it's time for me to take a new approach and solicit suggestions
Subject: Re: Entry ID on Submit
So I think it's time for me to take a new approach and solicit
suggestions on how others would accomplish this goal.
So here goes:
I have a schema that is setup as a parent/child based on the status
field. On this schema is a count field used for counting all
All
I need to use the entry id on some filters that execute on submit. The
problem is that the entry id isn't committed yet. I want to remember
that there is a way to make this happen by using the '! naming
convention to control the firing order.
Help
Kevin
Nope, generate a unique value using a guid/instance id. See the
special run process commands section of the basic/workflow guide.
Axton Grams
On 2/27/07, Kevin Thornley [EMAIL PROTECTED] wrote:
**
All
I need to use the entry id on some filters that execute on submit. The
problem is that
7 matches
Mail list logo