Page Comparison

{scrollbar}

There are three types of parameters that Action Sequence documents understand; inputs, outputs and resources.  Inputs and outputs are variables of a specific data type like string or property-map (see ADD LINK TO valid data types.)  Resources are similar to inputs except they specify a mime-type and  and path.  A default value cannot be specified for resources.  Typically resources represent large amounts of data like report definitions or images (see ADD LINK TO for valid resource types.) 

Parameters can come from four sources; runtime, request, session, global and default. 

...

Session and Global parameters can be used to provide secure filtering of data within the Action Sequence.  A session parameter gets initialized by executing an action sequence when the user logs onto the system.  The Action Sequence called upon login can be set up to perform a query using the user's login name in the where clause.  The result is stored in the user's session and is available to subsequent Action Sequences.  Global parameters are initialized when the system starts up and are available for all users.  See Using System Actions to Control Data Access for information on how to set up the filters and use them.

Here is an example if of the inputs section of an Action Sequence document:

<inputs>
   
    <region type="string">
            <default-value>Central</default-value>
   
        <sources>
   
            <request>REGION</request>
   
            <runtime>aRegion</runtime>
        </sources>
   </sources>     <default-value>Central</default-value>
    </region>
   
</inputs>

This example indicates that the Action Sequence document requires a parameter named region (case sensitive.)  When executed, the Runtime Context will first look to see if there was a parameter named REGION in the request.  If the Action Sequence was launched from a URL, and there was a parameter REGION=xxx specified, than this then the value (xxx) will  would be substituted for the region input.  If it doesndidn't find the parameter in the request, it will it would look in its own runtime data for a parameter named aRegion.  If it doesndidn't find it in the Runtime Context Data, the value Central will  would be used.  The Runtime Context always looks in the sources in the order in which they are specified and takes the default value last.  If no default was specified, then the Action Sequence would throw an error and return.  

There are two implicit parameters, instance-id and solution-id, that are always available and do not need to be specified as inputs or outputs.  They are the... well I'm sure you can guess what they are.

{scrollbar}