7 Commits (e9580d2e9d2b4e96de11ea502d07200356d6c04d)

Author	SHA1	Message	Date
Andreas Granig	04a64e1493	MT#16465 partly remove namespace::sweep and others ... Remove namespace::sweep Remove MooseX stuff Remove perl5i Remove Moose where possible Change-Id: I4f873afb466f4e58a04c3304ff74df2185470b03	11 years ago
Rene Krenn	7f7e3332d1	MT#15477 topup log ... any *attempt* of a top-up request should be logged. +create top-up log records for api in order to record failed top-up requests as well, the somewhat tricky thing is to have two separate transactions here +propery casting of topup request json field values to numbers etc., so the transaction for creating the log entry cannot fail and e.g. requests with subscriber_id='blah' are recorded correctly +new "request_token" parameter for /api/topupvoucher and /api/topupcash, to identify and filter for particular requests. +topup log api resource +topup log api tests +fix to correctly reject used vouchers +topup log panel UI +fix for balanceintervals.t threaded tests Change-Id: I86eb845f6173803705b12cc7e5cdbac9a3153a0a	11 years ago
Rene Krenn	07c9d1955d	MT#14255 add cash_balance underrun logic ... in short: whenever the contract_balances "cash_balance" is about to decrease, it might drop below thresholds defined by a contract's profile package. in that case, subscribers are to be locked and/or underrun billing profile sets are to be applied. this commit also contains some minor fixes: +when creating/editing profile packages, all billing profiles of initial, topup, underrun sets must show the same interval_free_cash and interval_free_time values. there was also a problem with adding profile sets to packages that use profile with prepaid = 1 (see ticket 14301) +when editing packages using the panel UI, the validation was not properly invoked (!) +the frequency of topups has to be limited to 1 per second. +updating the "lock" subscriber prior to editing or viewing it in the panel UI was added. +topup cash and topup voucher panel UI added +when aquiring multiple contract row locks at once, no joined tables are used any mure. the number of row locks is therefore minimal now (see ticket 14903) +rework of updating prepaid subscriber preference Change-Id: Ideb0fec2404ca10b3ac5d8735f53620d0c3a24ed	11 years ago
Rene Krenn	5a182d037a	MT#14631 topupcash didn't process package id ... Change-Id: Ic425f747b220d3614ce37145c103206a5c37667b	11 years ago
Rene Krenn	bd9f67040d	MT#13903 topupvoucher and topupcash ... +applying profile package and billing mappings +testcase in api-balanceintervals.t +caveats: to meet melita's user story, an additional 'topup_interval' interval start mode will be required. the currently implemented 'topup' start mode restarts intervals upon every topup and therefore does not provide constantinterval lengths. Change-Id: I0a4898783c023749994e94e6909833a42debe259	11 years ago
Andreas Granig	9a9d5772ce	MT#13903 Add voucher/cash topup forms for API ... Change-Id: I0a32d1239ca011b46ee69e5b095d364802b92565	11 years ago
Andreas Granig	521fc6a59f	MT#13929 Add voucher topup skeleton ... Change-Id: Ib8080cd7783e2c060b055599244f0f3856761317	11 years ago