pmgr/models at 237b0a901f93f0bc64e76c506a6b469fca46a3e1 - pmgr

Fixed yet another bug in the merging of actions & options

2009-07-25 07:57:56 +00:00

account.php

Cleanup of old lingering functions and some comment blocks

2009-07-30 02:39:09 +00:00

contact_address.php

Finished implementation of contact edit. This is now saving everything to the database. I hope to now leverage it for a new contact. This checkin includes a bit of code in the sitelink2pmgr script that sets the customer display name. It should have been checked in several revisions ago.

2009-07-05 23:43:35 +00:00

contact_email.php

Moved the customer edit page to include address and email fields. This is largely all the work on the presentation side, now I just need to take the data and update the database.

2009-07-05 20:01:06 +00:00

contact_phone.php

Finished implementation of contact edit. This is now saving everything to the database. I hope to now leverage it for a new contact. This checkin includes a bit of code in the sitelink2pmgr script that sets the customer display name. It should have been checked in several revisions ago.

2009-07-05 23:43:35 +00:00

contact.php

Many, many changes, and yet still much to do. Many things are working, but certainly nothing beyond simply data retrieval (no editing or adding of any data). Also, some work is still required to ensure the grids have the right columns; we can strip out certain columns for some views (such as removing customer from the leases grid of the customer view... completely redundant). And of course, there are still many bugs and lots to clean up.

2009-07-23 01:49:46 +00:00

contacts_customer.php

Implemented edit functionality for customer. Like with contacts, the interface leaves much to be desired, since it's limited in functionality. Namely, you can add a contact, but you can't add contact methods (phone/mail/email). Also, it doesn't use jqGrid to present the selection choices, and so the user is stuck with the fields we've chosen to display, as well as the sort order we've chosen. Enhancement is possible someday, but for now, it gets the job done.

2009-07-06 02:06:23 +00:00

contacts_method.php

Finished implementation of contact edit. This is now saving everything to the database. I hope to now leverage it for a new contact. This checkin includes a bit of code in the sitelink2pmgr script that sets the customer display name. It should have been checked in several revisions ago.

2009-07-05 23:43:35 +00:00

customer.php

Changed prints to use the new logging system

2009-07-31 01:23:27 +00:00

double_entry.php

Changed the deposit to use a grouped double entry instead of individual ones for each tender deposited

2009-07-29 10:10:11 +00:00

lease_type.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

lease.php

Bug fixes to get lease security deposit and balance information working.

2009-07-28 01:18:02 +00:00

ledger_entry.php

Suppressed all the debug print statements from transaction insertion.

2009-07-28 02:40:42 +00:00

ledger.php

In the cleanup of r423, some code accidentally got squashed. This checkin undoes that problem

2009-07-30 06:09:05 +00:00

map.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

maps_unit.php

Added more models

2009-05-28 09:27:29 +00:00

site_area.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

site.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

statement_entry.php

Renamed prExit to prReturn, to be consitent with the return statement where it should be used. Also, modified the chargePaymentFields to be more explicit on the balance, in anticipation of the new type VOID

2009-07-31 01:31:45 +00:00

tender_type.php

Re-implemented the deposit functionality. This is mostly working, although I'd like to get customer added to the tenders table, and probably change to a single deposit ledger entry for each tender type. A single entry would require that all tender types have been recorded to the same account, something that isn't mandated at the present, but is likely to be true most of the time. Perhaps they could just be grouped by account id, which should work in all cases and yet align with tender type 99% of the time. I'll have to think about it.

2009-07-29 08:55:09 +00:00

tender.php

Added effective date to each NSF entry, and fixed the account bug with receipts/payments. There is still a bug/question on how to handle nsf credits. It would be nice to simply delete the credit, since the check bounced, but then the original transaction will not add up. Either we decide that it doesn't need to add up, figure out a different type for the credit, or add a void flag to each statement entry and just void out nsf items. Or instead of a void flag, have an nsf_statement_entry_id which will also tie the payment/credit to the nsf payment/credit.

2009-07-30 18:23:37 +00:00

transaction.php

Added effective date to each NSF entry, and fixed the account bug with receipts/payments. There is still a bug/question on how to handle nsf credits. It would be nice to simply delete the credit, since the check bounced, but then the original transaction will not add up. Either we decide that it doesn't need to add up, figure out a different type for the credit, or add a void flag to each statement entry and just void out nsf items. Or instead of a void flag, have an nsf_statement_entry_id which will also tie the payment/credit to the nsf payment/credit.

2009-07-30 18:23:37 +00:00

unit_size.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

unit_type.php

Significant changes to work with the new account/ledger structure. Removed much of the auto-generated model association code. Added helper functions into the models to perform model related work, such as model 'stats' (a bad name for a function to return a summary of pertinent financial information from a given model instance). There is a ton of cleanup to do, but first I want to get it all captured.

2009-06-10 02:41:23 +00:00

unit.php

Got rid of the temporary function to determine unit status enums, and switched over to actually querying the database. Eliminated a legend entry for DELETED since no one should ever see a unit like that given that it should be, well, deleted. Modified the legend algorithm slightly to fix the number of rows instead of columns, since the placement algorithm works through the rows before moving to the next column.

2009-07-04 04:42:11 +00:00