Is there a way to make an email address clickable that opens default email client. I am testing this on my local and it works fine. But when I promote code to server it does not work.
java.awt.Desktop.getDesktop().mail(new java.net.URI("mailTo:"+ user.Contact.EmailAddress1))
I'm assuming that java.getDesktop is not available on server side? Is there another way to do this in Guidewire?
If you have the email address in a TextInput control, just pick the formatType email from the control properties.
If the control would be in read-only state it will display appropriate link starting from mailto:
Related
If a type in a dialog box on a website, is the owner of the website able to access the text? Note I have not submitted the page or draft in any way.
Furthermore if the dialog box is a address bar and comes up with address suggestions and I pick one is the owner of the website able to access this information? Note I have also not submitted the page or draft here.
Many Thanks
If you mean by dialog box input fields inside an HTML page, then the frontend code can listen to changes on the input fields, while you are typing and send that information to the backend. Nothing stops the frontend code from doing that, so it is possible.
We have a voting button in an email which works in the Client, is it possible to include a button in the email that would work for iNotes users?
The button is used to confirm that the email has been read and certain conditions understood.
Yes. Basically, what you want is for the user to click on a link that will run an agent on the server which executes the commands you have in the button in the Notes client directly on the server.
We have an alert set-up for sharepoint list, but I want to add some custom text to the alert email. We do not have any access to SPD or sharepoint server and can make changes to sharepoint client only.
Can anyone please advice?
The code that sends out emails runs on the SharePoint server via the Timer Job. Since you have no access to do anything with the server you've got absolutely no chance of modifying the built in alert emails.
Could you do this with javascript?
You can't send emails with JavaScript directly. You can open up a draft email in a users default email client using a mailto link but this won't achieve what you want as a user will still have to edit it.
You could, I suppose, put some javascript onto an edit page using a content editor web part (which you can do without SPD) to on changes make an AJAX call to a separate web server to do the actual sending.
What would be the best way to construct a contact form in Drupal 6 for each node of a particular type? I have some CCK nodes of type "profile" which have email address as a field. I want to have a view for each node with a contact form that users can fill out and send with their own email address as a return address (so that further contact is being done offsite).
Basically I just want that initial email contact to be done through my site, and when the recipient replies it just goes to the address that the sender entered when they filled out the contact form.
You might be asking yourself why I don't use the personal contact form that comes baked into Drupal. The issue is that the way my institution deploys their Drupal instances to use the local Kerberos logins, the user accounts it creates in Drupal do not have email addresses. They just get a basic skeleton account with username. I don't really want to force users to go through another hoop of editing their user account info, because they most likely just won't do it.
There is nothing to do particularly with node itself, all you need for this - is form with fields (from, to, subject, message) and custom submit handler for this form.
you can implement all this in custom module using forms API to create form and write custom submit for it. And in this submit you need to send email via drupal_mail() - take a look at this, it is provides examples as well. That topic can help you with forms.
Then, if you need to place this form within a node, you can do the following:
via hook_nodeapi, on "view" operation, add form you've created before, you can check for particular node_type and use existing field values (you mentioned cck field with email) to pre-fill form. So that every time user views node, he sees this form.
as logical continue of your task, I suggest it makes sense to take a look at menu system and create local task (tab) for the node, where you'll display email form.
In general, that's all. There are of course other ways of implementing this, however I think this one is the easiest for understanding.
Regards, Slava
I have some problem with the latest Jira (4.3.4). In this version you can set a specific outgoing email address in every project. That's a great feature. But I want to go even further and give every component a specific outgoing email address to. Why? Because we have our Support in one project and every different support customer has their own component representing them.
Every support customer have their own email address ex, support-customer#*.*. It is to this address we want them to email. But the Jira system as it works right now emails from a no-reply address. And a project specific address wouldn't do it either. Thats because we have a mailerdaemon which task is to modify the subject to JEMH (Jira Extentable Mail Handler) valid subjects. That mailerdaemon checks the To: address to add the right component.This works great and every issue gets their specific component.
Wanted scenario.
customer emails to address support-customer#*.*. Mailerdaemon picks the mail up and formats the subject. JEMH read the formatted email and creates the issue. Jira emails the customer that the issue is created using From: support-customer#*.*.
Same as commented and so on.
A potential approach would be to create a specific listener which sends a mail to the component lead.
An approach is using the script runner
Check out the example script to construct the email
https://studio.plugins.atlassian.com/wiki/display/GRV/Post+Functions#PostFunctions-SendEmailWhenBlockerReported
Logic to retrieve the component lead is straightforward. Getting the email address from the component lead also.
The listener would only act on 'my-create-event'. the my-create-event is included in the workflow create transition ...
Francis