Suitecrm Workflow - Email sending using varchar custom field option - suitecrm

I have a problem with the action of sending email to an email address entered in a varchar field. The option called ‘field’ in the action seems not to work. Can anyone help me understand what is entered as a parameter? I have already tried to insert several references to the field but without success.
Suitecrm workflow screen
Thank you

That option has an internal name of Record Field. I looked in the code and I don't think that option is implemented yet.
The Email addresses are stored in a specific module called Email Addresses. This module has different functionalities, such as the opt-in or rejected options. And it has a relationship by default with the modules Users, Contacts, Accounts, Leads.
I don't think SuiteCRM can send an email using the address from a text box.

Related

Remove "[External]" tags added by email server

My organization has begun adding obnoxious warnings to the subject and body of any email that arrives from an external address. My organization allows email forwarding, and I forward to gmail. I would like to have the extra text automatically removed before I see them in gmail. This would not violate the policies at my organization. Some ideas I had:
(1) One option would be to set up a gmail filter that edits the message. This feature does not seem to exist.
(2) Another option would be to customize the display so that this particular text is never shown on the screen. Again, there seems to be no way to do this.
(3) I wrote a script in Google Apps to grab to the content of each offending email and send an edited version to myself, but there is no way to make the "from" field show the original sender (perhaps with good reason). I can put that information in "reply to" but the gmail client doesn't show it nicely. This removes the annoying extra text at the cost of the ability to easily see who sent the email. The core of it is this call:
GmailApp.sendEmail("<my_email_address>",newSubject,newBody,{
attachments: message.getAttachments(),
bcc: message.getBcc(),
cc: message.getCc(),
htmlBody: newBody,
replyTo: message.getFrom(),
});
Any ideas? This is becoming a big problem as the "nanny state" approaches, so I'm sure others will appreciate your solution.
Issue
It unfortunately seems that at the day of this post, there is no way of edditing a forwarded email with the Gmail API. Check the documentation to see what you can actually do with the Gmail API in regards to forwarding email addresses.
Workaround
Despite it is not possible to edit a forwarding email address, in your case you are interested in:
Edit the body and subject of the email address.
Preserve the information of who the sender was.
Therefore what you could do is:
Get the email address you want to edit. Get the body, subject and information about who was sending it and store that.
Create a new message where you edit the message you just got and write on the subject the from field that was in the message you just got.
Send that created message to your desired recipient just like it was a forwarding email.
I hope this has helped you. Let me know if you need anything else or if you did not understood something. :)
Apps Script
You can insert messages into your inbox with their original "From" field but a modified body.
Note: Inserting is different from sending because the message is created on the inbox with less validation than sending.
To use this on Apps Script, take a look at the Advanced Gmail Service.
Custom Application
Another idea on how to do this is to use a custom application (in any language you'd prefer) that:
scans your company inbox with IMAP
manipulates the message body to remove the artifacts you don't want
insert manipulated message into your Gmail inbox with the Gmail API

DJANGO AllAuth Required Fields in User Model

I was using djoser, but ran into snags customizing emails and was referred to allauth + rest-auth.
I'm trying to convert my endpoints and running into problems with models.
Firstly, my user model with djoser dropped the username in favor of email, and I moved first & last name to a one-to-one profile table and added zipcode to the user model -- effectively my users are emails with passwords and zipcodes.
allauth threw an error that username didn't exist, after searching around I found a hacky 'solution' in adding an empty username filed back into my user model (and just ignoring it). When I changed my login endpoint from /auth/token/login/ to /rest-auth/login/ I got another error django.core.exceptions.ImproperlyConfigured: Field name 'first_name' is not valid for model 'User'. I'd really like to avoid adding all of the profile fields into my user model and making them nullable -- and I don't really want to write my own authentication backend.
Does anyone have experience with this type of model overriding?
Cheers,
-E
Unless you are planning on completely avoiding Django's user infrastructure, I would not bother trying to remove the default fields.
Whenever you're customizing the django user you'll want to extend AbstractBaseUser which includes first_name, last_name, username, email, date_joined, is_staff, and is_active. You don't have to use them but they will be there. You can specify which field will be used for the username
Once you're using AbstractBaseUser as the base for your user class, your problems here will go away and you can specify what you need from allauth from their configuration docs.
Also see the allauth doc on custom user models

DocuSign for Salesforce - relating to closed opportunity or quote record

We have a situation where some of our DocuSign documents do not get signed within the DocuSign system. We have someone that manages these "paper signatures" and then uploads them to DocuSign which connects to Salesforce.
We need to relate these envelopes to either an Opportunity or a Quote to get them to populate fields on these records.
When creatng the envelope, we have the option to "Relate to Salesforce" objects: Leads, Contracts, Opportunities, etc. We tried to use Opportunities and then use the Search to find the Opportunity to attach it to. However, if the Opportunity is in a Closed status (which it is 99% of the time), it will not show up in the search to select.
We could also attach to a Quote, however, there is no option on Salesforce Connect to relate to this object.
Does anyone know a workaround for this that will still allow our person to upload through DS and connect to the appropriate record?
Thanks,
Shannon
It will not unfortunately work with closed ops or quotes.
The only way I can think to do it would be to add a non-required envelope custom field in your account called ##SFOpportunity and when uploading that wet signed doc into DocuSign add the objectID as that envelope custom field (it's how the manage package relates back to proper objects when sending from SFDC).
It's a bit of manual process, but it should work.

how to find out wrong email id in mail using java

We will be sending automated emails through a mail box ,we will send an email with two to three emails in TO column and one or more emails in the CC column ,if i have a wrong email in the TO column in that mail box we will get a delivery report that email is wrong i need to write a program such that it will pick up the wrong email id
Start by reading up on JavaMail FAQ and the com.sun.mail.dsn package. The JavaMail Homepage has all of the downloads you'll need.
You could also enable the mail.smtp.reportsuccess property per the documentation:
When sending a message, detailed information on each address that fails is available in an SMTPAddressFailedException chained off the top level SendFailedException that is thrown. In addition, if the mail.smtp.reportsuccess property is set, an SMTPAddressSucceededException will be included in the list for each address that is successful. Note that this will cause a top level SendFailedException to be thrown even though the send was successful.

Can I use Contact Form DB plugin in my wordpress site for saving and displaying data without sending emails

I want to create a wordpress custom plugin for saving three fields of data and also an image of the same from wp-admin area for every item. It should be able to display all these items in a page.
When I searched for a plugin I found Contact Form DB plugin which can be used as contact form 7 plugin extension for saving data send through it..
http://wordpress.org/extend/plugins/contact-form-7-to-database-extension/
Can I use Contact Form DB plugin in my wordpress site for saving and displaying data without sending emails? It also sends email but I only want to store and display data.
Another problem:- I'm already using a contact form from contact form 7 plugin for sending email enquiries.. Will the changes for saving data in contact form 7 affect its working?
Please help me with any reference or solution as I'm new to wordpress and currently don't know about plugin development.
Any help will be greatly appreciated..
Thanks in advance.
You can use wpcf7_before_send_mail action hook to prevent form being sent to email..
(I have tested this with "Contact Form DB" plugin - it saves data before email is filtered)
To filter only specific Form IDs - use something like this:
function wpcf7_skip_email_sending($wpcf7_data)
{
if ( in_array($wpcf7_data->id(), array(2,3,7)) ) {
$wpcf7_data->skip_mail = true;
}
}
add_action("wpcf7_before_send_mail", "wpcf7_skip_email_sending");
(For older CF7 version you might have to change $wpcf7_data->id() to $wpcf7_data->id)
If you setup the Contact form 7 and put in a junk or noreply email address to send the message to on Contact form 7 it will still log the message being sent in the contact form DB
So in the shortcode template send message to junk#yourdomain.com and whenever a user submits it will try to send to that email and will still log the email as being sent. Personally I would actually create that email address so that your smtp doesn't get flooded with bounce back from smtp server.
To avoid sending emails, without even touching the files, the fastest way is to add in the additional settings tab
demo_mode: on
or
skip_mail: on
With Contact Form DB both works fine. The difference is that demo_mode won't work with Flamingo.

Resources