Comprehensive Hands-On Training Evaluation Assignment: Alpha Platform
Objective: Assess your ability to apply the Alpha Platform’s capabilities by designing and implementing a complete case management solution, ensuring key functionalities and minimum operational standards are met.
Assignment Overview
You are tasked with creating a “New Business Policy Underwriting System” using the Alpha Platform. This system should include end-to-end workflow implementation, data modeling, user interface design, task management for Underwriter and Reviewer roles, and automated email notifications based on decision outcomes.
To help you get started, we have provided a pre-configured Case Type and an initial case instance. You can use this as a foundation for your project.
Getting Started with the Provided Case Type
Pre-Configured Case Type: alpha_training
We have set up a Case Type named alpha_training with an initial case instance containing sample data. You can create a new case instance using the following curl command:
curl --location 'https://sandbox.neutrinos-apps.com/caseservice/case/instance/create' \
--header 'accept: application/json' \
--header 'Authorization: Bearer YOUR_BEARER_TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
"caseType": "alpha_training",
"caseData": {
"firstName": "gowtham",
"lastName": "balram",
"email": "customer@example.com",
"policyDetails": {
"inception_date": "01-12-2024"
},
"features": [
{
"text": "Basic Life Insurance",
"included": true
},
{
"text": "TeleMedicine",
"included": true
},
{
"text": "Digital Budgeting App",
"included": true
},
{
"text": "Short Term Disability Cover",
"included": true
},
{
"text": "Extended Life Cover",
"included": true
},
{
"text": "Priority Support",
"included": true
}
],
"address": "HSR Layout",
"dob": "12-08-1990",
"age": "34",
"coverage_term": "1 Year",
"beneficiary": "neelapareddy"
},
"wfData": {
"stp_rules_request": {
"version": "YOUR_REELS_WORKFLOW_VERSION",
"inputObj": {
"YOUR_REELS_WORKFLOW_PAYLOAD"
},
"subFlowIDs": [],
"workflowId": "YOUR_REELS_WORKFLOW_ID"
}
}
}'
Note:
- Replace
YOUR_BEARER_TOKENwith your actual authorization token. - Ensure the customer’s email (
"email": "customer@example.com") is included incaseDataas it will be used for sending notifications. - By default these variables are required for caseData:
firstName, lastName, email, policyDetails.inception_date, address, dob, age, coverage_term, benefiary. - wfData should have
stp_rules_request.version, stp_rules_request.inputObj.input, stp_rules_request.workflowId
How to Use This Starting Point:
- Understand the Data Structure: Review the provided
caseDataandwfDatato understand the initial data fields and workflow triggers. - Extend and Customize: Use this initial case as a foundation to build your data models, workflows, and UI components.
- Integrate with Your Project: Incorporate this Case Type into your Alpha Project, aligning it with your designed workflows and data models.
Getting Started with the Provided BPM Project
Make sure to import that attached Business Process zip file while configuring Process in Workflow Studio. Download the following file and rename the extension to .zip from .txt or remove the extension to upload the project to Workflow Studio.
alpha_training_nb_underwriting.zip (217.6 KB)
Assignment Tasks, Expected Outcomes, and Scoring Criteria
1. Plan Project Scope and Business Requirements (10%)
- Task: Document the project scope for the “New Business Policy Underwriting System” and outline business requirements for both Underwriter and Reviewer roles.
- Expected Outcomes:
- Clear and detailed scope definition for the underwriting process.
- Identification of key functionalities and responsibilities for Underwriters and Reviewers.
- Comprehensive list of required data points, tasks, and workflows.
- Inclusion of decision variables for human tasks:
underwriting_approved(Boolean) for the Underwriter’s decision.approval_approved(Boolean) for the Reviewer’s decision.
- Plan for email notifications upon rejection at either human task.
- Scoring Criteria:
- 10%: Comprehensive scope and requirements document addressing all aspects for both roles, including decision variables and email notification requirements.
- 5%: Partial details with missing elements for one role or insufficient depth.
- 0%: Insufficient planning, unclear scope, or missing key requirements.
2. Design Pages and Data Models for Users (15%)
- Task: Break down the pages and data models required for Underwriters and Reviewers, aligning them with their respective tasks.
- Expected Outcomes:
- Clear list of required pages (e.g., Application Details, Policy Review, Decision Page).
- Defined data models with fields such as
CustomerInfo,PolicyDetails,NomineeInfo,DecisionStatus, and inclusion ofunderwriting_approvedandapproval_approved. - Alignment of pages and models with user tasks and data needs.
- Scoring Criteria:
- 15%: Well-structured list of pages and models fully meeting user needs and incorporating required variables.
- 10%: Basic list missing minor elements or lacking alignment with tasks.
- 0%: Incomplete or irrelevant breakdown of pages and models.
3. Configure “My Tasks” and “Group Tasks” (15%)
- Task: Set up visible and searchable task lists for individual users (“My Tasks”) and user groups (“Group Tasks”).
- Expected Outcomes:
- Configured “My Tasks” showing individual assignments accurately.
- Configured “Group Tasks” showing shared assignments with effective search and filter options.
- Tasks are correctly visible to appropriate users and groups.
- At the bare minimum, add columns that helps users to identify cases i.e., Name, DOB, Email ID etc.,
- Scoring Criteria:
- 15%: Fully functional task lists with advanced filters and search capabilities.
- 10%: Basic task lists with limited search/filter features or minor visibility issues.
- 0%: Task lists not configured or not functioning.
4. Create Complex Data Model (15%)
- Task: Develop a comprehensive data model supporting “New Business Policy Underwriting,” including all required keys and relationships.
- Expected Outcomes:
- Data entities like
Customer,Policy,Nominee, andClaimHistorymodeled with correct fields.Correct implementation of one-to-one and one-to-many relationships. - Inclusion of data validation rules and data types.
- Incorporate
wf_datavariables intocase_data, ensuring they are available for email templates.
- Data entities like
- Scoring Criteria:
- 15%: Detailed, logically structured data model with all required keys, relationships, and variables.
- 10%: Functional model with minor field or relationship gaps.
- 0%: Incomplete, incorrect, or non-functional data model.
5. Create Relevant Pages for Underwriting (10%)
- Task: Build pages enabling Underwriters to view, edit, and submit application data.
- Expected Outcomes:
- Pages like “Application Details,” “Eligibility Check,” and “Underwriting Decision” with necessary fields and validations.
- Interface to capture the Underwriter’s decision (
underwriting_approvedas Boolean). Its value can be true or false based on which the task will move to Reviewer or Close the Reviewer. - User-friendly interface with data pre-population where applicable.
- Functionality to save progress and submit tasks.
- Scoring Criteria:
- 10%: Fully functional pages tailored for Underwriter tasks, including decision capture and validations.
- 5%: Basic pages missing some fields, validations, or functionality.
- 0%: Pages not created or not functioning.
6. Create Relevant Pages for Reviewer (10%)
- Task: Build pages enabling Reviewers to analyze application summaries and make decisions.
- Expected Outcomes:
- Pages like “Policy Summary,” “Approval Decision,” and “Comments Section” with necessary data and actions.
- Interface to capture the Reviewer’s decision (
approval_approvedas Boolean). - Options to approve, reject will close the process.
- Display of all relevant data updated by Underwriter.
- Scoring Criteria:
- 10%: Fully functional pages tailored for Reviewer tasks with decision capture and decision-making capabilities.
- 5%: Basic pages missing some data, actions, or clarity.
- 0%: Pages not created or not functioning.
7. Implement Email Notifications (10%)
- Task: Configure the system to send automated email notifications to the customer’s email address provided in the case data upon rejection at either the Underwriter or Reviewer stage.
- Expected Outcomes:
- Email templates utilize
case_datato fill in the template and email key is used to send the Email to the customer. - Upon rejection (
underwriting_approvedorapproval_approvedset tofalse), an email is sent to the customer’s email address. - Emails include relevant information such as the customer’s name, policy details, and reason for rejection if available.
- Email templates utilize
- Scoring Criteria:
- 10%: Email notifications are correctly configured and sent upon rejection at either stage.
- 5%: Emails are configured but missing information or not triggered correctly.
- 0%: Email notifications not implemented or not functioning.
8. Configure Inbox Dashboard (5%)
- Task: Design an inbox dashboard showing task summaries and statuses for users.
- Expected Outcomes:
- Dashboard displaying task status, priority, due dates, and other relevant details.
- Integration with “My Tasks” and “Group Tasks” for seamless navigation.
- Visual indicators for task urgency or pending actions.
- Scoring Criteria:
- 5%: Comprehensive dashboard with clear task visualization and user-friendly interface.
- 3%: Basic dashboard with limited details or usability issues.
- 0%: No dashboard configured or not functioning.
9. Configure Enquiry Search (5%)
- Task: Set up an enquiry page for users to search and filter applications based on specific criteria.
- Expected Outcomes:
- Search functionality with filters like “Customer Name,” “Policy ID,” “Application Status,” and date ranges.
- Quick retrieval of search results with relevant data displayed.
- Ability to access application details from search results.
- Scoring Criteria:
- 5%: Fully functional enquiry search with relevant filters and smooth navigation.
- 3%: Basic search functionality with limited filters or slower performance.
- 0%: No search functionality configured.
Sanity/Minimum Requirements (Mandatory for Passing)
To ensure the basic functionality of the case management system:
1. Case Assignment to Underwriter Group (Non-STP Case)
- Requirement:
- Non-STP cases must automatically be assigned to the Underwriter Group upon creation.
- Verification Steps:
- Use the provided
curlcommand to create a case instance with data that fails STP criteria. For deriving STP or N-STP you have to create a Rëels workflow, which should returnstpandprice. - Confirmation of the case appears in the Underwriter Group’s “Group Tasks.”
- Ensure the case is searchable in the Inbox and contains all required details.
- Use the provided
- Minimum Passing Criteria:
- The case is visible and accessible to Underwriters in their task list.
2. Submission by Underwriter to Reviewer Group
- Requirement:
- Upon Underwriting task completion and submission, the case should route to the Reviewer Group.
- Underwriter’s decision (
underwriting_approved) is captured and passed along.
- Verification Steps:
- Log in as an Underwriter, open the assigned case, complete the task, capture the decision, and submit.
- Log in as a Reviewer and verify the case appears in their “Group Tasks.”
- Confirm the case data includes Underwriter updates and decision variables.
- Minimum Passing Criteria:
- The case is correctly routed to Reviewers, and the decision variable is accurately captured and accessible.
3. Reviewer Submission and Case Completion
- Requirement:
- After the Reviewer completes their task, the case status updates appropriately (e.g., Approved, Rejected).
- The reviewer’s decision (
approval_approved) is captured. - If rejected, an email is sent to the customer.
- Verification Steps:
- Log in as a Reviewer, perform the review, capture the decision, and submit.
- Verify the case reflects the updated status and is no longer in the Reviewer’s task list.
- If rejected, confirm that an email was sent to the customer’s email address.
- Minimum Passing Criteria:
- Case updates correctly with the review decision, and email notification is sent upon rejection.
4. Email Notification upon Rejection at Underwriter Stage
- Requirement:
- If the Underwriter rejects the case (
underwriting_approvedset tofalse), an email is sent to the customer.
- If the Underwriter rejects the case (
- Verification Steps:
- Log in as an Underwriter, reject the case, and submit.
- Confirm that the case does not proceed to the Reviewer stage.
- Verify that an email was sent to the customer’s email address.
- Minimum Passing Criteria:
- Email notification is sent upon rejection by Underwriter, and case workflow ends appropriately.
5. End-to-End Workflow Functionality
- Requirement:
- The entire workflow from case creation to final decision must function without errors.
- Minimum Passing Criteria:
- Smooth progression through all workflow stages with correct task assignments, data integrity, and decision variables captured.
Additional Notes
- Key Data Integrity:
- Ensure that all data entered or updated at each stage persists correctly and is accessible to subsequent users in the workflow.
- Decision variables (
underwriting_approved,approval_approved) must be accurately captured and stored incase_data.
- Visibility and Accessibility:
- Task lists (“My Tasks” and “Group Tasks”) must accurately reflect assigned tasks for Underwriters and Reviewers.
- Failure to Meet Sanity Requirements:
- Not meeting these minimum requirements results in an automatic fail, regardless of performance on other criteria.
Evaluation Guidelines
- Submission Format:
- Project Files: Exported Alpha Project files containing all configurations.
- Documentation: Brief write-up explaining your implementation approach, design choices, and any challenges faced.
- Demonstration: Screenshots or a video walkthrough showing:
- Workflow implementations.
- UI designs and data models.
- Task assignment and Inbox configurations.
- Case creation and progression through the workflow.
- Email notifications being sent upon rejection.
- Passing Criteria:
- Minimum Score: 70% overall and all sanity requirements met.
Total Possible Score: 100%
By completing this assignment, you will demonstrate both your theoretical understanding and practical skills in using the Alpha Platform to build a functional case management system that meets real-world business requirements, including automated decision-making and customer communication.
