Known Issues and their Solutions in Salesforce B2B Cloud

Problem with Flow Debugging

Debugging with the flow typically requires impersonating a buyer Run flow as another user. However, the custom payment component installed as a part of this installation will be run as the user that is debugging, and not the buyer. This typically causes some malfunctioning behavior like missing billing addresses.

There are a few workarounds.

1. Don't debug and instead run as the buyer within the store relying on errors sent to the email specified in Process Automation Settings to find problems.
2. If you know the buyer's account you can make a change in B2BPaymentController.cls. Directions are specified near the top of getPaymentInfo().
3. You can also make a change in the getUserAccountInfo() method in B2BUtils.cls. Here you would put the ID of the user instead of the call to UserInfo.getUserId();. This was not documented within the class as the effects would be farther reaching than in B2BPaymentController.cls.