diff --git a/api-guides/expense/cost-object-workflow-integration.html b/api-guides/expense/cost-object-workflow-integration.html index 777c6c08e..0f2ce8173 100644 --- a/api-guides/expense/cost-object-workflow-integration.html +++ b/api-guides/expense/cost-object-workflow-integration.html @@ -634,14 +634,9 @@

Solution Steps for Expense

  • When the report is moving within a cost object sub-branch it will generate a single event with one step instances.
  • ESS Expense Event would include a new assignedUserId field in the Status Changed Facts Schema.
  • Portal can also optionally listen to subsequent status change events (eventType=statusChanged) to further notify users after item has entered cost object approval workflow. For example, in case an item has been recalled (A_RESU), could post an additional notification to those users.
    • +
  • Reference: See Concur Expense: Workflow – Cost Object Approval Setup Guide and Concur Request: Cost Object Approval Setup Guide for detail on cost object approval workflow steps. In the examples in Section 4 of both guides, Dave/Cindy/Finn would each receive a notification event when the Report/Request first enters cost object approval workflow.
    • - - -

    Reference: See Concur Expense: Workflow – Cost Object Approval Setup Guide and Concur Request: Cost Object Approval Setup Guide for detail on cost object approval workflow steps. -In the examples in Section 4 of both guides, Dave/Cindy/Finn would each receive a notification event when the Report/Request first enters cost object approval workflow.

    - -
    1. Portal system retrieves all delegates’ user IDs from the Identify v4 API for each approver that just received an event notification, and then portal sends a notification to each approver and delegate.