Manjari,
Use workflow to build your logic. Put a filter on
survey form that will check to make sure ticket number
exists in your ticket form, else throw error.
Alternative:
Generally, when building an interface like this one, I
like building an "interface form", which would be very
similar to the form being submitted to. Then you can
add code on this interface form to validate the
incoming request and do whatever you want, all the
power of ARS available to you. This is cleaner than
adding code to the main form (survey, in your case),
especially if your validation logic is complex.
--- "Shrestha, Manjari R."
<[EMAIL PROTECTED]> wrote:
> Hello List,
>
>
>
>
>
> I have a .Net application which sends an e-mail
> template once the
> Customers (who do not have access to remedy)
> complete the Survey to
> E-mail Engine. I am using a submit action in the
> template. Is there a
> way to put in a qualification in the submit template
> that will see if
> the Request ID for the ticket exists and if it does
> then only it will
> push in the values? Or is there a workflow I can
> create to get the same
> result. I asked the Support and they informed me
> that the submit action
> does not have any such capability. Right now the
> problem I am facing is,
> I am sending the Request ID for the ticket but if
> someone changes the
> Request ID, it will still submit the survey to the
> survey form, which is
> scary. Please advise.
>
>
>
> Thanks!
>
> Manjari
>
>
>
_______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at
> www.arslist.org ARSlist:"Where the Answers Are"
>
____________________________________________________________________________________
Check out the hottest 2008 models today at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
