1 $Id: TODO,v 1.19 1999-01-18 23:05:00 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 Lay out the forms a bit better.
11 view/cust_main.cgi should show country
13 add doc on mod_perl: upgrade to current CGI.pm
14 doc Apache::AuthDBI as well
16 FS::cust_pkg _require_'s FS::$svc, but this won't work with %FS::UID::callback
17 loading of configuration. (pry need same idea, but will run immediately if
18 context allows). Looks like error is masked by 'use FS::cust_svc' which in
19 turn 'use's FS::{svc_acct, svc_acct_sm, svc_domain}' which is now explicit
22 libwww regression test - since it will create sample data, can also use this
24 make fs-setup option to add sample data so you can click on "New Customer" right away? so people understand what this stuff is?
26 Allow a cancelled/suspended/active status from packages to bubble up to
27 the customer lists. Put active, then suspended, then cancelled accounts.
28 Similar ordering on the package listing inside a single customer.
30 Add the ability for services to filter information up to the package level
31 for invoices and web screens, so you can select a particlar package based
32 on username or domain name, etc.
34 You can't delete the stuff under administration yet. Add this,
35 _including_ making sure the thing you are deleting is not in use!
38 one-time/per-customer/? changes in rates and descriptions ('remembered
39 invoices'): implement by creating a new package on the fly... but it isn't
40 associated with any agent types so it won't show up for other customers to buy.
41 (but also... make sure they go away when the customer does! - need this? :
42 one-off package edits! : need a cust_pkgs or cust_part_pkgs or something table,
43 with custnum and partpkg (like type_pkgs)
45 update site_perl/table_template* (pry out of date)
47 -- before or after ---
49 svc_domain.pm mail sending uses Date::Format which doesn't seem to pick up
52 view/svc_domain.cgi needs to know the domain might be unaudited (cosmetic)
54 remove whois_hack set to 1 for svc_domain.pm? add all known registries and
56 .us domains and others!
57 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...
59 (test cust_main.pm with cybercash v2 and v3, especially with the callback
60 stuff AND with mod_perl w/cybercash v2 kludge in package main)
61 (callback stuff should be eliminated by now)
67 cust_bill.pm uses '==' comparison on dates because they're currently ints
69 config file for allowed card types
71 write instructions for adding new services w/svc_Common.pm. Get rid of all
72 places where svc_* tables are hardcoded (rename svc_acct_pop to part_pop so
75 test and document libapache-dbi-logger (woo!)
77 radius logfile parsing and perl expression check.
79 Fix in cust_bill BUGS:
80 There is an off-by-one error in print_text which causes a visual error (Page 1
81 of 2 printed on some single-page invoices).
83 fields should be a method against a FS::Record or derived object, as well as
84 being something you can call as FS::Record::fields('tablename'). Might
85 even be able to handle both in the same routine (that would be neato).
87 Immediate removal of incorrectly entered check payments (can't take too
88 long to do this, or accounting is fubared).
90 Add code to move from one service to another (POP to SLIP/PPP, etc.).
91 This _should_ be possible by working off the rules in part_svc rather than
92 hardcoding anything in. The rules in part_svc may need some elaboration,
95 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.)
97 (bring back from fsold, ) Generalize config-sending stuff and make more configurable.
98 Expand the HylaFAX interface (also possibly generalize for other fax
99 softwar ie .comfaxe); allow things like arbitrary faxes of sales
100 literature, specific troubleshooting documents and so on. Maybe even
101 allow users to do this (though that might not belong in Freeside).
103 misc/process/sendconfig.cgi
104 Configure fax recipients via a separate box rather than using the finger
105 name or first+last from cust_main.
107 move all phone number logic out of Freeside - let HylaFAX or whatever
110 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?!
112 should be able to link on some field in email alias (right now you can link
113 on username or domain with a fallback to svcnum)
115 generalize and make configurable new invoice printing scheme in FS::cust_main::collect (past due)
117 deleting an svc_domain should delete all associated svc_acct_sm records.
118 same with a svc_acct.
120 periodic password encrypter
122 Automated, configurable notification, suspension and cancellation of
127 Allow for a future setup date on accounts.
129 sub AUTOLOAD in FS::Record should warn? die? if used with a non-existant column
132 edit (not just import, export and allow default/fixed) arbitrary radius stuff
134 edit/svc_acct.cgi and edit/process/svc_acct.cgi should deal with arbitrary radius stuff
136 radius import should take DEFAULT entry and put it in /var/spool/freeside/conf/radius-default ; svc_acct.export should use it (and doc)
138 in UI, s/State/State\/Provence/go and s/County/County\/Locality/go
140 what else (besides l10n) for i18n? (money!)
142 audit htdocs/* for things that should be libraried and things that should be
143 new methods on the objects (need to do this before implementing a new UI)
144 all the big things are done
146 some places we die() where we should &FS::CGI::idiot (and perhaps vice-versa).
147 Decide based on whether or not the "error" should show up in logs.
149 all .cgi's should use standard header/footer and idiot() subroutines. maybe HTML:: perl modules
150 for HTML creation. Maybe Embperl or something along those lines. ?
152 When running bin/bill, Fix this (Annoying but harmless):
153 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 99, <ADDRESS> chunk 4.
154 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 102, <ADDRESS> chunk 4.
155 Use of uninitialized value at /usr/local/lib/site_perl/FS/cust_pkg.pm line 105, <ADDRESS> chunk 4.
157 all cgi (but internal to the isp) places where package names are listed should also have
158 comment (like agent_type)
160 clean up $recref and other silliness and use -> calls where possible, or
161 one other alternative. clean up everything else.
162 should FS::Record use Tie::Hash? That would be very clean, but where do we
163 store the other information? Maybe you could ask any FS::Record object for a
166 change all file access from regular open(FILE,) stuff to OO, because of
167 problems scoping and passing filehandles like that.
169 the web interface should create a new object and use it instead of a blank
170 form for new records. the create method of svc_ objects should set defaults
173 sub check in man FS::table_name should be rewriteen. Get rid of $recref
174 stuff. Make sure all fields that refer to other database are checked.
176 Integration with signup disks (are there any free ones? Netscape?).
178 One-button cancel (+refund) for lusers who can't get online.
180 Keep information on virtual web servers (hostname, IP, host machine,
181 directory, etc.) and export this information for importation into the ISPs
184 Remove requirement that the first mail alias be the catchall? Still make
185 sure only one catchall per domain is defined in any case, of course.
187 Ability to move cust_pkg records from one customer to another? (proably
188 will need to cancel the old and create a new like when we move services
191 Auto-increment expired cards one year, and try again?
193 More non-US stuff - zip codes, country codes, foreign currencies, etc.
195 cust_refund.{cgi.pm} need to do cards xaxtions. (now we only have cust_credit)
197 Nicer set of integrated reporting possibilities, like weekly sales totals
198 by customer, package, agent, referral, etc., aging reports sorted by lots
199 of different things, and so on.
201 Client/server setup for users to modify their own passwords, shells, etc,
202 via passwd or secure web interface (prelminary passwd/chfn/chsh
203 replacement done). Complicated by the fact that we don't want to allow
204 incoming connections to the machine running Freeside, so we probably need
205 to have a daemon on each external shell or web machine that is contacted
206 by the Freeside machine. Be very very careful for both traditional
207 security issues and DoS problems.
209 An extension of the above to allow users to modify selected parts of their
210 own information, order and cancel services. A web interface for new
213 Expand domain name stuff to house all domain information. Export
214 named.boot/named.conf (primary and secondary) and named.{domain} files.
215 Add more registries (not just InterNIC's com org net edu)
217 Nice postscript paper invoices, rather than current ASCII invoices.
219 think about race-condititions in FS::Record and derived ->check ->insert
220 and so on, uid and username checks in svc_acct, etc.
222 Move to rsync over ssh file exportation rather than scp.
224 check 'n fix the proactive password checker. (cracklib?)
226 refunds of "BILL" payments: generate pseudo-check.
228 write batch senders and batch parsers for the different credit card processors
230 More CC processors/methods.
232 you should be able to fiddle the setup date in cust_pkg. (at least initially)
234 delete options in administration section
236 write a generic batch senders and batch parsers.
238 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
239 type stuff from cerkit)
241 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)
243 you should be able to get column types as a method against an FS::Record object
244 as well as dbdef->table($table)->column($column)->type
246 move to perl module for fuzzy and soundex searching.
248 package view needs to list extraneous services; we need to prevent the
249 creation of them so this never happens (and mark it as such in the source)
250 (the creation problem should be fixed - though they will still happen if people
251 fsck around in the data manually, so list them anyway)
253 add attribute dictionary to fs-setup as a menu, plus analyze users file to
256 Check for and report on duplicate billing accounts (cust_main, though many
257 will have a need for these so probably don't disable them outright.)
259 create a ->warn as well as a ->check method for all FS::table classes?
262 something to automate making a release and updating the web demo
264 export a debian-style (also redhat and?) /etc/group file aswell!
266 svc_acct_sm.import qmail import should pull in recipientmap people too.
268 .pm's like svc_acct.pm which need to do time-consuming things like ssh remotely
269 should fork and do them in a child.
271 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.
273 get some of { city, county, state, zip } from the missing bits if
274 possible (where can i get the data to do this? usps.gov?)
276 additional interfaces (perltk? java?)
278 Put the GPL notice in all files.
280 integrate w/IDEA's signup server
282 $cust_bill->owed database field to be eliminated, replaced by a method call
283 that calculates on the fly. make sure to grep for ->(get|set)field('owed')
284 same for cust_credit->credited
286 Export quota information.
288 move all configuration to a central place. maybe in blob's in the
289 database. maybe even things like the code to execute when a username is
290 changed can be in there, so less of the distributed scripts change between
293 Implement setup and recurring fees as Safe perl expressions rather than
294 numbers, to allow for variable-rate services. Backwards compatibility is
295 obtained because { 43 } in perl is still 43. :) Define API to pass
296 starting and ending dates and any other necessary data to expression
297 (fees are currently evaluated as Safe expressions but more work needs to
298 be done to define an opmask for various needs, write examples
299 (usage-based billing, etc.) and so on).
301 Add the ability to modify the next billing date in cust_pkg, and take
302 appropriate action. This will allow the implementation of pro-rate/1st of
303 the month billing as well as the ability to manually fiddle with
304 anniversary dates in cust_pkg, so you can sync a customer's anniversary
305 date even if you're using anniversary billing (manually or automatically).
306 (now with above, we need to have a way to automatically pro-rate /^(\d+)$/
307 charges - anything more complicated should figure it out itself given
308 starting and ending dates [document that!])
310 Daily Radius log parsing into database; other logfile formats?
312 Callbacks to enforce hourly limits on accounts (suspend until the end of
313 the billing period?), for those who limit customers rather than tack on
316 Flag packages (part_pkg) as taxable or non/taxable as some ISPs (for
317 example) need to charge tax on equipment but not service (separate flags
318 for setup and recurring fee... or perhaps a setup_tax, setup_notax,
319 recur_tax and recur_notax fees, and possibly something more flexible if
322 Allow for a variable number of invoices for customers who need multiple
325 Add a mail alias service with table svc_acct (not domain mail aliasing
326 which is domain with svc_acct_sm)
328 (bring back from fsold) Change customer comment field from its current kludge to something more
331 Better work orders with more information. Should eventually open a ticket
332 when we have such a thing.
334 edit/process/svc_wo.cgi
335 Call tracking and trouble tickets.
337 More accoutability for complimentary accounts: approval, expiration, term
338 (no more than x months in advance) and notification.
339 Flag particular users (or all users, for that matter) as having their
340 passwords hidden and/or locked from users of Freeside (maybe need Freeside
341 security levels first?).
343 Better Freeside-level configurable access, for those ISP's who have
344 employees they can't trust. Right now you're "stuck" with setting up
345 .htaccess stuff yourself. This should really just be integrated.
347 configuration/setup should get web interface
349 /usr/local/etc/freeside should be configurable
351 (probably as part of some automated installation process?)
353 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 (1.2)
355 This requires some serious magic in FS::Record:
356 ok, if date_type in fs-setup is to be something besides int,
357 now we need to create wrappers
358 for them so they behave identically across RDBMS's, ie date pops out as as
359 UNIX timestamp (or an object of some sort? maybe even a blessed $obj which
360 is a string not a hashref for backwards compatibility?) and so on. (remember
361 to treat '0' as Not a Date instead of 1/1/70.
363 Add Freeside-level transactions for RDBMS's which don't support
364 transcations? (Currently we assume a minimal RDBMS which has no rollback,
365 transactions or atomic updates). Or just require a RDBMS that supports
366 rollback and/or atomic updates and get rid of the work-arounds? The /rdb
367 interface had this kludge on top of it but is a technical dead-end in most
368 other ways, unless it can gain an SQL parser and DBD interface.
370 Better automated comparison of our CC records with processors (CyberCash,
371 at least, has not always had 100% accuracy, though recent versions are
374 Expect or other pty based login check, where we actually connect to a
375 terminal server or shell machine and test logging in as the user (if we
376 are keeping a cleartext password for that user) (This is something tech
377 support often needs for new customers)
379 Use cust_main table for pre-sales tracking as well?
381 Automatic commision report and check generation via freq and prog (to
382 become a Safe perl expression) fields in agent table, and possibly others.
384 Database and add a mailed-out date and method for disk/CD mailing, so a
385 customer can call and you can say, "sent on xx/xx/xx via {US Mail, Fedex,
388 Inventory tracking for physical items such as routers (for sale or
389 lease... probably doesn't make a difference in the ordering... but if you
390 cancel a router lease the inventory should come back. hmm.)
392 -- Matt's wishlist ---
394 From matt@michweb.net Fri Feb 20 16:39:53 1998
395 Date: Thu, 19 Feb 1998 23:20:11 -0500
396 From: Matt Simerson <matt@michweb.net>
397 Reply-To: quadran-developer@netgoth.com
398 To: quadran-developer@netgoth.com
399 Subject: Re: Welcome to quadran-developer
401 >Whats it based on and what is it supposed to do? I'm interested, but
402 >unfortunatly, I don't have that much time to help on the project (I'm busily
403 >working on one of my own based around MySQL and Qt right now -- don't know
404 >if it will be GPL'ed or not yet -- we'll probably just use it in house since
405 >it is designed around our system)...
407 That's what I set out to find, but didn't find anything on the web site.
408 I'm looking for something that will do the following:
410 Single point of entry for users on a secure system:
411 Creates account on user (public) systems
412 update /etc/passwd/master.passwd file
413 update radius database (if necessary)
414 Set up up disk quotas (although I hacked adduser to do this)
415 Option for adding user to a mailing list(s)
416 Export of new user info to customizable report (for automated entry
418 accounting software, etc...)
421 Export credit card info for batch processing and have hooks built
422 in for other forms of electronic processing.
423 Batch-Payment (apply payments from formatted text file).
424 Customizable reports for manual entry/importing into Accounting
426 Email or laser print invoices
427 Sanity checks credit card numbers before processing (code available)
429 Simple method for disabling an account.
430 Arbitrary Expiration Dates (on a given day, in x days)
432 Changing password to '*'
433 Virtual customers disabling dns, http server, log processing, etc..
435 Billing for different account types:
436 Dialup monthly flat rate. Prorates for partial months.
437 Dialup monthly flat rate for x hours + hourly usage.
440 Virtual Web accounts - w/multiple mailboxes
442 Disk space used over quota.
443 Tech support minimum + hourly charges
444 Other for misc stuff (modem, RAM, etc...)
446 Per user definable RADIUS attributes (ties in with above)
449 IP filters (for dialup email only)
451 Keep logs of modem usage generated daily from radius accounting logs stored
452 on multiple radius servers.
454 Keep logs of disk usage generated from quota.
456 Method of adding virtual domains to your system:
457 Automatically grabs an IP address from a preassigned pool.
458 Creates a domain.com database file from database fields
459 Updates /etc/named.conf or /etc/named.boot and reloads named.
460 Add's virtual.com to /etc/sendmail.cw or qmail control files.
461 Edits your web servers httpd.conf file and restarts http server.
462 An optional section for adding vif's can be added if the users OS
463 supports adding them on the fly. Otherwise it's up to the end
464 user. Make a hook that can run a custom script that the user
465 tweaks for his system.
466 Update or create the config file your web stats analyzer needs. I've
467 done this for analog (free) and http-analyze. Probably
468 should only officially support analog and let users hack
469 it to their hearts desire.
470 I've already written scripts that do most of the virtual web stuff on my
471 system...in bash. Shouldn't be hard for a perlmeister to convert. In fact,
472 as long as all the info was stored in the database (username, domain name,
473 and ip pool) this could easily just be run as an external script that the
474 user tweaks to match his system.
476 We use a great accounting software (M.Y.O.B) that does all the AP, AR,
477 Payroll, Tax stuff, and most everything else we could need. It's already
478 set up for the type of checks we have, etc, etc... I just need something to
479 do the billing part. I can import/export sales and payments directly once
480 the billing part is done. You can't write accounting software as good as