← Creating Process Monitors

Using the Publishing Definition Type

The Publishing definition type allows you to publish content into a Report2Web catalog, which can be used as an archive. Content published into a catalog can also follow an approval workflow, where reports can be approved or rejected.

You specify the Report2Web Catalog, the Report Name, which is the name of the report within Report2web including its path, and the Source file. Optionally, you specify if the report requires to follow an approval workflow.

Specifying Files in the Source Field

You can specify files using the following syntaxes:

  • <step_name>, Job <n>:<file> - specify a chain process in a final state; the publishing job must be part of the same chain.
    • Example: Step 1, Job 1:stdout.log
  • Job <ID>:<file> - specify a process or chain process and the output
    • Example: Job 123:stdout.log
  • parent:<file> - specify the output file of the parent of the current process; note that the parent of a call in a chain is the step, and steps have no output.

Metadata

You specify Metadata that will be visible in Report2Web and which is used to describe and locate the document with ease.

Variables and Parameters

The following parameters are available:

NameDescription
Publish_Commentapproval comment
Publish_DeleteTemporaryFileShould the temporary file be deleted?
Publish_Statusapproval status

You specify variables like ${<variable_name>} and parameters like ${Publisher.parameters.<parameter_name>}

Variable NameData TypeDescription
${description}StringThe description of this process.
${file.index}NumberThe index of the file in the list of files.
${file.name}StringThe name of the file.
${finishtime}DateThe time when this process finished.
${jobdefinition}StringThe name of this process.
${jobid}NumberThe ID of this process.
${jobname}StringThe name of this process.
${jobowner}StringThe owner of this process.
${processserver}StringThe process server this process is running on.
${publisher.description}StringThe description of the publisher process.
${publisher.jobdefinition}StringThe name of the publisher process.
${publisher.jobid}NumberThe ID of the publisher process.
${publisher.jobname}StringThe name of the publisher process.
${publisher.jobowner}StringThe owner of the publisher process.
${publisher.processserver}StringThe process server the publisher process is running on.
${publisher.queue}StringThe queue the publisher process is running on.
${publisher.requestedstarttime}DateThe requested start time of the publisher process.
${publisher.starttime}DateThe start time of the publisher process.
${queue}StringThe queue the process is running on.
${requestedstarttime}DateThe requested start time of this process.
${starttime}DateThe start time of this process.

Example

The following example illustrates the use of Variables and for metadata:

<reportmetadata>
   <pubprofilename>${Publisher.parameters.Profile}</pubprofilename>
    <docproperties>
        <description>${Description}</description>
        <title>${JobDefinition}</title>
        <subject>${Description}</subject>
        <author>${JobOwner}</author>
        <date>${StartTime}</date>
        <keywords />
    </docproperties>
</reportmetadata>
← Creating Process Monitors