Subversion Repositories SmartDukaan

Last modification

• Rev 37194 – 2 h 39 m
• Author: aman

• Log message:

  LOI OTP: report real send outcome instead of always 'OTP Sent Successfully!'
  
  The Send OTP button showed success for any HTTP 200, including the daily-cap
  failure where the controller returned 'Something went wrong..'. Ops could not
  tell a working send from a broken one, so genuine failures were invisible.
  
  - OTPResponse: add 'sent' flag. result=true did not mean anything was
  dispatched - the 2-minute resend throttle returns the previous OTP without
  contacting the gateway.
  - OtpProcessor: set sent=true only on branches that actually dispatch.
  - LoiFormController.sentLoiAcceptanceOtp: return {status, sent, message} with
  the processor's real reason, wrap generateOtp in try/catch so a dispatch
  exception is logged and reported instead of surfacing as a generic 500, and
  log loiId/result/sent/reason.
  - loi-form.js: check the payload; distinct green/amber/red states, re-enable
  the button on failure instead of leaving it stuck on 'Sending...'.
  - common.js: optional error callback on doAjaxRequestHandler /
  doPostAjaxRequestHandler (additive; existing callers unchanged).
  - AppConfig: static resource version 389 -> 390 for the JS change.