So…what has happened on the SugarCRM side then?
In SugarCRM we have just started off by adding a simple module called AlfrescoDocs.
The issues we have discussed during the day has mainly been about how to store data in Sugar. Should there be any data in Sugar that is mapped to Alfresco or should SugarCRM only be a view of Alfresco’s documents?
What we are hoping for is to make it possible to do this as dynamic as possible and not store anything in SugarCRM. What we mean by that is that there will not be an alfrescodocs-table in the database referring to the documents in alfresco, instead all documents will be picked up in runtime. So when entering the Alfresco Docs ListView a call will be made to Alfresco through REST and the documents metadata will be added to the list in Sugar.
The only place where we really need tables is for the subpanels (relationship tables), so they will be created and contain an id of the document in Alfresco.
So this is the plan anyway. We know that it would be much easier to have a database table and store the Alfresco documents id’s and then add some logic hooks to retrieve all the information needed….but hey, why do it the easy way 
…if the time runs out or we find out that it is better to use a database table in Sugar then we will do that, but for now the plan is to not use a database table.
Today is a historic day for me since this is my first blog-post ever. I guess there will be some moore….
