Make sure to use same branch for CM / Admin (feature/APS-1234), also please check groups and user configuration in admin using same branch. @akash.patle
share with me as well - cm, admin url and creds privately via email
@shas, On CM/Admin, I can only see the main branch. I’m not sure how to add or view other branches there, as there is only a search option available, and I don’t see the feature/APS-1234 branch listed.
The same issue exists for Group Configs and User Configs as well.
I have also shared the CM and Admin URLs, along with the credentials, with you privately via email.
Make use of branching feature from alpha to create branch from main or merge. (I have done this for now)
–
Also i have noticed the case type in your project is “training_entry_process“ not “Business_Policy_Underwriting_AP“
–
I have created case definition for this case type with pdid 26. now case instance create is working as well the case has came to group task.
–
@akash.patle , please proceed with configuring pages for your process from branch feature/APS-1234 ( Alpha Studio )
I need some guidance on the Alpha assignment.
I have created the case, but I haven’t configured the workflow data (Rules/Reels for STP & Non-STP). Do we need to create those ourselves, or are they already available in the ZIP file?
We have completed the pages, including the Approve and Decline buttons, but we’re not sure what logic or bindings should be configured for them.
As per the assignment, when the Underwriter approves, the case should move to the Reviewer, and if either role rejects, a rejection email should be sent. Could you please guide us on how to configure this workflow?
Also, we couldn’t find where the email templates are configured in Alpha Studio.
If possible, could you please take a 30-minute session to explain/explore the workflow configuration? It would really help us move forward.
Regards
Hemanth v
Hello @Hemnath ,
You can configure your workflow based on your business logic by passing the required workflow data under the wf section in the Case Creation API. The corresponding workflow should also be configured in Reels.
The final outcome of the workflow should be either STP or Non-STP. If no workflow is provided in the request, the logic will directly enter the Non-STP flow, which results in case creation in Alpha and requires manual intervention, such as reviewing and approving the case.
The review and approval logic is already implemented in your BPM flow.
I need some guidance regarding the application approval workflow and email notifications.
- For email notifications when an Underwriter/Reviewer rejects an application, do we have any internal email service available that we can use to send emails? Or do we need to integrate a third-party email provider such as SendGrid, Mailgun, etc.?
- We have two separate pages: Underwriter and Reviewer. Once a case is created and reaches the Underwriter page, if the Underwriter approves it, the case should be routed to the Reviewer page along with all the associated data. What is the recommended approach to link these pages and pass the case data between them?
- Can you also confirm whether the following workflow is correct?
Case Created → Underwriter Approved → Reviewer Approved → Claim Success
Case Created → Underwriter Rejected → Rejection Email Sent
Case Created → Underwriter Approved → Reviewer Rejected → Rejection Email Sent.
Hi @Sam need admin access to create case in alpha
for - mariselvan.g@sutherlandgloabl.com
@Mariselvan can you please try now??
I have created a popup to capture Underwriter/Reviewer comments. After the Underwriter clicks Approve, how do I route the case to the Reviewer? Should this be configured in the Triggers section, or is there another recommended approach?
Could you please guide us on the email template configuration? Is there a built-in email template feature in Alpha, or should we implement it using custom code or integrate a third-party email service?
We are also not clear about the STP/Non-STP flow. How should it be configured and integrated with the project? Is there any sample implementation, recorded session, or documentation available that explains this?
Regarding the Reels workflow, while testing/case creating I noticed that it accepts an input payload and returns an output (STP result). Should our payload follow a specific format defined by the Alpha project, or can we design our own payload structure?
If there is a standard request/response format, could you please share any documentation or sample payload?
How that will capture on BPM
Is there any documentation or example that explains how wfData should be passed during case creation and how it is used by the BPM workflow?
data model json:
{
“$schema”: “https://json-schema.org/draft/2020-12/schema”,
“title”: “Case Definition”,
“type”: “object”,
“properties”: {
“firstName”: {
“type”: “string”
},
“lastName”: {
“type”: “string”
},
“email”: {
“type”: “string”
},
“dob”: {
“type”: “string”,
“format”: “date”
},
“age”: {
“type”: “number”
},
“address”: {
“type”: “string”
},
“coverage_term”: {
“type”: “string”
},
“beneficiary”: {
“type”: “string”
},
“policyDetails”: {
“type”: “object”,
“properties”: {
“policyId”: {
“type”: “string”
},
“policyType”: {
“type”: “string”
},
“coverageAmount”: {
“type”: “number”
},
“premiumAmount”: {
“type”: “number”
},
“inception_date”: {
“type”: “string”,
“format”: “date”
},
“expiryDate”: {
“type”: “string”
}
}
},
“nomineeInfo”: {
“type”: “object”,
“properties”: {
“name”: {
“type”: “string”
},
“relationship”: {
“type”: “string”
},
“age”: {
“type”: “number”
}
}
},
“features”: {
“type”: “array”,
“items”: {
“type”: “object”,
“properties”: {
“text”: {
“type”: “string”
},
“included”: {
“type”: “boolean”
}
}
},
“default”: null
},
“decisionStatus”: {
“type”: “object”,
“properties”: {
“underwritercomments”: {
“type”: “string”
},
“reviewerComments”: {
“type”: “string”
},
“underwriting_approved”: {
“type”: “boolean”
},
“approval_approved”: {
“type”: “boolean”
}
}
}
}
}
https://alpha-pt.neutrinos-apps.com/request/?/case/instance/update-data:
req:
{
“body”: {
“cid”: 6232,
“caseData”: {
“age”: 28,
“dob”: “1998-05-20T00:00:00.000Z”,
“email”: “vainannu@sutherlandglobal.com”,
“address”: “Chennai, Tamil Nadu”,
“features”: [
{
“text”: “Basic Life Insurance”,
“included”: true
},
{
“text”: “TeleMedicine”,
“included”: true
},
{
“text”: “Digital Budgeting App”,
“included”: true
},
{
“text”: “Short Term Disability Cover”,
“included”: false
},
{
“text”: “Extended Life Cover”,
“included”: false
},
{
“text”: “Priority Support”,
“included”: false
}
],
“lastName”: “R”,
“firstName”: “akash”,
“beneficiary”: “Priya R”,
“nomineeInfo”: {
“age”: 27,
“name”: “Priya R”,
“relationship”: “Spouse”
},
“customerInfo”: {
“gender”: “Male”,
“fullName”: “Raguraman R”,
“customerId”: “CUST-10001”,
“phoneNumber”: “9876543210”
},
“coverage_term”: “10 Years”,
“policyDetails”: {
“policyId”: “POL-50001”,
“expiryDate”: “1998-05-20T00:00:00.000Z”,
“policyType”: “Life Insurance”,
“premiumAmount”: 25000,
“coverageAmount”: 5000000,
“inception_date”: “1998-05-20T00:00:00.000Z”
},
“decisionStatus”: {
“reviewerComments”: “”,
“approval_approved”: false,
“underwritercomments”: “approved”,
“underwriting_approved”: false
}
}
},
“path”: “/case/instance/update-data”,
“method”: “post”,
“headers”: {
“Content-Type”: “application/json”
},
“apiAuth”: {
“authType”: “client”,
“ids_url”: {
“type”: “environment”,
“value”: {
“alpha_env”: “IDS_URL”
}
},
“path”: “/token”,
“method”: “post”,
“grant_type”: {
“type”: “string”,
“value”: “client_credentials”
},
“headers”: [
{
“key”: “Content-Type”,
“value”: “application/x-www-form-urlencoded”
}
],
“body”: [
{
“key”: “client_secret”,
“type”: “environment”,
“value”: {
“alpha_env”: “IDS_CLIENT_SECRET”
}
},
{
“key”: “client_id”,
“type”: “environment”,
“value”: {
“alpha_env”: “IDS_CLIENT_ID”
}
}
]
},
“url”: {
“type”: “environment”,
“value”: {
“alpha_env”: “ALPHA_CASE_SERVICE_URL”
}
},
“queryParams”: {
“branch”: “feature/APS-1234”
}
}
@Sam @shas if i click approve button in underwriter page.on the time i need to update the casedata decisionStatus.underwriting_approved to true.but it is taking default value as false.eventhough if i pass true in that approve button also it is taking false.
Hello @Raguraman ,
The Case Decision is a separate API and is not intended to update the case data.
The decision inputs correspond to the inputs configured in the Human Task Assignment section of the BPM flow. You can verify this by checking the BPM configuration.
For example, if the decision input is underwriting_approved and its type is boolean:
- Setting it to
trueindicates that the underwriter has approved the case. - Setting it to
falseindicates that the case has been rejected.
@Raguraman , also update the co object with alpha.co.update() method before the case update call if you wanna update the case data. Case decision doesn’t have impact on case data.
NB: use custom code to update co object.
tips: use debugger in script to explrore more
Hi @Sam @shas
Regarding the requirement:
Task: Build pages enabling Underwriters to view, edit, and submit application data.
I need some clarification on the editing permissions for Underwriters and Reviewers.
What data are they expected to edit, and to what extent should they be allowed to make changes? For example, if a user has already entered their personal details or selected specific features/options during the application process, it may not be appropriate for an Underwriter or Reviewer to modify that information.
Could you please clarify:
-
Which fields should be read-only for Underwriters and Reviewers?
-
Which fields, if any, should they be allowed to edit?
-
Are they only expected to review and approve/reject applications, or can they also update application data?
Also, we checked that filters, search not working on all pages in CM/Admin, can you please confirm that also, from my side we configured that correctly.