How-to

Workflow patching

After you confirm activation, Alloy Navigator performs workflow patching.

Workflow patching is a one-time operation that updates workflow configuration to support consistent use of Currency Code across forms, actions, and financial processes.

IMPORTANT: Workflow patching may take some time to complete. During the operation, the application displays progress information to indicate that activation is still in progress.

What workflow patching changes

Patch area What changes

Object forms

Currency Code is added to full forms for key monetary objects such as Purchase Orders, Assets, Vendors, Consumables, Contracts, and Service Catalog Items.

Create actions

Currency Code is added to object creation action forms for those classes and prefilled with %[SYS Default Currency Code]%.

Step actions

If an action form contains a physical monetary field, Currency Code is added before that monetary field.

Quick Steps

Standard Quick Step actions that use virtual monetary fields are updated so Currency Code is passed through virtual field, parameter, and update logic.

Purchase Orders

Vendor selection is filtered by the current Currency Code, so a Vendor can be selected for a PO only when it uses the same currency code.

When manual workflow changes may be needed

Manual workflow changes are usually not required for standard configurations. Alloy Navigator applies the required workflow patching during Multicurrency activation.

Manual changes may be needed only when your environment has customizations that fall outside the standard workflow patching scope. Examples include:

  • Custom monetary UDFs used on forms, actions, calculations, or updates.

  • Virtual monetary fields that are later written into physical monetary fields.

  • Customized Quick Steps that create or update monetary values, Purchase Order items, invoices, vendor products, or service catalog pricing.

  • Modified purchasing workflows with custom lookup filters, validation rules, dependencies, or vendor/product selection logic.

  • Custom forms or layouts where Currency Code must appear in a specific location or support a specific process.

  • External integrations that create or update monetary objects through the API and need to pass or read Currency Code explicitly.

  • Reports, notifications, templates, or email messages that display monetary values and need to show Currency Code next to the amount.

This is especially relevant for templates and notifications because monetary field placeholders resolve to numeric values only. If the currency must be shown in text, add a separate Currency Code placeholder.