-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Low
-
Affects Version/s: None
-
None
-
FLW Sprint 54, FLW Sprint 55, FLW Sprint 56
-
FLW Mobile App
-
UAT
Identify the SSD Portal configurations/data that can change frequently and may impact the AMRIT incentive calculation, approval, claim, or payment workflow. Evaluate whether these changes can be automatically pushed from SSD to AMRIT using webhooks.
Changes to identify
- Incentive Activity
- New activity added
- Activity removed/deactivated
- Activity code changed
- Activity name changed
- Incentive Amount
- Incentive amount/rate changes
- Activity-wise payment amount changes
- State-specific incentive amount changes
- Eligibility / Business Rules
- Eligibility criteria changes
- Activity validation rules
- Maximum/minimum limits
- Frequency/monthly limits
- Effective date changes
- ASHA / User Mapping
- ASHA registration/status changes
- ASHA mapped to facility changes
- Supervisor/ANM/CHO mapping changes
- Employee/user ID changes
- Approval Workflow
- Approval levels change
- Approver mapping changes
- Claim/verification status changes
- Approval/rejection rules
- Payment / Claim Configuration
- Claim window changes
- Payment status changes
- Payment eligibility changes
- Bank/account/payment-related status changes
- State-specific Configuration
- Assam and Chhattisgarh may have different incentive rules.
- Any change in state configuration should be identified and synchronized correctly.