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