Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Company Workflow #1266

Closed
solverat opened this issue Feb 7, 2020 · 3 comments · Fixed by #1284
Closed

Company Workflow #1266

solverat opened this issue Feb 7, 2020 · 3 comments · Fixed by #1284
Assignees
Milestone

Comments

@solverat
Copy link
Contributor

solverat commented Feb 7, 2020

Q A
Bug report? no
Feature request? yes
BC Break report? no
RFC? no

Definition

  • 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
@albertmueller
Copy link
Contributor

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

@solverat
Copy link
Contributor Author

solverat commented Feb 14, 2020

Backend

image

image

image

image

image

@solverat
Copy link
Contributor Author

Frontend

image

If user has access type own & company, he's able to switch address affiliation.

@dpfaffenbauer dpfaffenbauer linked a pull request Feb 14, 2020 that will close this issue
@dpfaffenbauer dpfaffenbauer added this to the 2.2.0 milestone Feb 14, 2020
@dpfaffenbauer dpfaffenbauer reopened this Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants