Evergreen farms (pos)

Private

Project *AFC APPFORSOLARArrow LogisticsArtificial Intillegence  » Algo Trade Automation  » Algo Trade Manual  » Bulk mail Automation with web interface  » Bulk Mail Service For Bench Sales  » Code Generation Tool  » Cold Emailing Automation (AI-Driven)  » Invoice Inventory Automation  » invoice to inventory for evergreen  » Test Automation  » What's app Bulk messaging with AI agents  » Zelle Payment for evergreenAsk RideCharan Technologies _ DevelopmentEver green Farms USA (static website)Evergreen farms (pos)Evergreen React ApplicationFinwareHackthonLucky BraidsMy Produce StandNexPumpNexZen Printer AgentNoxa_JewelleryOffice Requirments  » Daily Tasks For Madhu  » Employees requirements  » Recruitment senior mern stack developer  » Red MIne Speed  » Senior Mern Stack DeveloperOPT - (USA) UpdatesQA TestersRare FruitsRegal SolarRegal Solar DMRegal Solar Energy_ ReactReliance Home Builders_ reactRemit2AnyRestaurant POSRSVPRushi GardensRV_ EngraverSoloar AppSri Farms _ DMSri_FarmsSuthra QNova LabsTech FourceTechnical RequirementsTechy_DevelopmentTechy_POS Travel Mate

Tracker *Bug Feature Support Testing

Subject *

Description Edit Add an Action History feature to the Coupon Management System to track all important user and system actions performed on coupons. This will provide an audit trail for monitoring, debugging, and compliance purposes. ## Scope Record the following actions in the Action History table whenever they occur: | Event | Trigger | Action Value | | ----------------------------- | --------------------------------- | ----------------- | | Create Coupon | `createCoupon` | `create` | | Update Coupon | `editCoupon` | `update` | | Soft Delete Coupon | `deleteCoupon` | `delete` | | Manual Active/Inactive Toggle | Status toggle in edit/update flow | `status_change` | | Publish Coupon | Publish flow | `publish` | | Auto Activate (Cron) | Scheduled activation job | `auto_activate` | | Auto Deactivate (Cron) | Scheduled deactivation job | `auto_deactivate` | ## Action History Fields Each history record should capture: * Coupon ID * Coupon Code * Action (`create`, `update`, `delete`, `status_change`, `publish`, `auto_activate`, `auto_deactivate`) * Performed By (User ID/System) * Timestamp * Previous Status (if applicable) * New Status (if applicable) * Optional Remarks/Metadata ## Acceptance Criteria * Action history is created whenever a supported event occurs. * Manual actions store the authenticated user as the actor. * Cron-triggered actions store the actor as `System` (or equivalent system user). * History records are immutable after creation. * Existing coupon functionality remains unaffected. * Action history can be queried for future audit/reporting purposes. ## Technical Notes * Integrate history logging into existing coupon service methods. * Reuse the existing `editCoupon` flow for `update` and `status_change` logging where applicable. * Ensure cron jobs create history entries only when an actual status change occurs. * Keep action values standardized: * `create` * `update` * `delete` * `status_change` * `publish` * `auto_activate` * `auto_deactivate`