Hi,

I found this :

http://danielrivers.com/visibly/

i have tested it on DetailView :

call it : 

jQuery('[visibly]').Visibly();

under function dtlViewAjaxSave
and on document load 

quite interesting 

Well, since it hasn't been done yet I'll start this:

I've been thinking about the need for product hierarchy as discussed. Since I've worked and maintained a coreBOS system at a manufacturing company I've got some background. I don't think there is the need for a real 'hierarchy'. In stead, I think we should start by looking at products in a more sub-divided way:

A product could roughly be three things (in a manufacturing context):

• An end-product that you buy and sell as-is. Which is like it is now.
  
• An assembly. Which basically means this is the product you sell, but it doesn't enter your company in the form it exits. In stead, you buy or manufacture the parts and assemble the product. Which leads to the third type:
  
• A part. These products you buy from a supplier and use to create your end product (the assembly as mentioned above).
  

• When you sell an assembly, you should immediately see if you have all the required parts. If not, you should be able to create purchase orders for these parts (and preferably send an e-mail to the supplier).
  
• You could easily produce lists for factory workers (the assemblers) that list which parts they need (and for instance where in the warehouse these are located).
  

We offer a update service from ** any ** version of vtiger to the latest version of coreBOS.

Here you have more information about this Update Service for coreBOS CRM

For more information -> send us an email

I've started work on a new theme. Now I'd also like to incorporate some autocomplete functionality. Now I'd like some advice on how to do this as best as we can so that this can be integrated into the app. At first I tried just copying the standard 'softed' theme and modifting CSS. This works fine, but ir won't allow you to set new scripts in the head. So now I'm thinking about creating the theme as a module, which will allow me to register new head links. The third option is, I create commits on my github fork that can be implemented in the app no matter which theme is chosen, so that the functionality will always be available. The question is, which do you prefer?

Disponemos de un servicio de actualización desde **cualquier** versión de vtiger a la última versión de coreBOS.

Aquí tienes más información SERVICIO DE ACTUALIZACIÓN a coreBOS CRM

Para más información -> lorenzo@tsolucio.com

I'm working on the last touches of my module that connects coreBOS to Exact Online. In this process, I realized something. Any Exact sales person that comes into contact with someone using coreBOS will try to talk that person into moving their entire CRM system to Exact, since they also offer that. This brings us into a situation (or at least it has brought me into that situation) where offering the connection could in the end loose a customer. CoreBOS of course has many advantages over Exact, but there is one in which it lacks: official Accounting possibilities.

I've taken it upon myself therefor to investigate the possibilities of creating a set of modules (a suite) that fixes this, so that coreBOS can also offer real Accounting features. My investigation will split into two parts, for which I'm looking for input here:

1. The technical part. Of course I am an expert developer now , but I could still use a lot of help. I read somewhere in some documentation (I don't remember where) that it was possible to install a 'chain' of modules. Kind of like making the modules dependant of each other. Is this real, or just a distorted recollection? Also, any advice on implementation of what I'm describing below on the accounting side would be welcome.
   
2. The Accounting part. I've been going through my Exact Online test account to see what they offer, and how they approach the accounting part. I will post my findings hereunder, as a 'part 1' list, meant to be expanded by you: reader! Anyone with experience in the field of accounting, please respond, because I am not experienced or educated in this field so I'd like to setup a basic system to work from.
   

• A 'General Ledgers' module. This is a 'homo economicus' term for 'category', simple as that. Let's say you run a supermarket. Your General Ledgers could be:
  • Meat
    
  • Vegetables
    
  • Bread
    
  • Etc...
    
• The General Ledgers can be on three sides of your balance sheet, costs, revenue or stock. They can only be on one at the same time so this can be a simple dropdown.
  
• Within products, you'd have to create a new block for the general ledgers. For each product, you'd have three fields. There you can choose, for that product which Ledger you book the costs on, on which Ledger you book the Profits and on Which ledger you book the stock. Let's say my supermarket will now buy ten tomatoes. The purchase value of these tomatoes will now be booked on the Ledger I indicated as the cost one, AND on the stock one (since I also add ten to my stock). Now, if I sell three tomatoes, these three will be deducted from the stock Ledger I chose for tomatoes, and the revenue for these tomatoes will be added to the revenue Ledger I selected for tomatoes.
  
• The purchase part takes me to the second part. We already have purchase orders, but this module doesn't cover the needs for accounting. We need to be able to also import other costs, like rent, or electrical bills. So there should also be a module for 'Purchase Invoices'. You should be able to select a general Ledger here also, so we know which ledger to book these costs on to. From a purchase order (the existing module) we should also be able to create a purchase invoice (the same way a sales order can create one or more sales invoices). After saving the purchase invoice (using the aftersave events?) we can automatically book the purchase value of the products to the correct Ledgers (that are of the 'cost' type).
  
• The above leads to adding a new field in products (in the 'price' block), called 'cost price'. When a purchase order is created or converted to a purchase invoice, the system should take the value of this cost price field in creating the inventory lines. You should also be able to change these (as you are able to change sales prices per salesorder also), when for instance you received a one-time discount.
  
• Journals. Journals are nothing else then a record of any financial transaction you made. I'm not wuite sure how to describe this, and don't have a firm grasp on what they should show. I'm thinking every invoice you make should show that some amount of money transferred from one Ledger to another. So booking your electrical bill could be a journal, adding the amount to the Ledger you created for 'housing costs'. I'm not sure, but I think you should be able to tell the system which 'booking period' this journal belongs to.
  
• I don't know squat about a profit/loss balance, but if someone could explain in in a 'accounting for dummies' way, that would be nice.
  

Hello

One of my customer face this issue:

https://discussions.vtiger.com/index.php...nt/1198220


FYI: After check coreBOS code it look like the above vtiger issue also relevance to coreBOS.

Regards
Addady

I would like to attach "productized" (and sometimes bundled) steps of financial advice/analysis to projects related to contacts.

Bundled products fit the bill already - but how to make products/services to appear under "More Information" in project tasks (and likewise in the parent project)?

Might be interesting for all kinds of Consultants, Advisors and Lawyers.

If a code snippet is readily available that would help most - but a pointer to applicable documentation is also very supportive ;-)

Best regards

PS: There are other extensions which I will post in Feature Requests - like: Adding up Units (here: billable hours) or cloning "Master Projects"

Just tried this, because using ENGINE=INNODB throws 'Can't create' error:

I've just tried out PDFMaker Free for vtiger 5.40 via "Install Custom Module".

But there is NO "Uninstall". Only a checkmark to disable it!

One way to get rid of it (if you don't like to use the module):

1. Rename/Delete ... corebos/modules/PDFMaker
2. Rename/Delete ... corebos/Smarty/templates/modules/PDFMaker

AND

3. Delete any instance of PDFMaker in 'vtiger_links' in your CoreBOS database.

Only then you get rid of the annoying message "PDFMaker is not installed" when you view or create eg. an invoice etc.

Best regards