1 $Id: TODO,v 1.33 1999-07-08 11:40:40 ivan Exp $
3 If you are interested in helping with any of these, please join the mailing
4 list (send a blank message to ivan-freeside-subscribe@sisd.com) to avoid
9 grep 'uncomment this to encrypt password immediately' site_perl/svc_acct.pm
10 Not to say that it shouldn't be a configurable option.
12 in site_perl/cust_main_invoice.pm (elsewhere?), error out if mydomain config file is gone
13 (at least until the idea of a default domain goes away)
15 FS::Record::qsearch does an eval every loop iteration (which is itself not
16 guaranteed to work across all DBD's and should be fixed). This has got to be
17 slow. Fix it. (I think recent Perls might have a way to accept a variable
18 there, no eval needed?)
20 Could you have added /bin/sync, /sbin/shutdown, and /bin/halt to the
21 `shells' configuration file before importing, and removed them afterwords?
22 (even better if svc_acct.import did that automatically - it could just
23 munge and restore @FS::svc_acct::shells... hmm.)
25 > BTW, Ivan, I am trying to verify in an additional database table that a
26 > particular user doesn't exist. This database is used to store email aliases a$
27 > additional POP boxes for our customers (kinda like AOL allows). I have toyed
28 > with the idea of just writing the aliases to an email only svc_acct that
29 > doesn't write to the password file, but that isn't really how I want to do it.
31 Actually, I think that's a pretty good way to do it. Cerkit contributed
32 support a little while back for svc_acct.pm and svc_acct.export for
33 multiple export targets. It needs to be cleaned up and documented, which
34 I'll try to get to soon. For this to work correctly, the svc_acct_sm
35 table should go away, along with the concept of a "default" domain.
37 default setting for new packages should allow all agents to purchase them...
38 with a config file for the old behaviour
40 replace Term::Query with Quiz::Question?
42 Check config file reading stuff from CPAN
44 Authorizenet module from CPAN!
46 <http://www.math.fu-berlin.de/~leitner/mutt/faq.html> has a good y2k complience
49 I'm hoping Freeside can support arbitrailly complex pricing plans
50 because of a simple concept: all prices are perl expressions. So if
51 you use `19.95' for example, perl evalates that to be `19.95'. But if
52 you need to do a complex pricing scheme, you just need to write an
53 appropriate perl expression, which will most likely pull data from the
54 database to return pricing. Some things will already log to SQL; for
55 example most RADIUS servers can or have a patch available. Getting
56 Freeside to bill based on any sort of data then becomes a matter of
57 importing the data into the database.
59 There are some issues involved with pro-rating, partial month charges,
60 that sort of thing. Expressions will need a standard way to have the
61 applicable time/data ranges passed to them. Also the expressions are
62 currently running under the Safe perl module, and the opmask might not
63 be right in all situations. I'll try to spend some time working on
64 this if you are using it.
66 > 2. can customers view their bills on-line.
68 Not yet; it needs to be proxied from Freeside to a customer web server in
69 a secure way using something not completely unlike the fs_passwd,
70 fs_passwdd, fs_passwd_server trio.
73 > Lastly, if someone over pays on an invoice, the credit part does not flow
74 > over to other invoices..
76 The total balance flows over correctly, but individual payments don't.
77 The code you're looking for is in FS::cust_pay::insert
79 The question of what to do with overpayments that don't have another
80 invoice to flow into (yet.. or possibly not) is still an open one. The
81 legacy system Freeside replaced long ago had a separate place for this
82 (payments waiting for an invoice) for each customer, and it gave our
86 option to relax username uniqueness in favor of username+domain or mail/shell
87 vs. radius to ease import for isp's with namespace problems or who buy others.
89 do i have to store anything for radius realms besides regular radius attributes
90 (which are handled fine now)?
92 warn or complain or something when invoice_from is empty (and we use it)
94 Right now Freeside uses the `freq' field of a package definition as a
95 number of months. The specific section of code you're looking for is in
98 #change this bit to use Date::Manip?
99 #$sdate=$cust_pkg->bill || time;
100 #$sdate=$cust_pkg->bill || $time;
101 $sdate = $cust_pkg->bill || $cust_pkg->setup || $time;
102 my ($sec,$min,$hour,$mday,$mon,$year) =
103 (localtime($sdate) )[0,1,2,3,4,5];
104 $mon += $part_pkg->getfield('freq');
105 until ( $mon < 12 ) { $mon -= 12; $year++; }
106 $cust_pkg->setfield('bill',
107 timelocal($sec,$min,$hour,$mday,$mon,$year));
108 $cust_pkg_mod_flag = 1;
110 ..and when I went poking for this, looks like it tells us just what needs
111 to be done! Hehehe...
113 Date::Manip can handle cool things like "+ 1 month" (actually the current
114 case of /^(\d+)$/ would have to be added as a special case of "+ $1
115 month") and "+ 30 days" (what you need) and even "+ 5 business days" !
118 On Wed, Apr 28, 1999 at 08:38:16PM +0000, Kristian Hoffmann wrote:
119 > I can't quite seem to figure out how this exporting works. From what I
120 > understand, when you run svc_acct.export, it rewrites the /etc/passwd,
121 > /etc/shadow, etc. files. Is this only for initial setups with the
122 > export hooks being in the pm's?
124 You can use both, or just one method. The configuration files control
125 this. One of the things in the TODO is to take out the last few things
126 that aren't customizable wrt this and put them in config files.
128 http://www.daemonnews.org/199905/user-mgmt.html
130 Term::Query doesn't install out of the box from CPAN. Fix it (and get it
131 submitted upstream!), or remove requirement from bin/svc_acct.import and
132 bin/svc_acct_sm.import and take it out of the install instructions.
134 use this cool link to explain the Freeside API
135 ftp://cpan.nas.nasa.gov/pub/perl/CPAN/doc/FMTEYEWTK/easy_objects.html
137 Multiple tax rates by geographic region (county, state, and county) are
138 supported; just choose View/Edit tax rates from the main menu.
140 Multiple tax rates by package are not (yet) supported.
142 On Wed, Jul 07, 1999 at 12:13:36PM -0400, Shaun Batterton wrote:
143 > How would you handle something like multiple tax rates and multiple
144 > states? For example in Connecticut, they just changed computer and/or
145 > data processing services to 3% (whatever that is), and everything else
149 > Second, when trying to add a new user I get two types of errors; first one
150 > is when I place an e-mail address and select the "submit," Freeside
151 > complains with "Error: Unknown local account (specified literally)"
153 You probably put a (local) email address in for email invoices. Freeside
154 stores these as references to the database records, so (for example) they
155 follow username changes.
157 I'm guessing you put in the email address that you were creating, and got
158 that error because it didn't exist yet. Sounds like a buglet to me. I'll
159 try to fix that soon; in the meantime you can add the invoicing email
162 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
163 and use the numeric types, which *finally* work right.
164 On Sat, Apr 24, 1999 at 12:52:00PM -0700, Mr. Poet wrote:
166 > Error creating cust_bill record: ERROR: parser:
167 > attribute 'charged' is of type 'money' but expression
168 > is of type 'float8' You will need to rewrite or cast
169 > the expression ! Check updated but unbilled packages
172 Postgres `money' time sucks rocks anyway. I'll probably just require 6.5
173 and use the numeric types, which *finally* work right (well, according to
174 the web site, anyway).
176 In the mean-time, this could probably be fixed with the reverse of
177 the kludge in FS::Record::new. This removes `$' and `,' from money fields
178 coming out of the database. Something which fixed up the data so Postgres
179 was happy with it could go in FS::Record::_quote, for data going into the
182 our data display problem might be a Freeside problem wrt not using
183 Oracle-compatible DBI syntax (uses the return value from $sth->execute as
184 a number of rows). Fixing this is on the TODO.
186 hooks for arbitrary commands out of configuration files
187 svc_acct.pm svc_acct_sm.pm etc.
189 Add this to a FAQ, along with doing it for middle names:
192 > What I'm finding difficult is how to easily
193 > customize fields. For example, I am trying to add a "middle name" field
194 > to the Customer Edit, view, etc. If I'm going about it right, it appears
195 > I have to edit the cust_main.cgi under edit and edit/process and the
196 > site_perl/cust_main.pm, as well as other things. Perhaps you could shed
197 > some light on the best way of doing this.
199 You have the basic idea. To implement that completely, I would:
200 - Add the new field to bin/fs-setup for new users
201 - Document the field in htdocs/docs/schema.html
202 - Document the change in a new file, htdocs/docs/upgrade4.html
203 * Run bin/dbdef-create
204 * Add the new field to edit/cust_main.cgi and edit/process/cust_main.cgi
206 For bonus points, I'd grep around for the various bits which use "$first
207 $last" or "$last, $first" and replace them with a method call in cust_main.pm,
208 , like search/cust_main.cgi
210 document security model:
211 Don't forget about Apache usernames - since, via the mapsecrets file, each
212 user can login to the SQL database with a different username and
213 password, you can utitilize the security model of the SQL database as
214 well. Also, each username here can point to a different configuration
215 directory where you could store user-specific configuration info. Then
216 you could link each username to one-to-many agents.
217 (The web demo works using a trivial version of this.)
219 Yes, queue processing or the equivalent via checkpoint fields on various
220 talbes (which you pick up via a pretty simple SELECT) would be really
223 default (and ordering) state/county/country config file
225 cust_main_county table to provide a preferred ordering, so the most common
226 entries would be at the top of the selection box. automatically, based on
229 hmm... maybe svc_acct__shell should check off the legal shells list if
230 applicable? yeah... cool.
232 payinfo field should me much larger than 16
235 [Mon Apr 12 20:31:21 1999] [error] [Mon Apr 12 20:31:21 1999] null: Error closing true: Broken pipe at /usr/local/lib/site_perl/FS/cust_main.pm line 615.
237 javascript (yuck!) "are you sure?" confirmation on cancelations, etc.
238 (view/cust_pkg and view/svc_*)
240 get rid of time2str("%D") which formats dates in a non-y2k-safe looking fashion
241 (all the actual date handling uses UNIX timestamps and is fine)
243 uncomment expire in view/cust_pkg.cgi and find the expire cron from fsold
246 one-time/per-customer/? changes in rates and descriptions ('remembered
247 invoices'): implement by creating a new package on the fly... but it isn't
248 associated with any agent types so it won't show up for other customers to buy.
249 (but also... make sure they go away when the customer does! - need this? :
250 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
251 with custnum and partpkg (like type_pkgs)
252 (what happens if you hit "custom pricing" but the pricing is already custom?)
254 Lay out any remaining ugly forms better.
256 remove "records identical" warning? gets in the way of more important stuff.
257 or fix logic which tries to update identical records??
258 1.2 should be quiet enough that the error log is useful, hopefully.
260 Postgres has a maximum column length of 31 characters (but see NAMEDATALEN in
261 postgres_ext.h). part_svc has columns like: svc_acct__radius_Attribute_flag
262 (22 characters!) It seems that stuff over the limit is silently ignored,
263 so we get 4 characters back. So, Radius_Attributes are max 13 characters with
264 stock Postgres. see rfc2138 for what's affected
265 What's a good fix? (besides recompiling postgres with NAMEDATALEN 64)
266 (mysql has a 64 character max column length. others?)
268 [Mon Mar 29 06:57:56 1999] -e: Use of uninitialized value at /usr/lib/perl5/Date/Format.pm line 333.
269 (when sending mail in cust_main.pm::bill or svc_domain.pm)
271 look at DBIx::Recordset! (and Tie::DBI, and...)
273 undefined conf/lpr gives this uninfomative error:
274 [Fri Feb 26 16:42:36 1999] bill.cgi: Can't do bidirectional pipe at
276 l5/site_perl/FS/cust_main.pm line 629.
277 [Fri Feb 26 16:42:38 1999] bill.cgi: Error closing : Broken pipe at
279 l5/site_perl/FS/cust_main.pm line 631.
280 So give a meaningful error!
282 password and slipip stuff in svc_acct.pm store need to be split into two fields or something, so the silliness in svc_acct.pm and svc_acct.export with looking at the data to decide what to do with it can be fixed
284 i10n: Apache::Language
286 Apache::Session? Other useful Apache::* ?
288 email invoices are only sent for the BILL payby. If setup, should statements
289 (since they're not invoices) be sent for COMP and CARD as well?
291 $cgi->keywords is causing the (hard to trace) error:
292 Use of uninitialized value at (eval 5) line 5
294 edit/cust_main.cgi gives an uninformative error message:
295 > Can't call method "agentnum" without a package or object reference at
296 > /usr/local/apache-ssl/htdocs/freeside/edit/cust_main.cgi line 116.
297 if there are no agents.
299 (is this missing on any web screens? (easy with $cust_svc->label)
300 Add the ability for services to filter information up to the package level
301 for web screens, so you can select a particlar package based
302 on username or domain name, etc.
304 Allow a cancelled/suspended/active status from packages to bubble up to
305 the customer lists. Put active, then suspended, then cancelled accounts.
306 Similar ordering on the package listing inside a single customer.
308 false laziness: edit/cust_main.cgi got some parts copied from edit/svc_acct.cgi
309 the web interface in general needs to be redone in a more abstract way.
311 false laziness: some of search/svc_acct_sm.cgi was copied to search/svc_domain.cgi. but web interface in general needs to be rewritten in a mucho cleaner way.
313 Portability: in FS::Record, $sth->execute does not return a number of rows for all DBD's. see man DBI
315 subroutine the where clause (eventually all SQL) as OO perhaps (has anyone done this?)
317 add a select method to FS::Record?
319 one-time/per-customer/? changes in rates and descriptions ('remembered
320 invoices'): implement by creating a new package on the fly... but it isn't
321 associated with any agent types so it won't show up for other customers to buy.
322 (but also... make sure they go away when the customer does! - need this? :
323 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
324 with custnum and partpkg (like type_pkgs)
325 (what happens if you hit "custom pricing" but the pricing is already custom?)
327 You can't delete the stuff under administration yet. Add this,
328 _including_ making sure the thing you are deleting is not in use!
330 add links on view/cust_main.cgi to setup services, like view/cust_pkg.cgi
332 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
333 loading of configuration. (pry need same idea, but will run immediately if
334 context allows). Looks like error is masked by 'use FS::cust_svc' which in
335 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
338 Allow a cancelled/suspended/active status from packages to bubble up to
339 the customer lists. Put active, then suspended, then cancelled accounts.
340 Similar ordering on the package listing inside a single customer.
342 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
345 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
347 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
349 .us domains and others!
350 site_perl/svc_domain.cgi (hmm... or maybe should have a button? or maybe svc_domain.pm should handle this) should set $whois_hack for non-internic domains, so you can add them...
352 turn on the depriciation warnings for [e]idiot in FS::CGI. Stop using [e]idiot
353 the last places it is (htdocs/search/ htdocs/misc/ htdocs/misc/process)
355 (test cust_main.pm with cybercash v2 and v3, especially with the callback
356 stuff AND with mod_perl w/cybercash v2 kludge in package main)
357 (callback stuff should be eliminated by now)
359 bah, table/itable/*table in FS::CGI is silly.
361 doc Apache::AuthDBI as well
363 Provide sample httpd.conf files.
365 hey look: Tie::DBI! Check that out. Override its commit with something that
366 does perl-side caching for ? a performance improvement and as an emulation
367 layer to plug in f.ex mysql's atomic transactions
369 Record.pm uses does some non-portable DBI things. MySQL and Pg seem fine.
370 Fix it anyway unless we migrate to Tie::DBI.
374 cust_bill.pm uses '==' comparison on dates because they're currently ints
376 config file for allowed card types
378 write instructions for adding new services w/svc_Common.pm. Get rid of all
379 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
382 test and document libapache-dbi-logger (woo!)
384 radius logfile parsing and perl expression check.
386 Fix in cust_bill BUGS:
387 There is an off-by-one error in print_text which causes a visual error (Page 1
388 of 2 printed on some single-page invoices).
390 fields should be a method against a FS::Record or derived object, as well as
391 being something you can call as FS::Record::fields('tablename'). Might
392 even be able to handle both in the same routine (that would be neato).
394 Immediate removal of incorrectly entered check payments (can't take too
395 long to do this, or accounting is fubared).
397 Add code to move from one service to another (POP to SLIP/PPP, etc.).
398 This _should_ be possible by working off the rules in part_svc rather than
399 hardcoding anything in. The rules in part_svc may need some elaboration,
402 Use ut_ FS::Record methods in all derived classes (possibly some from dbdef?... eventually all from dbdef??? - but then `dbdef-create' would be impossible as there would be metadata we couldn't ask the backend for. hmm.)
404 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
405 Expand the HylaFAX interface (also possibly generalize for other fax
406 softwar ie .comfaxe); allow things like arbitrary faxes of sales
407 literature, specific troubleshooting documents and so on. Maybe even
408 allow users to do this (though that might not belong in Freeside).
410 misc/process/sendconfig.cgi
411 Configure fax recipients via a separate box rather than using the finger
412 name or first+last from cust_main.
414 move all phone number logic out of Freeside - let HylaFAX or whatever
417 soundex searches for customer name and company? where are free soundex tools? (standard Text::Soundex duh) - I could have sworn I saw Text::Soundex on CPAN?!
419 should be able to link on some field in email alias (right now you can link
420 on username or domain with a fallback to svcnum)
422 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
424 deleting an svc_domain should delete all associated svc_acct_sm records.
425 same with a svc_acct.
427 periodic password encrypter
429 Automated, configurable notification, suspension and cancellation of
434 Allow for a future setup date on accounts.
436 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
439 edit (not just import, export and allow default/fixed) arbitrary radius stuff
441 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
443 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
445 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
447 what else (besides l10n) for i18n? (money!)
449 audit htdocs/* for things that should be libraried and things that should be
450 new methods on the objects (need to do this before implementing a new UI)
451 all the big things are done
453 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
454 Decide based on whether or not the "error" should show up in logs.
456 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
457 for HTML creation. Maybe Embperl or something along those lines. ?
459 When running bin/bill, Fix this (Annoying but harmless):
460 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
461 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
462 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
464 all cgi (but internal to the isp) places where package names are listed should also have
465 comment (like agent_type)
467 clean up $recref and other silliness and use -> calls where possible, or
468 one other alternative. clean up everything else.
469 should FS::Record use Tie::Hash? That would be very clean, but where do we
470 store the other information? Maybe you could ask any FS::Record object for a
473 change all file access from regular open(FILE,) stuff to OO, because of
474 problems scoping and passing filehandles like that.
476 the web interface should create a new object and use it instead of a blank
477 form for new records. the create method of svc_ objects should set defaults
480 sub check in man FS::table_name should be rewriteen. Get rid of $recref
481 stuff. Make sure all fields that refer to other database are checked.
483 Integration with signup disks (are there any free ones? Netscape?).
485 One-button cancel (+refund) for lusers who can't get online.
487 Keep information on virtual web servers (hostname, IP, host machine,
488 directory, etc.) and export this information for importation into the ISPs
491 Remove requirement that the first mail alias be the catchall? Still make
492 sure only one catchall per domain is defined in any case, of course.
494 Ability to move cust_pkg records from one customer to another? (proably
495 will need to cancel the old and create a new like when we move services
498 Auto-increment expired cards one year, and try again?
500 More non-US stuff - zip codes, country codes, foreign currencies, etc.
502 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
504 Nicer set of integrated reporting possibilities, like weekly sales totals
505 by customer, package, agent, referral, etc., aging reports sorted by lots
506 of different things, and so on.
508 Client/server setup for users to modify their own passwords, shells, etc,
509 via passwd or secure web interface (prelminary passwd/chfn/chsh
510 replacement done). Complicated by the fact that we don't want to allow
511 incoming connections to the machine running Freeside, so we probably need
512 to have a daemon on each external shell or web machine that is contacted
513 by the Freeside machine. Be very very careful for both traditional
514 security issues and DoS problems.
516 An extension of the above to allow users to modify selected parts of their
517 own information, order and cancel services. A web interface for new
520 Expand domain name stuff to house all domain information. Export
521 named.boot/named.conf (primary and secondary) and named.{domain} files.
522 Add more registries (not just InterNIC's com org net edu)
524 Nice postscript paper invoices, rather than current ASCII invoices.
526 think about race-condititions in FS::Record and derived ->check ->insert
527 and so on, uid and username checks in svc_acct, etc.
529 Move to rsync over ssh file exportation rather than scp.
531 check 'n fix the proactive password checker. (cracklib?)
533 refunds of "BILL" payments: generate pseudo-check.
535 write batch senders and batch parsers for the different credit card processors
537 More CC processors/methods.
539 you should be able to fiddle the setup date in cust_pkg. (at least initially)
541 delete options in administration section
543 write a generic batch senders and batch parsers.
545 need a way to override svc_acct export on a per-machine basis; just use config files based on machine name i suppose; document that. (no, import desync_hosts
546 type stuff from cerkit)
548 add a table with column of export services (passwd, shadow, master.passwd, .qmail file update, dns update, etc.) and rows machine groups and whether or not to export that (and any necessary parameters). wasn't matt (vunderkid, not matt@michweb) working on this? find him? each machine goes in a group of its own as well as a group based on function. add a table with only svcpart and machine group. now, when you import from each machine, it can get its own accounts with one svcpart and universal accounts with another svcpart. (though that does make the username duplicate checking more interesting)
550 you should be able to get column types as a method against an FS::Record object
551 as well as dbdef->table($table)->column($column)->type
553 move to perl module for fuzzy and soundex searching.
555 package view needs to list extraneous services; we need to prevent the
556 creation of them so this never happens (and mark it as such in the source)
557 (the creation problem should be fixed - though they will still happen if people
558 fsck around in the data manually, so list them anyway)
560 add attribute dictionary to fs-setup as a menu, plus analyze users file to
563 Check for and report on duplicate billing accounts (cust_main, though many
564 will have a need for these so probably don't disable them outright.)
566 create a ->warn as well as a ->check method for all FS::table classes?
569 something to automate making a release and updating the web demo
571 export a debian-style (also redhat and?) /etc/group file aswell!
573 svc_acct_sm.import qmail import should pull in recipientmap people too.
575 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
576 should fork and do them in a child.
578 i18n/l10n: take ALL messages and catalog them in english.txt or in database or something, so we can eventually go int'l. int'l currency support would be a help aswell.
580 get some of { city, county, state, zip } from the missing bits if
581 possible (where can i get the data to do this? usps.gov?)
583 additional interfaces (perltk? java?)
585 Put the GPL notice in all files.
587 integrate w/IDEA's signup server
589 $cust_bill->owed database field to be eliminated, replaced by a method call
590 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
591 same for cust_credit->credited
593 Export quota information.
595 move all configuration to a central place. maybe in blob's in the
596 database. maybe even things like the code to execute when a username is
597 changed can be in there, so less of the distributed scripts change between
600 Implement setup and recurring fees as Safe perl expressions rather than
601 numbers, to allow for variable-rate services. Backwards compatibility is
602 obtained because { 43 } in perl is still 43. :) Define API to pass
603 starting and ending dates and any other necessary data to expression
604 (fees are currently evaluated as Safe expressions but more work needs to
605 be done to define an opmask for various needs, write examples
606 (usage-based billing, etc.) and so on).
608 Add the ability to modify the next billing date in cust_pkg, and take
609 appropriate action. This will allow the implementation of pro-rate/1st of
610 the month billing as well as the ability to manually fiddle with
611 anniversary dates in cust_pkg, so you can sync a customer's anniversary
612 date even if you're using anniversary billing (manually or automatically).
613 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
614 charges - anything more complicated should figure it out itself given
615 starting and ending dates [document that!])
617 Daily Radius log parsing into database; other logfile formats?
619 Callbacks to enforce hourly limits on accounts (suspend until the end of
620 the billing period?), for those who limit customers rather than tack on
623 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
624 example) need to charge tax on equipment but not service (separate flags
625 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
626 recur_tax and recur_notax fees, and possibly something more flexible if
629 Allow for a variable number of invoices for customers who need multiple
632 Add a mail alias service with table svc_acct (not domain mail aliasing
633 which is domain with svc_acct_sm)
635 (bring back from fsold) Change customer comment field from its current kludge to something more
638 Better work orders with more information. Should eventually open a ticket
639 when we have such a thing.
641 edit/process/svc_wo.cgi
642 Call tracking and trouble tickets.
644 More accoutability for complimentary accounts: approval, expiration, term
645 (no more than x months in advance) and notification.
646 Flag particular users (or all users, for that matter) as having their
647 passwords hidden and/or locked from users of Freeside (maybe need Freeside
648 security levels first?).
650 Better Freeside-level configurable access, for those ISP's who have
651 employees they can't trust. Right now you're "stuck" with setting up
652 .htaccess stuff yourself. This should really just be integrated.
654 configuration/setup should get web interface
656 /usr/local/etc/freeside should be configurable
658 (probably as part of some automated installation process?)
660 This requires some serious magic in FS::Record:
661 ok, if date_type in fs-setup is to be something besides int,
662 now we need to create wrappers
663 for them so they behave identically across RDBMS's, ie date pops out as as
664 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
665 is a string not a hashref for backwards compatibility?) and so on. (remember
666 to treat '0' as Not a Date instead of 1/1/70.
668 Add Freeside-level transactions for RDBMS's which don't support
669 transcations? (Currently we assume a minimal RDBMS which has no rollback,
670 transactions or atomic updates). Or just require a RDBMS that supports
671 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
672 interface had this kludge on top of it but is a technical dead-end in most
673 other ways, unless it can gain an SQL parser and DBD interface.
675 if i'm really bored, find the /rdb interface in fsold and port it to NoSQL,
676 and while I'm add it add interfaces for AnyDBM_File tied hash.. hmm. Shouldn't
677 an FS::Record have something to do with a tied hash? But we don't want
678 performance to go gaga... maybe something with commit to help out here?
680 Ok: FS::Record gives you a tied hash, and you get methods for commit, etc.
682 Better automated comparison of our CC records with processors (CyberCash,
683 at least, has not always had 100% accuracy, though recent versions are
686 Expect or other pty based login check, where we actually connect to a
687 terminal server or shell machine and test logging in as the user (if we
688 are keeping a cleartext password for that user) (This is something tech
689 support often needs for new customers)
691 Use cust_main table for pre-sales tracking as well?
693 Automatic commision report and check generation via freq and prog (to
694 become a Safe perl expression) fields in agent table, and possibly others.
696 Database and add a mailed-out date and method for disk/CD mailing, so a
697 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
700 Inventory tracking for physical items such as routers (for sale or
701 lease... probably doesn't make a difference in the ordering... but if you
702 cancel a router lease the inventory should come back. hmm.)
704 -- Matt's wishlist ---
706 From matt@michweb.net Fri Feb 20 16:39:53 1998
707 Date: Thu, 19 Feb 1998 23:20:11 -0500
708 From: Matt Simerson <matt@michweb.net>
709 Reply-To: quadran-developer@netgoth.com
710 To: quadran-developer@netgoth.com
711 Subject: Re: Welcome to quadran-developer
713 >Whats it based on and what is it supposed to do? I'm interested, but
714 >unfortunatly, I don't have that much time to help on the project (I'm busily
715 >working on one of my own based around MySQL and Qt right now -- don't know
716 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
717 >it is designed around our system)...
719 That's what I set out to find, but didn't find anything on the web site.
720 I'm looking for something that will do the following:
722 Single point of entry for users on a secure system:
723 Creates account on user (public) systems
724 update /etc/passwd/master.passwd file
725 update radius database (if necessary)
726 Set up up disk quotas (although I hacked adduser to do this)
727 Option for adding user to a mailing list(s)
728 Export of new user info to customizable report (for automated entry
730 accounting software, etc...)
733 Export credit card info for batch processing and have hooks built
734 in for other forms of electronic processing.
735 Batch-Payment (apply payments from formatted text file).
736 Customizable reports for manual entry/importing into Accounting
738 Email or laser print invoices
739 Sanity checks credit card numbers before processing (code available)
741 Simple method for disabling an account.
742 Arbitrary Expiration Dates (on a given day, in x days)
744 Changing password to '*'
745 Virtual customers disabling dns, http server, log processing, etc..
747 Billing for different account types:
748 Dialup monthly flat rate. Prorates for partial months.
749 Dialup monthly flat rate for x hours + hourly usage.
752 Virtual Web accounts - w/multiple mailboxes
754 Disk space used over quota.
755 Tech support minimum + hourly charges
756 Other for misc stuff (modem, RAM, etc...)
758 Per user definable RADIUS attributes (ties in with above)
761 IP filters (for dialup email only)
763 Keep logs of modem usage generated daily from radius accounting logs stored
764 on multiple radius servers.
766 Keep logs of disk usage generated from quota.
768 Method of adding virtual domains to your system:
769 Automatically grabs an IP address from a preassigned pool.
770 Creates a domain.com database file from database fields
771 Updates /etc/named.conf or /etc/named.boot and reloads named.
772 Add's virtual.com to /etc/sendmail.cw or qmail control files.
773 Edits your web servers httpd.conf file and restarts http server.
774 An optional section for adding vif's can be added if the users OS
775 supports adding them on the fly. Otherwise it's up to the end
776 user. Make a hook that can run a custom script that the user
777 tweaks for his system.
778 Update or create the config file your web stats analyzer needs. I've
779 done this for analog (free) and http-analyze. Probably
780 should only officially support analog and let users hack
781 it to their hearts desire.
782 I've already written scripts that do most of the virtual web stuff on my
783 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
784 as long as all the info was stored in the database (username, domain name,
785 and ip pool) this could easily just be run as an external script that the
786 user tweaks to match his system.
788 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
789 Payroll, Tax stuff, and most everything else we could need. It's already
790 set up for the type of checks we have, etc, etc... I just need something to
791 do the billing part. I can import/export sales and payments directly once
792 the billing part is done. You can't write accounting software as good as