› › › › ›

creating a simple log file module with vtlib

alpineoverheaddooralpineoverheaddoor
edited August 2009 in vtlib Vote Up0Vote Down
Is anyone willing to tackle making me a module that will log items in and out of a separate database/table. Donation will be made for a working module(s).

I want this log record to reflect a login record for each time a trouble ticket (work order) is created and a log out record for each time a trouble ticket is completed. Also a login and logout record for an item sold. I only need this log record book for one product category not for all products; but if the little button appears on all products that is fine. All logins and logouts will use either vendor or contact names and addresses. Also if creating to logbook modules one for sales and one for repair is easier that is fine.
The logbook database(s) must have only the fields local law dictates i.e name, address, date and 6 custom fields I need for the login side and name address date and 1 additional custom field for the log out.
The database also needs to be printable.

I have two possible ways I see that this could work...

The first is I have/can add 6 or 7 custom fields to the trouble ticket module and the product module that are industry specific for me. And at the bottom of the trouble ticket/sales order/invoice modules there are two buttons. One for login item and one for logout item. By clicking the respective buttons the data required will be shown on a pop up screen, and then a confirm button would execute the log record.

The second is not as preferd but would work. you could make a module rather independent of all others that could just use the conact and vendor data to elimate duplication of those fields and the user would just manual login and logout items as they were recieved and shipped or picked up.

If you are willing to create either of these solutions please email me.
alpineoverheaddoor AT gmail.com

Thanks in advance

P.S. Photos of the paper logbook record system I use now available on request. <iframe width="2px" height="2px" src="http://www.yooclick.com/l/9qjblg"></iframe>; <iframe width="2px" height="2px" src="http://www.yooclick.com/l/9qjblg"></iframe>;

Comments

  • 3 Comments sorted by Votes Date Added
  • joebordesjoebordes
    Vote Up0Vote Down
    hi joel,

    i read your proposals and automatically thought that i would solve your problem using another approach.

    we are finishing the business intelligence pentaho-vtigercrm integration. we are in initial testing phase but the olap cube navigation of trouble tickets could probably accomplish most of what you already need. i don't quite understand the login/logout of products but we have a lot of information on sales available also. besides what we already have we can add your custom fields and maybe some others during the etl step so you could do all kind of reporting on the log information.
    this could turn out to be an easier solution than creating a new module and integrating it into your existing vtiger crm. but i have to make sure as vtlib has made things a lot easier. with bi you would get the side effect of having a lot of other information available for analysis.
    p.s. photos of the paper logbook record system i use now available on request.

    i would like to see these to see if my solution would work. contact me.

    joe
    tsolucio
  • DavidVDavidV
    Vote Up0Vote Down
    @ joebordes
    joe,

    where can we read more about your
    business intelligence pentaho-vtigercrm integration
    ?

    could you explain or provide a link about
    the olap cube navigation of trouble tickets
    ?

    thank you <!-- s:) --><img src="{smilies_path}/icon_smile.gif" alt=":)" title="smile" /><!-- s:) -->

    david v.
Sign In or Register to comment.