Alpha : What is the correct way to attach wfData in Alpha when creating a case

Neutrinos Platform
1

I’m using a curl command to create a case and I’m passing a parameter called wfData (as shown in the screenshot). However, I’ve noticed that even if I don’t pass wfData, the case still gets created successfully.

image
image1237×735 59.4 KB

Now, when I do pass the wfData parameter — what is the expected behavior? Should the output/result from the Reels workflow be automatically attached to the case response?

For example, when I open the case in Workbench using the created caseID, should it include a Reels result object? Because in my testing, it doesn’t. I’m wondering if I’m doing something wrong with the payload format when sending the request.

I’m still unclear about the exact role of the Reels integration in this assignment. Can someone please explain what it’s supposed to do, and what the expected outcome is when we pass wfData during case creation?

1 Like
2

Hi @shubham.dhamne,

It will create the case successfully.
wfData is data used for BPM workflow

3

Hey @shubham.dhamne , the assignment assumes that you have completed a reels assignment. And, the workflow that is being invoked takes the process variable step_rules_request as an input and internally triggers a Reels Workflow which is being passed as a configuration here.

So, if you have a workflow in and have deployed it, it invoke that Reels Workflow with the above Workflow Id.

4

Here’s my current understanding — I’d appreciate clarification on whether this is correct:

  1. Normally, in a jBPM project, we set up both STP and NSTP scenarios.

  2. A method inside jBPM can call the Reels workflow, which applies rules to decide whether a case is STP or NSTP.

  3. Based on that decision:

    • STP cases are handled fully within jBPM.

    • NSTP cases are routed to the Alpha Workbench for human decision-making.

  4. jBPM generates a Swagger spec with APIs to create and manage cases (e.g. create case instance, update case, decision-making).

  5. We can use Postman or Swagger UI to create a case via those APIs, optionally passing wfData (the input for Reels rules).

  6. Once the case is created, it appears in Alpha Workbench:

    • First on the Underwriter Decision page.

    • After that, it moves to Reviewer Approval.

  7. Depending on their decisions, the case is either approved or rejected and the workflow completes.

    Now, in this assignment, steps 1 to 4 (jBPM, Reels, Swagger generation) are already done for us. So no need of doing anyting about reels in assignment correct?

@Sam

1 Like
5

Hello @shubham.dhamne ,

  1. Case Creation:

    • When a case is created, the BPM assignment flow starts immediately.

    • At this stage, the system does not check whether the case is STP (Straight Through Processing) or Non-STP. This determination happens later inside the BPM flow.

  2. Workflow Execution:

    • Providing wfData with any deployed workflow ID triggers the Execute Rules API.

  3. Case Types:

    • STP Cases:

      • These cases require no human intervention.

      • The process completes automatically.

    • Non-STP Cases:

      • These require human tasks, such as actions from underwriters or reviewers.

      • If you belong to a relevant human task group and the case is Non-STP, it will appear in your group task queue and eventually in My Tasks.

  4. Process Visibility:

    • The imported BPM project and associated human tasks are visible on the Process Page.

    • Generating pages for each task allows you to view them on the Case Details page.

  5. Flow Example:

    • Approval by Underwriter: Case moves to the next human task (e.g., reviewer).

    • Approval by Reviewer: No further human intervention is required.

    • Rejection: The process continues following the defined workflow path.

      Hope this helps

3 Likes