You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to assign customers to a company object
There should be no BC break and also no change in the current workflow but should allow us to decide which workflow we want to use
Company Object
Introduce new object company
Fields: name
Customer Object
Add optional 1-to-1 relation field for company
Addresses
Address assignment: By default, every address object gets assigned to a customer object. This is standard by now and should stay that way except if a customer is bounded to company: There should be a configuration event for that:
User can choose addresses from company
User can/cannot add new addresses to himself or to company
Registration
Guest Registration: Same as now. New customer object with isGuest flag Default Registration: Same as now. New customer object with given data. But: there should be a possibility to hook into this process: If a user needs to set a company name, I may want to create a company object and append the user to it by automatization.
Cart
After a user has been logged in, we're able to detect a company by hasCompanyRelation(). By default, this should be enough.
Checkout
Addresses: See Address section. Which address should be shown? Make it configurable:
Addresses from company
Addresses from customer
Addresses from company and customer
Backend
Add new configuration panel customer
Add new sub configuration Customer to New Company
Create companyobject by adding a name (check for duplicates)
Move customer as child object to new company
Allow choosing between keep addresses to customer or move addresses to company
Fire Event to allow projects to do some more data assignment
Add new sub configuration Customer to Existing Company
Choose customer and company
Move customer as child object to new company
Allow choosing between keep addresses to customer or move addresses to company
Fire Event to allow projects to do some more data assignment
Show Company field in Order Overview if available
Migration
Create new company object
The text was updated successfully, but these errors were encountered:
great idea, already had two use cases especially when you have to connect SAP via API etc.
would still recommend to add a VAT number field in the register process, with a already exist validation.
nice to have: special rules, condition based on company for custom prices, shipping and payment
Definition
Company Object
company
name
Customer Object
1-to-1 relation
field forcompany
Addresses
Address assignment: By default, every address object gets assigned to a customer object. This is standard by now and should stay that way except if a customer is bounded to company: There should be a configuration event for that:
Registration
Guest Registration: Same as now. New customer object with
isGuest
flagDefault Registration: Same as now. New customer object with given data. But: there should be a possibility to hook into this process: If a user needs to set a company name, I may want to create a company object and append the user to it by automatization.
Cart
After a user has been logged in, we're able to detect a company by
hasCompanyRelation()
. By default, this should be enough.Checkout
Addresses: See
Address
section. Which address should be shown? Make it configurable:Backend
customer
Customer to New Company
company
object by adding a name (check for duplicates)customer
as child object to newcompany
keep addresses to customer
ormove addresses to company
Customer to Existing Company
customer
as child object to newcompany
keep addresses to customer
ormove addresses to company
Migration
company
objectThe text was updated successfully, but these errors were encountered: