Question

0

DISC request workflow emails requester

Kjell Nygren posted 8 Years Ago

Maybe I am not understanding this correctly.

When I go to a person's profile, in this case my wife, and initiate the DISC request, the email gets sent to me and not my wife.

Am I missing something?

0
- Jim Michael replied 8 Years Ago
Yeah, that's not how it's supposed to work. It should (and does, here) send to the person who's record you initiate it from. Stupid question: your wife doesn't have your email on her record, does she?
Edit Answer

Yeah, that's not how it's supposed to work. It should (and does, here) send to the person who's record you initiate it from. Stupid question: your wife doesn't have your email on her record, does she?
Yeah, that's not how it's supposed to work. It should (and does, here) send to the person who's record you initiate it from. Stupid question: your wife doesn't have your email on her record, does she?
Yeah, that's not how it's supposed to work. It should (and does, here) send to the person who's record you initiate it from. Stupid question: your wife doesn't have your email on her record, does she?
Save Cancel
0
- Kjell Nygren replied 8 Years Ago
Haha. No, we have separate emails.

Actually, I tried it on a couple different people and wondered why they didn't reply that they got it.
Edit Answer

Haha. No, we have separate emails.  Actually, I tried it on a couple different people and wondered why they didn't reply that they got it.
Haha. No, we have separate emails.  Actually, I tried it on a couple different people and wondered why they didn't reply that they got it.
Haha. No, we have separate emails.  Actually, I tried it on a couple different people and wondered why they didn't reply that they got it.
Save Cancel
0
- Jim Michael replied 8 Years Ago
For future visitors... this was a result of the default workflow being modified in a way that assigned the Person attribute to the Current User instead of the (default) of Entity. This meant that when run from a person's profile page, that user was not being passed to the workflow, and instead the person RUNNING the workflow was used. Should not be an issue for anyone as long as you don't mess with the default DISC workflow ;-)
Edit Answer

For future visitors... this was a result of the default workflow being modified in a way that assigned the Person attribute to the Current User instead of the (default) of Entity. This meant that when run from a person's profile page, that user was not being passed to the workflow, and instead the person RUNNING the workflow was used. Should not be an issue for anyone as long as you don't mess with the default DISC workflow ;-)
For future visitors... this was a result of the default workflow being modified in a way that assigned the Person attribute to the Current User instead of the (default) of Entity. This meant that when run from a person's profile page, that user was not being passed to the workflow, and instead the person RUNNING the workflow was used. Should not be an issue for anyone as long as you don't mess with the default DISC workflow ;-)
For future visitors... this was a result of the default workflow being modified in a way that assigned the Person attribute to the Current User instead of the (default) of Entity. This meant that when run from a person's profile page, that user was not being passed to the workflow, and instead the person RUNNING the workflow was used. Should not be an issue for anyone as long as you don't mess with the default DISC workflow ;-)
Save Cancel