|
<< Click to Display Table of Contents >> Navigation: General Functions > Configuring the MIE (Programmer's Guide) > Portal Design > Request Portal Design (Programmer's Guide) > Template Construction > STEP<n>-AREA<m> > Special Merge Input Tags |
The Request Portal will calculate certain special case fields. The calculated value will then be returned with the HTML when the page is rendered, and may be referenced by later pages or by javascript from within the document itself. The field must be placed somewhere on the Request Portal template using the [%<iid>,Input,%] merge tag. (Notice the substitution of [% and %] for {% and %} when using merge tags in a Request Portal template.)
The following special case fields are available to be used with merge tags. If encountered the value of the variable will be set based on the defined action that is taken:
Variable |
Action Taken |
SRPAppEmail550 |
If encountered, acts as a trigger that causes a determination of the approver. The system setting SLMRequestApproverQuery will be used to determine how the lookup of the approver will be performed. If the setting is COST CENTER, then the approver will be looked up using the values that are populated (requestor's email, cost center, organization, or department) using the WFdataApprovers table. If the setting is CONTACT, then the lookup is performed using the requestor's email via the dataContactsApprovers table. If the setting is COST CENTER and the first query returns no records, then the additional WHERE clause syntax contained in the system setting SLMRequest2ndQuery is added to the requestor's email address to form a new WHERE clause to perform a 2nd query of the WFdataApprovers table. In all cases the returned records are ordered by spend limit and the first record to have a spend limit over the amount of the order will be selected. If a matching record is found, the approver's name and email are returned and automatically filled in if those fields are found in the collection of fields on the current SRP Gen II template. |
SRPReqCatnosToApprove550 |
If encountered, will populate the variable with a comma delimited list of ReqCatNo values from the current Shopping Cart that require approval (if any). |
SRPReqCatNosInCart550 |
If encountered, will populate the variable with a comma delimited list of ReqCatNo values from the current Shopping Cart. |
SRPReqEmail550 |
If encountered, acts as a trigger that causes a lookup of the requestor via the dataContacts table using the ctNo value (primary key value). Usually a drop-down is presented to select the requestor and that drop-down returns the ctNo value. This lookup is then used to populate the user's name and email address fields, if they are present on the Request Portal template. |
SRPDescriptionsToApprove550 |
If encountered, will populate the variable with an HTML-formatted list of Request Catalog item descriptions from the current Shopping Cart that require approval (if any). Each item on the list is separated by an HTML "<br>" break, and each item contains the item description from the Request Catalog. |