Making Commerce, Webform & Group play nicely together - DrupalCamp Bristol 2017
0 likes337 views
The document discusses how an insurance company case study combined Webform, Drupal Commerce, and Group modules. It describes how Webform was used to build a quote builder, Commerce to select and purchase insurance products, and Group to implement tiered access levels for dealer head offices, branches, and staff. The case study created different user types and needs, content types, and product displays to allow users to get quotes, buy policies, manage claims, and see reports according to their access levels.
Making Commerce, Webform & Group play nicely together - DrupalCamp Bristol 2017
- 1. @ChandeepKhosa #DCBristol17 Insurance company case study: Making Commerce, Webform & Group play nicely together @ChandeepKhosa
- 2. @ChandeepKhosa #DCBristol17 Who am I? Freelance / Contract Drupal Developer Drupal 8 core contributor (front end & usability) Organiser of Drupal West London user group Involved in training & mentoring Drupal developers Drupal meetup & camp addict
- 3. @ChandeepKhosa #DCBristol17 Who am I? Im self-taught since playing with Drupal in 2008, procrastinating when I should have been working on my 鍖nal year university project :) Ive been addicted ever since and love it! Worked as a contractor for The Health Foundation, Toyota, Oxford University, Team GB, Christian Aid, Tate Art Gallery, Agile Collective, Five Mile, Microserve & NDP.
- 4. @ChandeepKhosa #DCBristol17 Ill be covering Project background Site architecture Webform - Quote builder Commerce - Architecture & selecting relevant products Group - Tiered access levels
- 5. @ChandeepKhosa #DCBristol17 Project background Build a web application that handles quotes, policies & claims. Allows users to buy policies, cancel them, make claims on them. Display reports.
- 7. @ChandeepKhosa #DCBristol17 User types Consumer Dealer Staff Branch Head Of鍖ce Client admin
- 8. @ChandeepKhosa #DCBristol17 User needs Find out information before deciding to buy Get a quote Buy a policy Manage their policy Make & track claims
- 9. @ChandeepKhosa #DCBristol17 Site architecture Content types : Policy, Claim Webform : Request a Quote Commerce products
- 10. @ChandeepKhosa #DCBristol17 Get A Quote
- 11. @ChandeepKhosa #DCBristol17 Webform Learnings Use Webform 4.x instead of 3.x if you need to be able to insert tokens. Switching can may break your custom modules. e.g.) User 鍖elds such as name & address Webform Wrappers module allows you to add classes e.g.) Row & Col-Md-4
- 12. @ChandeepKhosa #DCBristol17 Webform 鍖elds & tokens
- 14. @ChandeepKhosa #DCBristol17 Drupal Commerce Product displays Product Dealer Product with Model Number Accidental Damage
- 19. @ChandeepKhosa #DCBristol17 Find relevant products
- 20. @ChandeepKhosa #DCBristol17 Find relevant products
- 21. @ChandeepKhosa #DCBristol17 Quote form : step 2
- 25. @ChandeepKhosa #DCBristol17 Dealer groups Head Of鍖ce : Can create branch groups & admin users. Can see all policies & claims. Branch : Can create staff users. Can see policies & claims restricted to their branch. Staff : Cant create groups or users. Can see policies & claims created by other colleagues.
- 28. @ChandeepKhosa #DCBristol17 Dealer Head Of鍖ce : permissions
- 29. @ChandeepKhosa #DCBristol17 Dealer Head Of鍖ce group as User 1
- 30. @ChandeepKhosa #DCBristol17 View members as User 1
- 33. @ChandeepKhosa #DCBristol17 Making content belong to a group
- 34. @ChandeepKhosa #DCBristol17 Dealer HO viewing a report
- 36. @ChandeepKhosa #DCBristol17 Summary All these modules are awesome, but when used together correctly they can build a powerful business critical application. Email me at hello@chandeepkhosa.com Please leave feedback at https://joind.in/ talk/88d9a