Workflow considerations for currency fields
You can use currency fields in active link, filter, and escalation actions. Currency fields behave like other fields in workflow actions, with these exceptions:
- The Change Field active link action cannot access the currency code menu attached to the field.
- The Set Fields and Push Fields actions allow only the overall value of the field to be set. You can use the overall value or any portion of the value (such as the date) as a data source.
- The first functional currency entered is the currency that is used in workflow and searches.
Currency fields have four functions: CURRCONVERT, CURRSETDATE, CURRSETTYPE, and CURRSETVALUE. For more information, see Specifying arguments that use a comma as a decimal separator.
Because the currency field is a complex type, it has special rules for conversion to and from other data types.
Conversion from currency
|Target data type||Data conversion rule|
|Character or Diary||The decimal value, with the currency code to the right.|
|Decimal, Real, or Integer||The decimal value only, dropping the fraction as necessary.|
|Date/Time, Date, or Time||The decimal value converts to a long date value.|
|Selection||The decimal value converts to an integer value.|
Conversion to currency
|Source data type||Data conversion rule|
|Character or Diary||
Parses the string to get a number and symbol. If the currency code is valid, the following rules are applied:
|Decimal, Real, or Integer||Converts the numeric value to Decimal, and then appends the primary allowable currency code.|
|Date/Time, Date, or Time||Converts the numeric value of the time stamp to Decimal, and then appends the primary allowable currency code.|
|Selection||Converts the numeric value to Decimal, and then appends the primary allowable currency code.|