BusinessPlus System/Nucleus
BusinessPlus System/Nucleus
Breadcrumbs

BenefitEnhancement\HR_EMPBENGRP

BenefitEnhancement\HR_EMPBENGRP

 

Start-to-End Scenario: HR Employee Bene Group Process

  1. A New Employee Record is Created

  • Someone in HR enters a new employee into the company system.

  • This action triggers the workflow automatically (it listens for new records in the employee master table).

  1. Workflow Begins

  • The workflow starts its sequence.

  1. Update Instance XML Data

  • The system retrieves the new employee's data.

  • It checks a setting (“HRPY Code”) to determine if benefit assignment for this employee requires approval.

  • The workflow looks up and compiles a list of benefit groups that are set as “default” for employees like this one (based on their department, union, etc.).

  • For each benefit group, it determines which benefit plans are marked as default and gathers their descriptions.

  1. Decision: Is Approval Required?

  • If approval is NOT required:

    • The system moves immediately to assigning the default benefits to the employee.

    • The workflow ends successfully.

    • Example: The HRPY code says “no approval needed for this job title; just assign benefits.”

  • If approval IS required:

    • The system routes the benefit assignment for approval.

    • An approval task is created and sent to the relevant person (usually whoever created the employee record).

  1. Approval Step (“TaskApprovals” Activity)

  • The approver receives a notification or a task in their workflow inbox.

  • They review the proposed default benefits for the new employee.

  • If the approver approves:

    • The process continues, and default benefits are assigned to the employee.

  • If the approver rejects or does nothing:

    • The process records the rejection or stalls until timeout/error rules take over.

  1. Assigning Default Benefits

  • If approved (or if approval was not required), the list of default benefits is attached to the employee’s record.

  • The benefit assignments are updated in the database.

  1. Workflow Ends

  • The process finishes.

  • Any rejections, errors, or rules without a valid route are handled by specific “end,” “error,” or “rejection” handlers to close out the workflow cleanly.