I solved my case by doing following steps:Ģ) Do Select Action: SQL Statements to select employees that emails should be sent to their supervisor.ģ) PeopleCode Action: Import Appication Packages: Especially thank Richard Linton and David for the solution and helpful tips, this is exactly what I looked for. What you want is pretty simple and easy to implement which means your users will continuously "refine" the message and drive you nuts. If it looked good, then turn off the flag and run it for real.Ī) sending one at a time ensures that if one fails then the remainder will still be sent.ī) if using a number of email addresses in any block (to, cc, bcc) if one is bad processing stops at the bad address and does not continue with any succeeding addressesĬ) there is a limit as to how many addresses can be included (character string limit set by your system) so don't attempt to have, say, 20 emails
This way, I can see who it would send emails to about whom without actually sending an email. How would I use a "Report Only" flag for this process? I would have it log a message to the process log rather send send an email. Personally, I like to have a few parameters including "Report Only" to make development and implementation much easier. Does the process keep sending daily messages about the absence? Testing and discussions will prove out what the process needs to do.Ĥ) Yes, this would require a run control record but considering that the input needed is minimal if any then an existing record could be easily used. On the 8th day the process should pick up the information and email it.
2do app forward emails code#
The fun part will be the code and the requirements. You do NOT want to hear from a Vice President complaining about a test message that was sent out.ģ) Your requirements can be easily handled by an application engine program run on a daily recurrence. You do not want to be sending emails to real people from development. I also preface the body of the message with text apologizing for the interruption and that this message came from a test system and can be ignored and deleted.Ģ) ALL email addresses (save for the developers and a few others) in development and test are set to a single email address. If NOT production then I add a CC of my email address as well as additional text to the message so I can confirm that what it generated is what I wanted it to generate. It checks to see if the %dbname is production or not. What I do is:ġ) The code is environment aware. What is more important is the mechanics of delivery. In the past, I have used Message Catalog entries as well as Generic Templates. How the message is created is irrelevant but that will be the majority of the time spent. Emoji UTF-8 characters cannot be used in task titles or notes as Toodledo does not support them. In fact, ToodleDo will replace Emoji characters with question marks, and all tasks that had an Emoji will be duplicated: one will have the Emoji, the other will not.I see this as not so much an issue of the coding to create and send an email (two options that I know exist, SendMail PeopleCode function and the various Application Packages that can send email).Alarms from 2Do will not sync to Toodledo.
Audio and picture attachments in 2Do will not sync to Toodledo or to other devices running 2Do.Only tags assigned to a task in 2Do will sync across to Toodledo.
2do app forward emails pro#
0 kommentar(er)
