5 Commits (c044e2410a4bddcee04191bc7a9b8e9ba4383689)

Author	SHA1	Message	Date
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	bef06dce91	MT#14301 deleting prof packages instead of terminating ... +profile package details view to overlook associations +voucher count is properly checked before deleting a package +package_id filters for /api/customers and /api/vouchers +Fake::Time replaced by Time::Warp for balance_interval tests +cleanup Change-Id: Idc34220a9d29c115453eeee2907e70a71cf9f0cc	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	2537819f0d	MT#12643 billing networks and multi bill prof WIP ... -properly validate billing mapping intervals -api/contracts and api/customers complete +the problem with updating the "prepaid" preference remains at the moment +billing_mappings field contains future (editable) mappings only, the full schedule is given in a separate field +hal-links to all occurring billing profiles and networks -extended tests: api-customer.t and api-contract.t -api-billingnetworks.t test -billing networks panel controller +search by enclosed IP address -panel UIs for billing networks, customers, contracts +past billing mapping intervals that cannot be edited are displayed by a seperate hfh "block" part of the billing_profiles repeatable -profile packages api, UI +terminating billing profiles (MT#8645) will be broken +fixed now: profile cannot be terminated unless there are: -zero non-terminated customers, whose mappings contain the profile with future or open end -zero profile packages, that link to the profile in either one of their initial-, underrun- or topup profile sets +panel edit should work, termination wip +topup_profiles w/o amounts +contracts/customers API profile_package_id field: +apply the package's initial profiles +api/customer and api/contract profile definition modes (id/profiles/package) +api OK, api-customer.t tests +customer and contract panel UI with selector to specify actual billing mapping, schedule or profile package (same as api) +terminate logic harmonized: profiles, networks, packages +api tests updated +prepare for merging: cleanup, enable tests Change-Id: I6c0dec72f490b5731fc673cd393d6aeb08dd8143	11 years ago