Hi Team,

One of our customer reported that the ‘Cancellation’ is not working when we used Partner’s domain users instead of the designated clients’ domain users in client’s environment for testing. The delegated user (user with partner domain) cannot send email in workflow and this causes the Workflow to be stuck in Processing.

For an example, where a user with Partner’s domain rejects a document in client’s test environment, the status in Purchase document remains ‘Pending for Approval’, despite the approval entries being updated as rejected. Sending notifications is not functioning due to discrepancy in domain address and those notifications are not moved to ‘Sent Notification’ which indicates Job Queue is not running. So that, BC process in updating Purchase Order status is not happening and remains ‘Pending for Approval’.

Based on these findings, it is learnt that testing an approval scenario in the client’s BC using Partner’s logins is not a valid approach. To test an issue, either all relevant scenarios to be replicated to Partner’s environment for testing purpose or we need to get help from client’s users to follow the testing scenarios.

We will be much appreciate if we can have a solution/feature help partners to test approval flows in client’s test environment in upcoming versions.