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