Subversion Repositories SmartDukaan

Rev

Go to most recent revision | Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
35716 166 d 4 h amit /trunk/ Refactor GrnController and PurchaseOrderController: extract business logic into focused services and fix N+1 query performance issues

- Create InvoiceService: invoice item CRUD, validation, vendor price matching
- Create GrnRequestService: GRN request lifecycle, mismatch resolution state machine
- Create DebitNoteService: debit note generation, PDF model building
- Move PO amendment logic from PurchaseOrderController to PurchaseOrderService
- Delegate generateDebitNote from PurchaseOrderServiceImpl to DebitNoteService
- Thin GrnController from ~1215 to ~717 lines, remove 15 unused autowired dependencies
- Thin PurchaseOrderController editPurchaseOrder from 40+ lines to 3 lines

Performance fixes:
- InvoiceServiceImpl.validateInvoiceDetail: batch item/vendor pricing/GST loading (4N+3 queries -> ~5)
- DebitNoteServiceImpl: batch item loading in buildDebitNotePdfModel and generateDebitNote
- GrnController.generateDebitNote: eliminate 2 redundant DB fetches
- Replace 3x supplierRepository.selectAll() with targeted selectBySupplierIds()
 
35679 168 d 11 h ranu /trunk/ calling webhook updated  
35674 169 d 4 h amit /trunk/profitmandi-fofo/src/main/ Add multi-month duration option for manual partner category upgrade (up to 3 months)  
35672 169 d 8 h ranu /trunk/ code commit for calling target / retailer contact  
35670 169 d 9 h ranu /trunk/ code commit for calling target / retailer contact  
35669 169 d 10 h ranu /trunk/ code commit for calling target / retailer contact  
35660 171 d 10 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/ code commit for calling target / retailer contact  
35654 171 d 16 h ranu /trunk/ code commit for calling target / retailer contact  
35648 172 d 17 h ranu /trunk/ code commit for calling target / retailer contact  
35646 173 d 10 h aman /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/ Fix:Dsm Code update null check  
35645 173 d 13 h ranu /trunk/ code commit for calling target  
35640 175 d 12 h amit /trunk/profitmandi-fofo/src/main/ Skip escalations in ticket overview Message column, compact escalation styling in detail dialog

- Pass lastMessageMap to ticket overview templates for all three views
(myTicket, managerTicket, myPartnerTicket)
- Template Message column prefers lastMessageMap over activityMap
- Escalation activities in detail dialog render as compact centered
system messages with pill styling instead of chat bubbles
- Add .system-activity CSS for compact centered gray pill style
 
35631 175 d 15 h ranu /trunk/ code commit for calling target  
35628 176 d 11 h amit /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/ Commented dashobard  
35626 176 d 11 h amit /trunk/ Ticket system: add unread tracking, pagination, search, and partner notifications  
35624 176 d 12 h ranu /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/ web hook deploy  
35617 178 d 9 h amit /trunk/ Filter invisible subcategory tickets for CRM and end users only

- CRM users: Cannot see tickets with visibility=0 subcategories
- Sales/RBM/ABM users: Can see all tickets (no filtering)
- End users in web module: CRM users filtered, others see all
- Uses getTicketSubCategoryMap() for efficient batch lookup
- Named query filters by tbc.visibility=true for recent tickets
 
35607 178 d 11 h amit /trunk/profitmandi-fofo/src/main/java/com/spice/profitmandi/web/controller/ Fix partner position assignment error for newly added partners

- Changed validation from cached retailerService.getFofoRetailers(false) to direct fofoStoreRepository.selectAll() query
- This ensures newly added partners are validated correctly without waiting for cache to expire (30 mins)
 
35603 178 d 15 h amit /trunk/profitmandi-fofo/src/main/ Allow Sales and RBM teams to resolve their own category tickets

- Sales team can now resolve tickets in Sales category
- RBM team can now resolve tickets in RBM category
- CRM team can still resolve all tickets
- Added isSalesUser, isRbmUser flags and category IDs to template model
- Updated ticket.vm canResolve logic to check user category against ticket category
 
35601 178 d 16 h amit /trunk/profitmandi-fofo/src/main/ Filter out Sales/RBM Escalation tickets from CRM user's My Tickets view

- CRM users should not see Sales Escalation (84) and RBM Escalation (83) subcategory tickets
- These escalation tickets are internal and not relevant for CRM team
 

Show All