appian send email for user input task. How i resist submitted task appian email....
After task submit, this message come. I dont want below message in email . How I resist it .
Discussion posts and replies are publicly visible
Hi! This is actually a pretty simple issue that's occurring, and I am more than happy to help clarify.
So, when the task notification is sent out, the task is currently active and unassigned. This means that no one has yet completed and submitted the task.
The issue that you are having here is that you are opening the task from the notification email after someone has submitted it.
This means that you have one of two things going on:
1) You (or someone else) is completing the task before you can get in and open it from the notification. You can resolve this by checking who completed it last and asking them to not do so while you are testing, or by not submitting it yourself before opening the task from the email.
2) The process is designed in such a way that it ends before you could possibly open the notification email. As it seems that this notification comes from a User Input Task node, this is unlikely (but it is possible). You can fix this by redesigning the process so that does not happen, or by simply not sending out the notification.
Alternatively, and this very unlikely, but it could be possible that you are creating this notification manually and have incorrectly set the task link to a different task than the one you meant. This is only the case if you are certain that the task is still active (and has not yet been submitted), but you cannot open it from the task link in the email regardless.
Finally, I'm more than happy to keep helping you troubleshoot! First, just look into some of these items, and then feel free to get back to me with any complications!
Hi Nicole - just out of curiosity, can you clarify what you're hoping to help by downvoting other (correct) answers in this thread?
People aren't being too nice to someone who is clearly an Appian newcomer, but I reverted my votes in the interest of staying friendly with other answerers.
I agree that sometimes we can work on our evenness of tone around here - though I think some leeway must be given for frustrations over tangential factors like severely-repetitious questions, lack of detail or clarity, etc.
I myself try to avoid the "nuclear option" of downvoting another answer, unless it's clearly (and maybe even egregiously) wrong and/or off-base, which I've seen here and there, but not very often.
Well said - I'll make sure to be more careful in how I use it in the future, especially since downvoting a correct answer might mislead someone
Good to see that you have reverted your down votes on other threads too, I was so curious to know the reason why this guy is downvoting my and other fellow contributors every comment on any post.
If you didn't liked something and think is not up to mark then you can always tell directly by replying to that but downvoting other correct answers like that was just very unethical, we are a community here. But I think you got the whole point now.
Thanks Mike for pointing this out. Do you think a kind of checklist, similar to John Skeet's, but tailored to our needs, might help? We could make it a habit to share a link to it when appropriate.
codeblog.jonskeet.uk/.../