Redwood Documentation

Product Documentation

 

›Action Rules

Finance AutomationFinance Automation Reference

Introduction

  • Introduction

Template And Parameter Maintenance

  • Close Template
  • Process Lists in Orchestrator
  • Workflow Templates
  • Templates
  • FCc Templates

Balance Sheets

  • Balance Sheet Certification
  • BSC Installation
  • BSC Process Definitions
  • BSC Rules

Enhancements

  • Enhancements
  • Journal Extensions
  • Journal Definitions

Processes & Subprocesses

  • Process Definitions
  • Generic Loop
  • General SAP Process Definitions (Abap Run)
  • General SAP Process Definitions (Mail)
  • General SAP Process Definitions (Batch Input)
  • General SAP Definitions
  • Generic and Infrastructure Definitions
  • Utility Process Definitions
  • FPA specific Process Definitions
  • FCc specific Process Definitions
  • EBS specific process definitions
  • SAP Functional Process Definitions
  • Generic SAP Synchronization Process Definitions
  • Bulk Data Processing

Customizing

  • Customizing Redwood Finance Automation
  • Redwood Finance Automation Application Customizing FPA flavor
  • Redwood Finance Automation Application Customizing FCc Flavor
  • Redwood Finance Automation Application Customizing SAP
  • Redwood Finance Automation Application Customizing Base
  • Redwood Finance Automation Application Customizing Mail HTML Styles

Action Rules

  • Action Rules
  • Action rules Syntax
  • Files via Output Selection in Action Rules
  • Base Rules
  • SAP Rules
  • ABAP Rules
  • Transaction Rules

Replacements

  • Replacements
  • Base Replacements
  • Generic SAP Replacements
  • FPA Specific Replacements
  • FCc Specific Replacements
  • SAP FCc Replacements

RedwoodExpressionLanguage

  • REL Expressions
  • Base REL Functions
  • SAP Contraint REL Functions
  • SAP REL Functions
  • SAP ALM REL Functions
  • SAP FCc REL Functions
  • SAP FPA REL Functions
  • Reconciliation REL Functions
  • SAP REL functions, Miscellaneous

Default Roles

  • Built-in Roles

Appendix: Reference

  • SAP Add-Ons Contents
  • Chain Definition Templates
  • Process Definition Templates
← Action rules SyntaxBase Rules →

finance-related topic Files via Output Selection in Action Rules

General description of how to access files. This is valid for all action rules.

Current process

Several parameters allow to pass files, as input or output. Particularly the case of addressing files retrieved from SAP spool is a typical case, which is described in the section for Rule input below.

The general syntax of file addressing (usually Source files) from the current process as follows:

  1. OS file name of the server, for example /home/redwood/dest/report1.xls.
  2. Document in Redwood Finance Automation, for example doc:/FCA.FCA/report.csv.
  3. Using JobFile:<jobfile Uniqueid>.
  4. Using <Step_name>, Job <x>:<jobfile_name>.
    1. Example Step 1, job 1:stdout.log.
  5. Using job <jobid>:<jobfile_name>.
  6. * to select all files of the current process.
  7. ** to select all files of the current process and its children.
  8. Files which fit to mask (using * or ?), for example *out.log or stdout?.log.
  9. File name.
  10. Parameter, the value of which contains references like above.

Mail Attachments

For mail attachments, a more advanced syntax is available.

Syntax

<name>=<relative_job>:<file_spec>
  • <name> - the name of the file in the email attachment, for example err_log.txt:.
    • inline_ - prefix to use for files to be embedded in emails, for example inline_stderr.log=Step 1, Job 1:stderr.log, you then specify ${inline_stderr.log}` in the email source where you want the file contents to be inserted, see Inline Attachments.
    • @{name} - used when multiple files can match the expression, will be evaluated to the short name of the output.
    • @{index} - used when multiple files can match the expression, a simple counter that gets incremented.
  • <relative_job> - reference to the process that produced the output:.
    • parent - the parent of current process; note that in chain calls, the parent is usually a step and steps have no output.
    • <step_name>, Job <job_order> - a relative process in the chain.
    • Job <job_id> - process with the id job_id; for example Job 12345.
  • <file_spec> - the file reference <name>|?type.
    • <name> - matches a name, * and ? wildcards can be used. A <file_spec> of * matches all files. ** cannot be used, here.
    • ?type - will attach all files matching the type:.
    • log - log files contain the output of standard error, for example Job 6:?type=log.
    • output - output files contain the output of standard out, for example Job 6:?type=output.

You can also extract part of the file using ?search; see Using the Mail Process Definition Type for more information.

Example

<html>
<head/>
<body>
<h1>Report Generated</h1>
<br />
<p>The following is the log of the report generation:</p>
<p>${inline_Sap_Log}</p>
</body>
</html>
[Attachments]
SAP_Log.log=Step 1, job 1:joblog.log
inline_Sap_Log.log=job 12345:joblog.log
report.csv=

Relative Process

There is also an extension that allows the relative selection of output outside of the context of a process. The criteria is then executed from the relative process as a starting point.

To select output in a different process:

[<Criteria>;][{<Rel process>;<Criteria>[;<Criteria>]}]

To select output file names from the parameter content of a relative process:

Step 2, Job 3;{Step 1, job 1:stdout.log}

financeTopic

← Action rules SyntaxBase Rules →
  • Current process
  • Mail Attachments
  • Syntax
  • Example
  • Relative Process
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |