7 Commits (2cf0b3f6ba76e236b1cc0d58ff8ff3d1ee19d63a)

Author	SHA1	Message	Date
Guillem Jover	a6d859ca8f	MT#21193 Remove unused dependencies and imports ... The codebase does not use autodie directly, it does indirectly via Sipwise::Base, and the autodie module is part of the standard perl distribution anyway. TryCatch is imported via Sipwise::Base, and that depends on it. The rest are not used anymore in the codebase. Change-Id: Ic08e246cc60d7d151381dff39e0eba517a492e06	10 years ago
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	10 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	10 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	4227fd2522	MT#13201 Enhance voucher API. ... - Use billing_data ACL grants to modify vouchers - Use encryption in UI for voucher code Change-Id: I7711a43db8596d5f733d6c52d2f6608f434b2463	11 years ago
Andreas Granig	2c54106fd0	MT#13201 Implement voucher API ... Change-Id: Ia82579179a29245d51c5ae3d3ea71054ceaf1bf0	11 years ago
Andreas Granig	64d65a10a5	MT#9277 Implement basic voucher management.	11 years ago