I’m currently working on an alpha assignment related to building a New Business Policy Underwriting System.
So far, I understand that we need to:
Create pages for Underwriters and Reviewers to view application and policy details.
Allow them to approve or reject applications.
If the Underwriter approves, only then the Reviewer should receive the task to take further action.
I also understand how to configure “My Tasks” and “Group Tasks” to show individual and group assignments.
However, I’m getting confused with Point 4, 5, and 6 of the assignment:
Point 4: Create Complex Data Model
Point 5: Create Relevant Pages for Underwriting
Point 6: Create Relevant Pages for Reviewer
I want to make sure I complete this part correctly. If anyone can explain these points in simple terms or share an example, I would really appreciate it.
Thanks for the response @Aswin . I’ve already added the comment option for the Reviewer.
But I’m still confused about what exactly needs to be done in Step 4, 5, and 6, especially compared to what I’ve already completed. Here’s where I’m stuck:
Point 4 – Create Complex Data Model
What exactly does “complex data model” mean in this context?
Does it just mean adding more relevant fields to my Policy or Application data models based on business understanding?
How can I define one-to-one and one-to-many relationships in Alpha?
Point 5 – Underwriter Pages
I understand that Underwriters can edit application details and make decisions.
But what does “Eligibility Check” mean practically? What should be included on that page?
What kind of validations or logic should I add to the decision screen?
Also, does “data pre-population” mean auto-filling fields from case data, and allowing the Underwriter to edit them?
Point 6 – Reviewer Pages
I have added the comments section, but I’m not sure what else is expected.
Should all fields be read-only for the Reviewer?
How do I structure the approval decision page to close the process correctly?
In the alpha assignment they are not mentioning about you need to do this or you need to do this validation like REEL assignment. It depends on your imagination and logic. So you can design the workflow and eligibility check on your own. And for the underwriter page i kept everything as read only and add 2 fields for adding the comment and insurance amount then 2 buttons for approval and decline and in the reviewer section same as this
and about you point 4 i dont have that much idea about that because im still in training. @Sam@Simphiwe will guide you about that
Regarding the Alpha Masterclass assignment, you have the flexibility to define certain elements as you see fit, as long as you meet the specified requirements.
Point 4 – Create Complex Data Model
On Alpha you have data model where you can define your case object that you wil working with through out the application(Model)
Yes you can on what is provided.
Click Model to find out more about Alpha data model
Point 5 – Underwriter Pages
I understand that Underwriters can edit application details and make decisions.
This means integrating REELS to your Alpha applications and checking eligibility
For a case to go to an Underwriter and a Reviewer it because it failed the criteria to generate a policy automatically so it creates a human task for an Underwriter if an underwriter approved it goes to Reviewer then a policy will be generated if approved by all these users. You can approve or reject based on your criteria for these users.
Yes, according to the masterclass guide an underwriter should be able to edit.
Point 6 – Reviewer Pages
Comment is for giving rejection reason if a case is rejected
No, according to the masterclass guide it wasn’t specified that a reviewer should be able to edit(Build pages enabling Reviewers to analyze application summaries and make decisions.).
Point 4 – Create Complex Data Model