You can use OGNL expressions to determine input parameters dynamically when a workflow runs. The Orchestrator OGNL parser uses certain keywords during OGNL processing that you cannot use in workflow attribute or parameter names.

Using a reserved OGNL keyword as a prefix to an attribute name does not break OGNL processing. For example, you can name a parameter trueParameter. Reserved keywords are not case-sensitive.

You cannot use the following keywords in workflow attribute and parameter names.

Table 1. Forbidden Keywords in Attribute and Parameter Names
Forbidden Keyword Forbidden Keyword Forbidden Keyword
  • abstract
  • back_char_esc
  • back_char_literal
  • boolean
  • byte
  • char
  • char_literal
  • class
  • _classResolver
  • const
  • context
  • debugger
  • dec_digits
  • dec_flt
  • default
  • delete
  • digit
  • double
  • dynamic_subscript
  • enum
  • eof
  • esc
  • exponent
  • export
  • extends
  • false
  • final
  • flt_literal
  • flt_suff
  • ident
  • implements
  • import
  • in
  • int
  • int_literal
  • interface
  • _keepLastEvaluation
  • _lastEvaluation
  • letter
  • long
  • _memberAccess
  • native
  • package
  • private
  • public
  • root
  • short
  • static
  • string_esc
  • string_literal
  • synchronized
  • this
  • _traceEvaluations
  • true
  • _typeConverter
  • volatil
  • with
  • WithinBackCharLiteral
  • WithinCharLiteral
  • WithinStringLiteral