7 Commits (a6d859ca8f03691b2fcbdbfff001e7f0900160f6)

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	11 years ago
Rene Krenn	fa2c02ee5f	MT#16045 notopup expiry for balance intervals output ... including "timely" topup periods. +for /api/balanceintervals +and for panel UI, "Contract Balance" contract details section reworked api_dump.pl was simplified accordingly. Change-Id: Ib0c4942b1db059b4fe8ee3343838f516662ca166	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	d54bd5d360	MT#13903 "topup_interval" start mode impl ... The prior "topup" start mode for balance intervals (contract_balances) creates intervals for each top-up using a voucher, resulting in dynamic length. This new "topup_interval" start mode will just align the *first* balance interval upon the topup. Subsequent intervals use the constant interval unit+count specified in the profile package. Melita user story is completely covered now. Change-Id: I0a8b8d73a7fbf054d0aa8b2b1e73a54609fdeee0	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
Rene Krenn	c378681a24	MT#13903 balance interval catchup and resize WIP ... + synchronized contract balance catchup + balance interval resizing upon profile package transitions + dynamic interval length, interval start, carry-over propagation, .. + end-of-month 'preserve' mode correction for strictly aligned month intervals for start_mode=customer "create" timestamp + new api/balanceintervals resource to inspect contracts' balance interval histories + updated affected panel UI controllers + test case with time warps using Time::Fake caveats: - creating an invoice for a given 'period' (month) has to be refactored to select a disitnct balance interval. right now it takes the last interval in the month specified. - generate_invoice.pl is broken and needs a major refactoring Change-Id: I7bb54a83b76e510b1baa573a986d05400a7fec1e	11 years ago