Hi,
We need help solving a problem (not a bug in DW). We have a B2B site that uses Impersonation extensively this way:
- Impersonation mode = Replace logged in user
meaning secondary user = user that impersonates another user - User log's in
- Impersonates another user (a company/department) and places orders for them
The problem is that we implemented Saved Cards and now the customer told us, they should not be shared, meaning, they should be stored on the user that logged in initially.
Quick fix now is not to use Saved Cards, but we need to overcome this. We came up with some ideas but need guidance:
- Have secondary user ID reference on the Saved Cards table - much like orders
- We can create a new column but don't know in which event/notification to set it
- We could then exclude just the cards the user has created in Razor
- While impersonating, render the saved cards from the "secondary" user
- But technically would using a card from User A to pay an order for User B - Currently DW checks for that (as it should)
- It would also mean we'd have to change to whom a credit card is saved when creating a new one (primary or secondary)
I am leaning towards idea 1. Would that be feasible? Are there any other ideas?
We understand this is an edge case and goes beyond the planned scope of impersonation, but it's a real issue for some customers and need to find the best way to approach it in all of our projects.
Best Regards,
Nuno Aguiar