So then Get Email List should work, right? But it doesn’t have an ID property. But it does have “Include subfolders” which would be handy in some situations.
So our solution was to use Get Mail because we can designate the Mail Folder, and the Email ID. Oddly, this activity doesn’t have the “include subfolders” property:
But why? You can achieve the same thing by properly configuring Get Email as “top 1” and “order by newest first”…
So WHY do you have all these activities that are nearly the same? If you just added the “include subfolders” property to Get Mail, it could accomplish literally everything that Get Email By ID, Get Email List, and Get Newest Email do. Four different activities for no particular reason, when a single activity already (almost) does everything the others do.
You’re making more work for yourself having to maintain all these different activities. I bet there are other sets of activities with this kind of overlap.
–
The reason for multiple similar activities like Get Mail, Get Email By ID, Get Email List, and Get Newest Email is to provide flexibility and optimization based on specific use cases. While Get Mail with the “Include Subfolders” property could handle many scenarios, the other activities are specialized to provide more precise control over specific requirements (e.g., fetching emails by ID, retrieving a list of emails, or fetching the newest email). These variations help improve performance and simplify workflows for different needs. However, combining features could be beneficial, and it’s something to consider for future improvements.
That doesn’t make any sense, sorry. The other activities don’t provide more precise control. They have FEWER options, which means less precise control. It has absolutely zero impact on performance and doesn’t make workflows simpler by having redundant activities.
prashant1603765
ashokkarale
imad-pro
Matias_Clemente.Arg
Shah_Rukh