Kevin, Another approach is to do a push to the current record and include a "signal" that allows the modify filters to "branch" and call a filter guide and not do the full Modify processing.
You add a display only field that you set to a value like "FinishSubmitLogic". Then a Modify Filter that checks that filed for that value and calls a guide then does a GOTO 1000 to skip the rest of the modify filters. The only other thing you need is to add a filter on submit that does a push to the current form where '1'=$1$ AND make sure that filter IS phased. (That way you know the Request ID value 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) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 2/27/07, Axton <[EMAIL PROTECTED]> wrote:
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 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
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
