Configuring Payables Workflow Notifications

You can configure Payables workflow notifications for both email and in-app to meet your business needs and requirements. For example, approvers for Payables invoice approval receive a standardized workflow notification when the invoice requires their approval.

This standardized workflow notification has a list of attributes shown in a specific format. However, you have your own requirements regarding what information is in the approval workflow notifications and in the format you want displayed. The ability to configure Payables workflow notifications to meet your specific business needs and requirements is now available. The capability to configure the notifications supports changing the format, content, and display of the notifications. In the invoice workflow approval notification, you have the ability to add other invoice-related attributes that you want to display in those workflow notifications.

Payables Workflow Notifications

This table shows a list of the current Payables workflow notifications.

Notification Name

Workflow Task Name

Description

Invoice Approval

FinApInvoiceApproval

Workflow notifications sent for approving invoices.

Hold Resolution

FinApHoldApproval

Workflow notifications sent for resolving invoices on hold.

Payment Approval

PaymentApproval

Workflow notifications sent for payment approval of invoices.

Invoice Account Coding

FinApInvoiceAccountCoding

Workflow notifications sent for account coding of invoices.

Note: For the Invoice Approval and Invoice Account Coding in-app notifications, use the Edit Distributions option in the Actions menu to edit the distributions.

Oracle Analytics Publisher

Use Oracle Analytics Publisher for configuring the Payables workflow notifications.

  • Mobile devices can use optimized notifications that are ready to use as delivered.

  • The notifications generated based on Analytics Publisher templates are ready to use as delivered. You can easily configure the templates to meet your business requirements. If required, you can change the delivered template layouts and content, to add images, change colors and styling, add or remove attributes or modify text.

  • Any change made to the BIP template impacts both the email and the in-app notifications.

    Predefined BIP reports generate workflow notifications pulling content from the standard data models. The report layouts use common table and paragraph styling. In addition, reusable notification components use a common sub template. These include a custom logo in the notification header, action buttons, and task history.

    Note: The history component is currently not based on a BIP data model. You can't modify it.
    Note: Both email and in-app notifications use the same template. Any change made to the BIP template for email has an impact on the in-app notification as well.

Best Practices

Follow these best practices:

  • Never edit delivered notifications.

  • Use the Customize feature for reports and subtemplates.

  • Copy the data models, paste into the Custom folder, and edit the copies.

  • Don't rename the standard BI components, the reports, or sub templates. Preview your changes before publishing. In case of errors, revert the changes.

  • Don't modify any links in the subtemplate file. Before saving a local copy, disable the Update links on the save option in Microsoft Word.