Validate SRF Inputs

Discussion created by govindaraj on May 21, 2013
Latest reply on May 23, 2013 by Tom_Kouhsari

Like • Show 0 Likes0
Comment • 4

Hi All,

How can i validate the SRF inputs using Javascript?

For Ex, if request_id or request_item_id is empty, i need to exit and go to the Abnornam stop. Any thoughts?

Thanks,
Govindaraj

Outcomes

4 Replies

Tom_Kouhsari May 21, 2013 8:55 PM
govindaraj wrote:
Hi All,

How can i validate the SRF inputs using Javascript?

For Ex, if request_id or request_item_id is empty, i need to exit and go to the Abnornam stop. Any thoughts?

Thanks,
Govindaraj
With 4.x, you can go some pretty advanced validation right in the SRF. Or if you want, you can let the SRF start the process and then do whatever validation you need in any location that javascript is used (pre-execution, post-execution, Run Javascript operator, Evaluate Expression operator, etc) and take a path to abnormal stop based on the results.

Thanks,
Tom
Like • Show 2 Likes2
Actions
- govindaraj @ Tom_Kouhsari on May 23, 2013 12:37 PM
  Thanks Tom for the information. I am current using the Run Javascript operator. Is there a way we can use like "exit 0" or "exit 1" to exit from the operator and go to the abnormal stop?
  Like • Show 0 Likes0
  Actions
  - Tom_Kouhsari @ govindaraj on May 23, 2013 1:19 PM
    govindaraj wrote:
    Thanks Tom for the information. I am current using the Run Javascript operator. Is there a way we can use like "exit 0" or "exit 1" to exit from the operator and go to the abnormal stop?
    You're welcome. There are two approaches to doing routing decisions:
    1) Use the Evaluate Expression operator. This operator has two main uses. If you keep the Refresh Rate set to 0, all it does is evaluate the Expression field and succeed or fail based on whether the expression is true. So you could put Process.requestId == "" in for the Expression and if requestId is blank, the operator will succeed and take the success (green checkmark) path and if requestId is not blank then it will take the failure (red x) path.
    
    2) Use Custom Results. You can add Custom Results to any operator. Just right click the operator and select Custom Result from the context menu. There you can define the condition that must be true in order for that path to be taken. This option also allows you to have more than two ports/paths and also allows you to take multiple paths at the same time (if that's what you design). BTW, in general you want to use either the standard success/fail ports OR Custom Result ports. In most cases you do not want to mix the two.
    Like • Show 3 Likes3
    Actions

samuel.leibowitz May 22, 2013 3:17 PM

If you're still on 3.1 you can still do this pretty trivially in a calculation operator.

In the main source code for the calc operator:

Process.SetupFailures = [];
if( ! myValidationFunction(Process.someVariable)) { Process.SetupFailures.push("Hey, Process.someVariable is messed up.") }

In post-execution code

if (Process.SetupFailures.length > 0)
{

Process.FailureMessage = "The following failures occurred attempting to process this request:\n\n"

for(i = 0; i < Process.SetupFailures.length; i++) {


Process.FailureMessage += "* " + Process.SetupFailures[i] + "\n";

}

Process.FailureMessage += "\nPlease abort this process, correct the request form, then resubmit this request.";

setOperatorStatus("Failure", 4, Process.FailureMessage);
}

Alter as necessary to make sure that the operator actually sees this message.

Actions

Validate SRF Inputs

Outcomes

Related Content

Recommended Content