Element "zpro > ProcessForm > ExecuteCommand"
|
Element "zpro > ProcessForm > ExecuteCommand" |
|
|
ExecuteCommand element must be placed into a ProcessForm Element. It is used to define which processes will be executed when user clicks on the command.
Before setting the properties of this element, at least one ProcessDefinition Element must be existing within the ProcessForm. Setting the Properties
Before-Submit Function In this property you can define a Javascript function that supposed to be called just before the submitting the Process Form. The function receives the form object as the parameter can perform last minute tasks such as validation the input and it can cancel the submision of the form by returning false as the result. Validate Input Select "true" if you want that the input fields are validated before submitting the ProcessForm. The validation is performed only for the fields that are located in the ProcessBlock where the selected Process Definition Elements exist. Confirmation Request Message For some cases it is necessary to ask the user for confirmation before submitting the process form; for instance, before deleting a record. If a value is given into this property, it will be displayed to the user in the confirmation request dialog and the proccess form will be submitted only if the user confirms. Next Page (displayed when maxcc <= 4) (Accepts MScript) The name of the page to be displayed if the execution of the selected processes are successful. If the maximum completion code is <= 4, then the Process Manager assumes that the overall execution is successful and display the page specified in this property. The value for this property can be a page name or an URL. Please note that the next page value assigned with this property can be changed by the processes using MScript. The following MScript code will overrride the current next page definition. @set(_nextpage,'products')
Redirection with a GET Request (since MMAF v4.3) If nextPage value starts with "redir " definition then it has a special meaning. If that is the case then ProcessManager makes a redirection to display.doms service with a GET method using the provided parameters. Caution! Only the parameters defined here will be included in the GET request. Since the POST request and its parameters will terminate all request based memory storage (Variable Pool, and request ADOMs) will not be available in the new GET request. It should be thought that a brand new request is created when processing of the processes completed with the parameters defined here. Syntax: redir page-name[¶meter=value][¶meter=value][..][_rand=] (Accepts MScript) page-name
parameter
value
_rand=
Examples: redir %vof(PAGE_NAME)&ID=?&_rand= redir mppa/index&CUST_ID=@vof(v:CUST_ID)&_rand= redir lou/SGA/Details&ID=?&SGA_ID=@vof(p:SGA)&_rand=
Error Page (displayed when maxcc > 8) (Accepts MScript) The name of the page to be displayed if the execution of the selected processes are not successful. If the maximum completion code is > 8, then the Process Manager assumes that the overall execution was failed. The value for this property can be a page name or an URL. Please note that the next page value assigned with this property can be changed by the processes using MScript. The following MScript code will override the current error page definition. @set(_errorpage,'reservation_error')
Next Page After Error Page Enter the name of the page to be displayed after the error page is displayed. Warning Page (displayed when maxcc > 4 and maxcc <= 8) This is a hidden parameter and it is preset to the current page. If the maximum completion code is > 4 and <= 8 then ProcessManager displays the current page assuming that the user's input is not correct and he should be warned. Access Control This property is used to check if the current user has a sufficient authority to execute the command. See Access Control of Page for details. Execution Precondition If an MScript expression is defined in this property it is evaluated first and the command is executed only if the evaluation result is true. Process Manager Debug Level Assign a value between 1 and 3 to debug MoreMotion AF Process Manager. The debugs can be traced from the system console. The debug options can be set for the processes individually using the Process List property.
Click on [...] button of the property on the property editor to open Process List Editor.
Click on [+] button to add a row where you can select one of the process definition elements existing in the ProcessForm element.
You can add more process definition elements depending on your needs. Sub Processes If the selected process is a query process then you can insert sub-processes under it using the
Step Name This is an optional parameter. If you assign a step name to a process then you can use it in the Execution Precondition of the succeeding processes. For example if step name is given as update then the completion code of this step can be checked with _update_cc symbol. Reset The value of this field is meaningful when nested sub processes are used and It is used to reset the process defined in the current call definition. See more. Execution Precondition By defining expressions in Execution Precondition columns you can define preconditions for the processes to be executed. The expression defined for a process will be evaluated by the Process Manager first and if the result of the expression is true, only then the process will be executed. Record Filter The MScript expression defined with in this column is used as a process pre-condition for each ProcessRecord existing in the ProcessBlock. The expression is evaluated for each record and the process or the template is called for that record only if the evaluation result is true. See Built-in symbols that can be used in Execution Precondition and Record Filter Expressions
Debug You can activate the debugging functionality of the configured process classes by setting a value between 1 and 3 for this column.
|
button. You can change the level of a process using 
buttons.