ColoredCow / civicrm

Other
1 stars 0 forks source link

Prototype: Registration Workflow #13

Open deep4k-tripathi opened 3 weeks ago

deep4k-tripathi commented 3 weeks ago

Functional Requirements for the Registration workflow

In this issue, we are tracking all the requirements to execute the prototype for the registration workflow within the CRM. The prototype will include the registration workflow for both individual and institutional stakeholders.

Registration - Individuals

The registration process is essential for entering contact information into the contact database. This helps us gather information about the stakeholders who are linked to Goonj and details about their engagement.

User Journey for Individual Registration The individual registration process allows stakeholders to connect with Goonj through various entry points:

  1. Stakeholders can register through a link on the Goonj website, via a WhatsApp share/chat bot, using a QR code during event registration, at drop-off centers, collection camps, or during events. Additionally, a Goonj team member can manually register the stakeholder.
  2. When initiating the registration process, the system will verify if the user is a first-time registrant or if they are already registered. This is determined based on configurable key parameters such as mobile number or email.
  3. The registration form will capture and store the origin of the registration (e.g., specific QR code or link) to understand how the user landed on the registration page.
  4. The form will feature multiple configurable sections, including a basic registration section and a detailed information section. The sections displayed to the user will vary based on the origin of the registration.
  5. The basic form will collect essential information such as name, contact information, city, and state.
  6. If a detailed form is required (e.g., for volunteers or when filled out by a Goonj team member), additional fields will be displayed, including age group, gender, address, status, and tags. These fields will also be configurable.
  7. Upon submission, automatic acknowledgment emails or messages will be sent to the user and optionally to team members. The content of these emails/messages will depend on the user's selections and will be based on predefined templates.
  8. Help texts will be provided in the forms to assist users in completing the registration.
  9. Once the form is filled and submitted, an entry will be made for the registered individual in the contact database

Workflow Diagram: image


Registration - Institutions

In this context, institutions can include educational institutions, corporates, FMCG companies, bulk manufacturers, dry cleaners, youth groups, associations, philanthropic foundations, hotels, housing societies, and clubs (e.g., Rotaries). The registration process for institutions is designed to cater to groups rather than individuals.

User Journey for Institutional Registration The institution registration process facilitates the connection of groups with Goonj through various methods:

  1. Institutions can register directly using QR codes or links, or a Goonj employee can manually register the institution.
  2. The institution registration form will have configurable sections.
  3. The form will collect comprehensive information including the type of institution, institution details (name, branch, department hierarchy if applicable), address, and contact information. The contact information will be linked in a one-to-many relationship, capturing details such as name, profile (e.g., CSR Head, Teacher, PTA Secretary based on the institution type), status (active/inactive), and contact details. Individuals associated with the institution will automatically be registered as individuals if they are not already in the database.
  4. Additional information collected will include the size of the institution, the Goonj team member attached (with a history of changes if applicable), and the initiation source (Goonj or the institution).
  5. Upon form submission, an entry will be made for the registered institution in the contact database.
  6. The system will maintain a history of the contact information associated with the institution, ensuring that the point of contact is part of the individual registration as well.
  7. A field will indicate whether the institution is onboarded. If the registration is created by a Goonj member and the onboarded field is not selected, the status will be “Initial.” If the onboarded field is selected, the status will be “Onboarded.” If the registration is done directly by the institution, the status will be “Initial.”
  8. Checkboxes will be available for the team to confirm whether the institution has political or religious affiliations. Team members will update the status field to “Onboarded” or “Blocked” after due diligence, including reasons for a “Blocked” status.
  9. If the status is set to “Onboarded,” a registration confirmation email will be sent to both the associated Goonj member and the institution. If not, the email will be sent only to the Goonj team member.

Workflow Diagram: image

deepankar-sajwan commented 2 weeks ago

Test case scenarios for individual user registration in desktop and mobile view

deepankar-sajwan commented 2 weeks ago

Test case scenarios for institutional registration in desktop and mobile view

Verify below cases after form submission

deepankar-sajwan commented 1 week ago

Scenarios related to user access based on the user role are listed below