Testes de integração SugarCRM 6.x com IPBrick 5.2

Conforme previmos há um ano atrás, a integração IPBrick mantém-se operacional nas novas versões de SugarCRM. A versão testada foi SugarCRM 6.0.3 com IPBrick 5.2 e, apesar de não ter sido emitido pacote "oficial" (pelo menos ainda), confirmamos que esta integração mantém-se totalmente operacional.

Neste teste de menos de uma hora bastou:

• Fazer download do SugarCRM 6.0.3


• Seguir o Wizard de instalação do SugarCRM


• Copiar o módulo de integração para a distribuição de SugarCRM


• Carregar o script de post install
  
• Executar Repair templates


• Aceder ao painel de administração e executar a sincronização
  

Em poucos minutos foi possível validar os três testes de QA (lembramos que existem 3 modos possíveis de tratamento da importação).

Não hesite em nos contactar se pretender ajuda no processo de actualização.

Quick update on KTEmailPush KnowledgeTree Plugin

Over the last weeks the KnowledgeTree Email Gateway Plugin received some attention:

• It's now fully configurable through the administration pages, without the need to edit at config.inc.php;


• It was also adapted to ease the process of customizing the logic behind destination folder determination — it's now possible to merge a bit of code that will determine where to put each incoming attachment, based on its parameters (subject, sender, etc.)


• Fully customized mail notifications using Smarty templates, which minimizes the risk of accidentally mixing up the code.

These are, of course, the most proeminent changes. These changes triggered, however, some feature requests to Knowledge Tree team. Their actually simple fixes which I don't know why never got in, since everything is in place already:

• KTS-4678 — To allow custom fields on configuration mechanism;


• KTS-4679 — To allow configuration settings registration without the need to run SQL;


• KTS-4680 — To allow custom templating to override the original KT's.

Here are some screenshots. Here is the new administration section...


... the new Task Fetch Mail in the the Task Scheduler (where you can enable/disable, control frequency, etc)....


... and the configuration options, as you used to have in the config.php file:


Do mail me if you want to see a demo.

KnowledgeTree Folder Special Plugin released

We are proud to announce the release fo the Folder Special Plugin v1.0. This plugins extends the Folder objects providing Description and descriptive Image support for each folder. It can also be a starting point for extending current Folder class implementation, thus allowing you to extend folders with any specific information.

This is a feature that not only answers to KTS-798 feature request but also allows folders to be extended on any number of fields and, better yet, there's no code patching. It's fully plug&play.

It will add special folder actions and permissions, so you can replace your "old" addFolder and rename_folder permissions for these new two to completely "hide" the old mechanism.

This plugins also supports an extra field (folder intro) to receive introductory texts for each folder, so when you're browsing that folder, you can see it before (or after) the folder/document listing — however, due to KT limitation, you'll have to apply a simple patch to the core templating engine.

Here is a screenshot (no folder intro):


(Folder images from Wikimedia commons; click image to view full size)
Also note the link to the KT Email Gateway Plugin in the 'pending' folder description.

Installation

• Get the release file from KT Forge FolderSpecialPlugin File Releases and unpack it inside the 'plugins' folder in your KT installation;


• Go to "administration » miscellaneous » plugins" and re-read plugins. Activate Folder Special Plugin;


• Go to a folder and edit permissions. Check the two new ones, save, and return to the folder view;


• You can now see there new actions for that folder: add special folder and change folder details.

The rest should be self-explanatory.

Roadmap

• I think the deployment on large systems might become complex because of existing permissions. It currently misses a way of mimic'ing all the current addFolder/rename_folder permissions to these new ones; since they are compatible, I think that's the way to go. The plugin is already prepared for it.