易客CRM官方博客

由于不自觉的朋友在Trac系统里添加了很多与C3CRM开发无关的内容，从今天开始不再允许匿名new ticket，希望那些不自觉的朋友请自重，尤其是我打过电话的那个北京女士，请不要再发不相关的垃圾广告。

需要trac的帐号请发mail申请，符合条件才可以拥有trac帐号。

您可以在这里(http://www.sugarforge.org/frs/download.php/1571/Implemention3.pdf)下载如何快速实施C3CRM3.0(3)文档。

经过一段时间筛选，终于确定通畅的短信通道，该短信通道支持支持移动、联通和小灵通手机，短信到达率达99％。
短信通道与C3CRM无缝集成，不仅可以发送内部通知短信和会议与电话邀请，还可以通过营销活动模块进行手机短信营销，迅速提高公司的销售业绩。

短信费用如下：
短信通道占用费 2000元
1200元 10000条
2200元 20000条
3000元 30000条

为了庆祝开通短信通道，购买短信服务的前10名用户获赠2000条短信。
联系电话：13701696656 Email:dfar2008@gmail.com

注：1）短信没有时间限制

更新：可以接收客户发回的短信

windows平台自动安装程序提供下载，此安装程序主要是由董骞同学制作，我辅助修改而成，在此感谢董骞同学。
下载地址：http://www.sugarforge.org/frs/download.php/1536/Setup.zip

这个安装包适合不懂技术或对PHP、Mysql陌生的朋友，下载解压缩后点击Exe文件，连续几个下一步即可完成C3CRM3.0的安装，安装后会自动安装Easyphp1.8和C3CRM3.0。安装完成后，打开IE或其它网页浏览器，在地址栏输入http://localhost即可访问C3CRM，如果需要允许局域网的其它朋友访问，请修改c:/c3crm/conf_files目录下的httpd.conf，在Listen 172.0.0.1:80的下一行添加Listen yourip:80即可。

希望得到大家的反馈和建议！

C3CRM项目组 2006.7.7
http://www.c3crm.com

升级2.0.x的朋友请执行下面的步骤，昨天忘记写这个步骤了，谢谢支持。

5）以admin登陆3.0系统，进入系统管理->升级->修复数据库->点击执行按钮，修复数据库。

由于C3CRM3.0和C3CRM2.0.x差别比较大，所以升级比较麻烦，正式版发布2天后才发布升级版，如果给您带来不便，敬请谅解。
3.0beta版升级比较简单，使用正式版的文件覆盖beta版的文件，注意别覆盖config.php，然后以admin登入系统，进入系统管理->升级->修复数据库->执行升级即可完成从Beta版到正式版的升级。

C3CRM2.0.x升级步骤如下：
1）解压缩升级包，升级包可以在这里下载(http://www.sugarforge.org/frs/download.php/1525/upgrade_Patch.zip)
2）拷贝backupdb.php到C3CRM2.0.x的根目录下，然后通过url访问backupdb.php,例如http://localhost/c3crm2.0.3/backupdb.php，备份C3CRM2.0.x的数据库；
3）以admin登陆到已安装好的C3CRM3.0系统，进入系统管理，通过恢复数据库把第2步备份的数据库导入C3CRM3.0中，操作成功后进入第4步；
4）拷贝upgrade_from2to3.php到C3CRM3.0的根目录下，然后通过url访问upgrade_from2to3.php,例如http://localhost/c3crm2.0.3/upgrade_from2to3.php，升级数据库；

5）以admin登陆3.0系统，进入系统管理->升级->修复数据库->点击执行按钮，修复数据库；(此步骤昨天忘记写了，请升级的朋友执行这个操作，谢谢支持)

6）升级完毕。3.0与2.0的地址输入方式不一样，所以升级时把2.0.3中的所有地址信息(国家、省份、城市和地址)都赋给新系统中的地址字段了，因此在新系统中要根据地址信息重新选择一下省份和城市。需要输入地址的模块有潜在客户、联系人、客户、报价、目标及用户。

祝大家升级成功！
希望得到大家的反馈和支持，我们一起努力把C3CRM做好做强！

C3CRM开源社区 2006.7.5

您可以在这里(http://www.sugarforge.org/frs/?group_id=91)下载C3CRM3.0安装手册、C3CRM3.0权限规则、如何快速实施C3CRM3.0(1)和如何快速实施C3CRM3.0(2)等文档。

如何实施C3CRM3.0(3)编写中。。。

C3CRM开源社区隆重发布C3CRM3.0正式版，您可以在这里(http://www.sugarforge.org/frs/?group_id=91)下载C3CRM3.0正式版和C3CRM完全安装手册，可以在这里(http://www.c3crm.com/c3crmdev)进行在线试用(will/will)，还可以到论坛(http://www.c3crm.com/forum/index.php)中发表您的意见和建议。

此版本是根据C3CRM的用户和C3CRM产品顾问小组(由C3CRM用户组成)提出的需求开发的，充分考虑了国内中小企业的实际情况和使用习惯，不仅在功能上，而且在界面上和性能上都做了很大的改善，满足了国内中小企业的实际需求，真正解决中小企业遇到的问题。

此版本与C3CRM2.0相比，增加的功能如下：

1）考虑国内用户的需求，增加报表、合同管理、手机短信、公司通知、常见问题、部门管理、应用程序、解决方案、客户回访、产品服务等模块。

2）增强每个模块的查找功能，用户可以保存查找条件，同时安装时预设了用户常用的查找条件；

3）增加类似Gmail和del.icio.us的tag功能，用户可以为查到的纪录添加标签，方便用户对自己的客户、联系人等纪录进行分类；

4）增加OA主题，此主题参考国内用户习惯的界面风格，可以很方便对菜单进行分组，使不同的角色看到不同的应用程序和菜单；

5）增强系统的权限功能，负责人可以是某个用户、某个角色或者某个部门，如果负责人是某个用户，该用户可以共享所负责的记录；

6）增强地址的输入功能，可以通过下拉框选择国家、省份和城市；

7）增强详细信息页面的关联模块功能，查看每个模块的详细信息页面时无须加载所有相关的纪录，只加载所选择的相关纪录，提高系统的执行速度；

8）联系人姓名有中文名和英文名，不再分别输入姓和名；

9）用户在保存记录时会自动发送邮件给相应的负责人；

10）增加备份数据库和恢复数据库功能。

11）此外还特别优化了系统的性能，大大提高了系统的执行效率。

其它增强的特性在此就不再一一列出。

在此感谢C3CRM产品顾问小组和论坛上支持C3CRM社区的朋友，希望我们继续努力，再接再励，尽力把C3CRM做好做强，为国内的开源事业和企业信息化共尽绵薄之力。

注：您可以在这里(http://www.sugarforge.org/frs/?group_id=91)下载C3CRM3.0权限规则、如何快速实施C3CRM3.0(1)和如何快速实施C3CRM3.0(2)文档。

C3CRM项目组 2006年7月2号
http://www.c3crm.com

The second article in this series describes the inclusion of your custom backend systems right into the webbased Sugar user interface. We created ZuckerDocs following those steps (well, those maybe were the first 1 percent of the whole project …), and it worked pretty good in the end – but there are some obstacles to consider.

Starting a new module from scratch

There are some steps to take to make a new module appear in your Sugar user interface.

1. create a folder called “TestModule” in the “modules/”-folder of your Sugar installation
2. create some empty files in there: “index.php”, “Forms.php” and “Menu.php”
3. create a folder called “language” in there, containing an empty file “en_us.lang.php” (or whatever language you are using)
4. open the file “include/modules.php” with your text editor and add the line
   $moduleList[] = ‘TestModule’;
5. open the file “include/language/en_us.lang.php” (or your own language) and add the line
    ‘TestModule’ => ‘TestModule’,
   to the “moduleList”-array
   Note: If you have ever used the “Rename Tabs” function, you have to use this function again here instead of manually edit this file – just add “TestModule” to the tabs list.
6. Now login to Sugar as “admin” user, go to the “Admin”-panel, click on “Configure Tabs” and add the “TestModule” to the “Display Tabs” list
7. Go to the “My Account” panel, click on “Edit” and add the “TestModule” to the “Display Tabs” list
   Note: this step sometimes is required, sometimes not – don’t know the difference
8. The module now is visible in the module list.

You may download a prepared module folder here: TestModule.zip

Extending the skeleton

You can now try to fill in your custom behaviour into this skeleton. One of the most important points is, that it is not possible with Sugar to call your PHP files directly, but all of them are called by the front controller “index.php” right in your Sugar folder. Direct access to your custom module is not allowed for calling your PHP scripts (just for resources as images or javascript). To call your script “myaction.php” in the TestModule, you have to use the link “index.php?module=TestModule&action=myaction” – rather easy, but you should know in advance. The default action called when clicking on your module in the module bar on the top always is called “index” – that is, the file “index.php” in your module folder is called first.

The file “Menu.php” contains the hyperlinks which are shown in the menu bar on the left (depending on the theme you are using, it may also be located on the top or on the right). You just have to add one line to the “module_menu”- array to have an additional entry point available.

The file “Forms.php” can optionally contain some extra forms and javascript code. For example, the function “get_validate_record_js” should return javascript code for validating your form entries. If it contains the function “get_new_record_form”, the returned HTML code is used for displaying those nice “quick create” forms just below the menubar (look at the “Contacts” or “Accounts” module for an example). Have a look at the TestModule (TestModule.zip) – it just shows a company logo, but you can easily replace it with a small HTML form.

Useful Sugar APIs

In most cases, you don’t have to output your HTML code from PHP. Sugar includes a template engine which supports keyword replacements, listviews, variables and some more. It also provides database access to the Sugar database (hint: look at the global variable “$db”), and really a lot of helper functions for building up a visually integrated and appealing user interface for your modules. I will try to describe the most important APIs in other blog entries, it is out-of-scope for now.

Using the Sugar Module Loader

The file edit steps you did above in the “start from scratch” section are usually done automatically by the “Sugar Module Loader” – your users typically don’t have to edit Sugar configuration files manually to use your custom module. In the next blog entry I will describe how to build a complete module installable with the Sugar Module Loader starting from the TestModule created before.

注：这篇文章是ftreml所写，另外感谢他把C3CRM开发的模块改成兼容SugarCRM的新版本和支持英文，并与非中文国家的用户分享，在此表示感谢。

This series discusses the various means of integrating 3rd-party software, open source or not, with the well-known “commercial open source” CRM-Software SugarCRM. The first part describes the most basic integration by simply sharing database access.

In a lot of projects, no tight integration of your software with SugarCRM is needed – you only want to access the data, most of the times readonly, but also have the possibility to make changes. No UI needed, or no UI which is integrated into SugarCRM. For those cases it might be a good solution to simply share database with Sugar. ODBC, OLEDB as well as JDBC and Perl::DB drivers are available for free to access the mysql database. SugarCRMs table structure is rather easy to understand: 

There are “data” tables, “link” tables and some helper and config tables. All of the “data” tables have a set of common fields:

• “id” – holds the unique id of the object
• “date_entered” – original creation data
• “created_by” – unique id of the user who created the object
• “date_modified” – data of last change
• “modified_user_id” – unique id of the user who made last change
• “assigned_user_id” – unique id of the user the object is assigned
• “deleted” – if set to 1, the object won’t be displayed anymore

The data tables usually are called just the same as the module they belong to – “accounts”, “contacts”, “projects” and so on.

The “link” tables relate two or more objects and are used for building relationships – all the subpanels in Sugar, for example the contacts matching an account, are built upon those link tables. The tables are called as the objects they relate – for example “account_contacts”. They always contain the following fields:

• “id” – holds the unique id of the relationship
• “deleted” – if set to 1, the relationship is invalid

The “id”-field is never used explicitely in Sugar, as it makes no sense for itself – the interesting part in the link-tables are the additional fields, which link to the related objects. They are called like “object-name_id”, for example “account_id” and “contact_id” in the link table “account_contacts”.

This is an example query which lists all contact names with associated account name:

select c.first_name, c.last_name, a.name from contacts c, accounts_contacts ac, accounts a where c.deleted != 1 and ac.deleted != 1 and a.deleted != 1 and c.id = ac.contact_id and ac.account_id = a.id order by a.name, c.last_name

Using this query and an the MySQL ODBC driver (available here: http://dev.mysql.com/downloads/connector/odbc/) it is possible to do a mail merge with Microsoft Word, or even to perform calculations and build charts with Microsoft Excel. Some examples on how to do this are available in the ZuckerReports project at SugarForge: http://www.sugarforge.org/projects/zuckerreports/

注：这篇文章是ftreml所写，另外感谢他把C3CRM开发的模块改成兼容SugarCRM的新版本和支持英文，并与非中文国家的用户分享，在此表示感谢。