Affects Version/s: None
Fix Version/s: None
Component/s: User Management > Business Accounts
Sprint:U&SM| S04 Sprint 6|1.5-1.26
Four options to consider:
- Full Migration of Backend, Create New Countries UI
- Full Migration of Backend, Reuse Commerce Countries UI
- Bridge Migration of Backend, Create New Countries UI
- Bridge Migration of Backend, Reuse Commerce Countries UI
The options that seem to make most sense for the sake of time are options 2 or 4. Option 4 would likely be the cheapest, but Option 2 might not be much more expensive since only a few callers are calling CommerceCountry or CommerceRegion services.
Decided to go with option #2: "Full Migration of Backend, Reuse Commerce Countries UI".
There are not many usages of CommerceCountry and CommerceRegion in Commerce's code base, thus it's not much more expensive to do a full migration compared to the bridge migration.
In terms of the UI, the Commerce Countries management interface is sufficient for Commerce's use case. Creating a portal-wide management interface doesn't provide much value at this point, though it's a nice to have for the future.