Idoc Script Application 2-11
For example:
■
You can use Idoc Script tags in the query results page definition to specify the contents of each row in a search results table.
■
To set the search results to return all content items up to 7 days, you could define the search query to be:
dInDate dateCurrent-7
■
To define a report that returns results based on the current user, you could define User Name is UserName as part of the report query expression.
For more information, see Oracle Fusion Middleware System Administrators Guide for Oracle Content Server.
2.3.6.3 Batch Loader
In the Batch Loader, you can use Idoc Script in a mapping file, which tells the BatchBuilder utility how to determine the metadata for file records. For more
information, see Oracle Fusion Middleware System Administrators Guide for Oracle Content Server.
2.3.6.4 Archiver
In Archiver, you can use Idoc Script in the following areas:
■
Export query values. For example, to archive content more than one year old, you
could use dateCurrent-365 as the Release Date value.
■
Value map output values. For example, to set the expiration date one week in the
future for all imported revisions, you could use dateCurrent7 as the Output Value.
For more information, see Oracle Fusion Middleware System Administrators Guide for Oracle Content Server.
2.3.6.5 System Properties
When you set values in the SystemProperties utility, in the Admin Server, or in the Local Configuration or Shared Configuration screens of the Inbound Refinery, you are
actually setting Idoc Script configuration variables. For more information, see the documentation for these applications.
2.3.6.6 E-mail
You can use Idoc Script to customize the subject line and body of a notification e-mail. For example:
Hello, UserName. Content item dDocName requires your review.
2-12 Oracle Fusion Middleware Idoc Script Reference Guide
2.4 Special Keywords
The following keywords have special meaning in Idoc Script:
2.4.1 Keywords Versus Functions
Oracle Content Server pages use the include and exec Special Keywords
and the inc and eval
Functions extensively. This section describes the differences between
these commands and gives examples of how to use them. The include and exec keywords are standalone commands that operate on defined
parameters, but cannot take a variable as a parameter. The inc and eval functions have similar purposes, but they can take variables for parameters, which enables you
to dynamically create Idoc Script code depending on the value of the variables.
The following sections describe these keywords and functions in detail:
■
Section 2.4.1.1, exec Keyword
■
Section 2.4.1.2, eval Function
■
Section 2.4.1.3, include Keyword
■
Section 2.4.1.4, inc Function
Keyword Example
Description
active active.variable
Retrieves the value of the specified variable from the DataBinder, searching in the following default order:
1.
Active ResultSets
2.
Local data
3.
All other ResultSets
4.
Environment Does not send an error report to the debug output if
the variable is not found. local
local.variable Retrieves the value of the specified variable from the
local data. Does not send an error report to the debug output if the variable is not found.
env env.variable
Retrieves the value of the specified variable from the environment settings. Does not send an error report
to the debug output if the variable is not found. exec
exec expression Executes an expression and suppresses the output
does not display the expression on the page. In earlier versions of Idoc Script, the exec keyword
was required to suppress the value of any variable from appearing in the output file. In the current
version, the exec keyword is needed only to suppress an expression from appearing in the output file.
include include
ResourceName Includes the code from the specified resource. For
more information, see Section 2.3.1, Includes.
super include
super.include Starts with the existing version of the include code.
For more information, see Section 2.3.1.2, Super
Tag.
