all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
We have a number of requests to merge customer data. Basically, people end up creating duplicate records. They then want to clean things up. We may need a find and replace or some sort of merge function. This may end up needing some deep changes. Maybe use the find and replace parts section as a pattern. Customer data runs deep and touches multiple tables and sub tables. To help… start with these tables: - Additional customers - All inv - Corporations - Customer contacts - Customer history - Customer log - Customer photos - Customer queue - Customers - Elements of time - Invoices - PO invoice lines X (some number) - Quotes - Statements - Tie in flex grid - Etc. Also remember to change photo names and also check for generics with a main id and an app type id of 8. Check for the CMS media main, tie in flex grid, time sub assignments, and time sub pool assignments. -Along with merging customers and customer records. We have also had requests for merging vendors and payee records. Similar to customers… payees are used in tons of tables. They also have photos, media/content, flex grid, and time assignments. Remember tables that use main id and app type id 9 & 10. Number 9 = vendor/payee & 10 = employee. We may have to check both. A payee adjustment could run very deep. -With our community funded projects, how are we going to handle pledged or promised funds and monies? I think we could just add an internal payment and focus on operations. We could use a user-maintained balance sheet item to temporarily offset values as needed. Maybe I’ll do a pledged amount on GPS & GIS tracking for my dad and mom. I’ll go figure it out. -Idea from Steve… what if we used the existing page hooks right this second. Page hooks, meaning places that we could change the look and feel right now. We have plans to add 8-10 black boxes on every page. We already have 3 virtual black boxes on every page inside the secure side of the adilas application. Let’s use those to start with. This is 3 black boxes per page without any recoding of the site. -What if we used the session scope (after a valid login) and the chooser page to control corporation level settings as well as user level settings. We also have a personal settings page that could be used as needed. This could handle things like headers, footers, css stuff, skins, templates, custom pages, favorites, etc. Using the session scope, the custom header and footer black boxes, and custom settings could be awesome! -Small clean-up note… when editing customer log notes and elements of time (notes and sub comments) and their notes, maybe reconvert HTML break tags back into enter signs. That may help with editing for non HTML users. What this means is, we convert returns and enter signs (from a keyboard) into HTML break tags to help show what was entered. In order not to scare people, maybe un-convert or revert back to simple returns and enter sings for editing. That way the user doesn’t have to know any HTML or web code. |