When reading an email, there is an Import to Sugar button available on top of the contents. I use izeno SMS module in sugarcrm.
can I import an SMS and relate it to a contact, account or ... in a systematic way or I should try ugly hard coding stuff?
Is Importing a systematic behavior of sugarcrm? i.e.
Is importing and relating email imitated anywhere in sugarcrm?
Importing data into SugarCRM is generally a system-wide ability. Accounts, Contacts, Cases, Calls, Meetings, Leads, etc. can be imported from CSV files. For example, any user with appropriate rights in the system should see the "Import Leads" link in the Leads action list.
See SugarCRM's documentation Introduction to Importing.
Not all data can be so easily imported. For example, Emails and Contracts cannot be imported via the interface without making code changes. As for iZeno SMS for SugarCRM, the documentation doesn't specifically state whether you can or cannot import SMS data, but being how similar SMS messages to multiple recipients would be to emails, I'd expect it to be difficult. I suggest you contact iZeno directly for support and information about their customization.
Related
I'm trying to find a way to export the emails of a current employee without them knowing. I'm currently a delegate on the account and am using GAM. Any ideas?
If you are superadmin then you should look into either Google Vault which is the immutable record of emails see doc or you should use Got Your Back here written by Jay0lee who wrote GAM. GYB exports to MBOX though so if you want to share the emails with someone who for whatever reason can't read MBOX then you will need an MBOX to PST converter of which there are many online. I have used the one from Systools effectively link. Or you can export by GYB and then import into a different gmail account which is quite useful for some types of investigation.
If you are merely a delegate then there is no easy way.
I'm writing a Google Forms app to collect application data to a spreadsheet, and to email a pdf with the information included.
The code I wrote already works, but I'm a little concerned that it might require some locking.
Do Google Form Apps need any sort of locking in the onFormSubmit(e) code for this?
Nobody will be editing the forms after they are submitted, and no usernames are tied to the forms.
yes you do need (script level) locking because a new onFormSubmit can get called while onFormSubmit is executing.
https://developers.google.com/apps-script/reference/lock/
I'm using SugarCRM Community Edition. I have a bunch of contact information. There are fields I have empty that would like filled. I want each user to be able to fill out a form and fill in those fields.
I'm not sure how to hook each contact into the database. I imagine creating a generic form that somehow hooks into the database using a key. The form/php is not the issue. What is the 'key' and where is the 'door'? I think the door is the SOAP API but I'm not sure. The key, maybe the tracker id?
The only thing I am familiar with as far as interaction between an email campaign and the contact is the campaign 'Tracker'. I know the tracker url with removeme is used for allowing the user to opt out of emails. Is there a way to use this tracker to allow the person to edit their information? I think the answer to this is easy but I need some guidance.
One way of doing this is using the built-in REST api. There are a couple of helpful tutorials out there, here is a link to the one I used for guidance in a similar situation.
You can have a form post the data to your sugar crm's REST gateway, accessible via the url http://localhost/sugar/v2/rest.php.
Although it is quite straightforward to implement, you may want to look at this wrapper class that can be used to maybe keep things cleaner than the hacked up script churned out on the spur of the moment I used in my project.
Last but not least, be sure to glance over the documentation, in the Web Services section you will find more information.
Good-luck
I would like to create a program that does the following:
1. Monitor all emails received at an address that I own, e.g. subscribe#mydomain.com
2. Read the From and Cc fields and insert those email addresses to my database
3. Parse the body of the email to find a certain text, such as a 6-digit registration code (assume I already have the logic to do the parsing)
4. Reply the emails from a template that includes the registration code and some other data retrieved from my database
To make my job easier, I would like to leverage any relevant services out there (maybe SendGrid, apinbox.com, etc.). Ideally all the servers are hosted somewhere in the cloud.
My question: Can you recommend the best way to do the above? You can consider me a total newbie in developing such programs, so please be gentle :-)
I don't know anything about the services you mention but It's fairly easy to write an app to do basic emailing in VB.Net. The built in SmtpClient class makes it easy to send emails, and there's plenty of projects on codeproject.com that shows how to read emails (just search there for POP3). The POP3 protocol isn't very difficult to implement, but it can be a little bit more difficult to handle MIME encoded content, but as I said, the projects at code project should show you that.
However, reading your question more carefully it sounds like you just want to have some automated way of sending out registration codes. If so, it might be worth to check if there isn't already services that'll do that for you. I'd suggest looking into that at some forum for Shareware Developers. One group I've heard of is the Association of Software Professionals, they might have some forum or advice about that.
If you are interested in a hosted service to handle the email parsing and conversion to HTTP POST I would recommend looking at a few like: http://mailhooks.com (free) http://mailnuggets.com (not free, but new and cheap). If you consider yourself a programming newbie, I would consider posting to a simple PHP script to test it out, like this:
<?php
// put the code below in a file at yourwebsite.com/test.php
// and POST your email to it as a test.
$postArr = print_r($_POST,1);
$log = "postLog.txt";
$fh = fopen($log, 'w') or die("can't open file");
fwrite($fh, $postArr);
fclose($fh);
?>
This will log the posted contents to a file called postLog.txt. Some of the mail processing services mentioned above may also have sample code to help out.
We have a number of customers that we have to send monthly invoices too. Right now, I'm managing a codebase that does SQL queries against our customer database and billing database and places that data into emails - and sends it.
I grow weary of maintaining this every time we want to include a new promotion or change our customer service phone numbers. So, I'm looking for a replacement to move more of this into the hands of those requesting the changes.
In my ideal world, I need :
A WYSIWYG (man, does anyone even say that anymore?) email editor that generates templates based upon the output from a Database Query.
The ability to drag and drop various fields from the database query into the email template.
Display of sample email results with the database query.
Web application, preferably not requiring IIS.
Involve as little code as possible for the end-user, but allow basic functionality (i.e. arrays/for loops)
Either comes with it's own email delivery engine, or writes output in a way that I can easily write a Python script to deliver the email.
Support for generic Database Connectors. (I need MSSQL and MySQL)
F/OSS
So ... can anyone suggest a project like this, or some tools that'd be useful for rolling my own?
(My current alternative idea is using something like ERB or Tenjin, having them write the code, but not having live-preview for the editor would suck...)
I think your looking for a reporting tool which is also capable of sending email. Sending a generared report in html or pdf shouldn't be to hard to do as well.
I've used JasperReports in the past for which I think it should fit your needs.
Another good solution is the pentaho reporting tool
You could easily write something on your own.. give them a basic edit control and allow them to use psuedo variables like {customername} {anothercustomerattribute} within the mail body.
On submit either send directly or save as template.
When the template is sent away the script automatically parses stuff like {customername} into the real customers name from the database.
Your own very very simple custom scriptlanguage :)
Everything else like loops and so on would be maintained on serverside. And if you want particular groups of customers to receive the letter, allow the enduser to select from selectboxes or whatever and do the rest on the serverside with pre-defined rules.