|
8.10.1 System modification
To satisfy two of the requirements identified in 4.2, Requirements, we have to make a small modification to one of the system files.
| Users registered in a parent buyer organization can shop in both B2B direct stores.
|
|
| Users registered in a child buyer organization can shop in only one B2B direct store.
|
We encountered a problem when attempting to implement a solution that matched the requirements listed above. Each time a user is given the role of Registered Customer to a parent seller organization, they automatically have the same role for the child seller organizations. We got around this problem by creating a separate child buyer organization, All Stores. Our current organization structure offers three possible scenarios when registering buyers:
| 1.
| Buyer A accesses the SWG store and registers, entering her Buyer Organization as SWG/IBM. She is given the role of Registered Customer in the IBM Seller OrganizationSWG and is granted access only to the SWG store.
|
| 2.
| Buyer B accesses the IGS store and registers, entering his Buyer Organization as IGS/IBM. He given the role of Registered Customer in the IBM Seller OrganizationIGS and is granted access only to the IGS store.
|
| 3.
| Buyer C accesses either the SWG store or the IGS store and registers with a Buyer Organization of All Stores/IBM. She is given the role of Registered Customer in the IBM Seller Organization and access to both stores.
|
Enabling the third scenario requires modifying the file called MemberRegistrationAttributes.xml.
|
