2543684 - MDF Workflows: Initiator of an MDF Workflow will receive a "Declined" e-mail notification when an in-flight change is made

When the Approver of an MDF Workflow updates a Workflow "in-flight", the Initiator will receive a "Declined" e-mail notification and the change is directly saved to the Database.

• Employee Central 2.0 - MDF features
• Metadata Framework

1. Create a new Position and set a value in a field (the value in the field must be used in the Business Rule which is defined to initiate a Workflow)
2. Workflow is triggered and approver can receive pending approve email
3. One of the approvers, makes in-flight changes via Update
4. The position is approved and is visible in the system
5. The original Initiator has receive the "Declined" email notification and on the workflow page, it states that the approver declined workflow.

This is caused by a combination of the workflow configuration and the business rule to trigger the workflow.

The workflow for this approver step will have "Edit with Route Change" in the Edit Transcation section.

When an approver who have "Edit with Route Change" on their approver step makes a change to the workflow, this will end the current workflow and try to trigger a new workflow based on the changes.

• If the changes do not meet the criteria of the rule, then no new workflow is triggered and the changes will be approved and visible in the system. The decline email will still be sent for the original workflow.
• If the changes do meet the criteria of the rule, then the new workflow will be triggered and follow the defined the workflow approval steps. The decline email will still be sent for the original workflow.

You have two options here:

• Change the workflow Edit Transaction to "Edit without Route Change":
  This means that is the workflow is edited by the approver, the workflow will continue on as normal.
• Leave the workflow Edit Transaction as "Edit with Route Change":
  Here the behaviour will stay as defined above.
  If you see that no new workflow is ever triggered and would like one to be raised, you can include a "Catch-all" else condition in your workflow rule.
  Add a "Catch-all" condition to the Workflow rule to ensure that a Workflow is still re-triggered in this scenario: 
      1. Navigate to Admin Center > Configure Object Definitions
      2. Search the object in question
      3. Identify the rule used to trigger workflows
      4. Add an "ELSE" condition to the Business Rule that triggers the Workflow for the MDF object, and define as:
         EXAMPLE:     THEN Set wfConfig to be equal to XYZ (XYZ meaning the Workflow object)

 2607123 - Workflow Rejected After Update from initiator

XAF-18019, MDF, metadata framework, mdf position management, time off, employee central, declined, email, initiator, update, rejected, sent back, send back, sentback, sendback , KBA , LOD-SF-MDF , Metadata Framework , LOD-SF-EC , Employee Central , LOD-SF-EC-POS , Position Management , LOD-SF-EC-MDF , MDF & EC2MDF Migration , Problem