Advanced Search
Search Results
12 total results found
Calculate Driver Advance Payment ver1
Overview A cron job that runs every 5 minutes to process queued tasks and generate flat report records from delivered orders within a specified date range. Used for reporting and finance export (e.g. payment file generation). Task Code Calculate Drive...
Calculate Driver Advance Payment ver2
Overview This is a cron job executing every 5 minutes that computes and generates advance payment records for drivers based on their delivered orders within a specified Malaysia date range, leveraging JobCostSetup to determine payment rates per route. Scoped t...
autoUpdateCIMASupplierDataBySupplierData
Version: Draft — Changes pending production deployment. Overview A cron job that processes queued tasks to sync CIMA supplier delivery data into the Order table. It matches CIMA records against order documents and updates order fields with the supplier-prov...
autoUpdateCIMASupplierData
Version: Draft — Changes pending production deployment. Overview A cron job that processes a queued task to sync CIMA supplier delivery data into a specific order document and its associated order. Unlike the autoUpdateCIMASupplierDataBySupplierData sibling...
Overview — CIMA Supplier Data Flow
Purpose This chapter documents how CIMA supplier delivery data flows into the Order table via background cron jobs. There are two independent entry points (Flow A and Flow B), both ultimately syncing CIMA data into the order. Flow A — CIMA Lorry In/Out Report...
processCimaLorryInoutReports
Version: Draft — Changes pending production deployment. Overview A cron job that picks up queued tasks to parse uploaded CIMA Lorry In/Out Report files. On success, it triggers the next step in Flow A by creating an Auto Update CIMA Supplier Data By Supplie...
Test Guide — Flow A
Purpose Verify that uploading a CIMA Lorry In/Out Report file correctly parses the data, populates CimaDeliveryInfo, and updates the associated Order fields. Prerequisites A valid CIMA Lorry In/Out Report file (correct format) An existing Order with matching...
Test Guide — Flow B
Purpose Verify that uploading an OCR-processed Order Document with autoUpdateFor = CIMA correctly triggers the CIMA supplier data sync and updates the associated Order fields. Prerequisites An existing Order with autoUpdateFor = CIMA on its OrderDocument A m...
Release History
Purpose Central log of all API releases — what changed, why, and when it was deployed. Each entry links to the relevant KB detail pages for full context. Upcoming Release (Pending Deployment) These changes are documented as Version: Draft in their respective...
createMsRpaDownloadCimaLorryInOut
Version: Draft — Changes pending production deployment. Overview A cron job that runs every 2 hours to instruct the RPA to download CIMA Lorry In/Out reports (TRN and DST) from the CIMA portal. It creates two MicroserviceTasks that the RPA picks up, downloa...
Entity Relationships
Version: Draft Overview Six tables form the Driver Performance Feedback system. They cover incident tracking per order, monthly score aggregation, and performance tier management. Entity Relationship Diagram ┌─────────────────────────────┐ │ PerformanceI...
EKA-GPS Knowledge Base
Version: v1.6.0+hotfix.2 | Last Updated: 26Feb2026 1. Overview EKA-GPS is a TCP server microservice that receives real-time GPS telemetry from vehicle tracking devices (trucks), persists location data to MySQL, and manages geofencing-based pickup/delivery w...