Hi Ikrima. Can you offer some advice on a workflow question I have been
considering. I'd like to be able to have a workflow wait for an event. So a
user gets created but it waits for the objectSid to come back into the
portal before sending the notification. It would seem to be simpler if all
done in the one WF so I can send the random password in the email, without
having to write it onto the user object. The alternative is to muck around
with sets like "Created and waiting confirmation" and "Created and
confirmed". So I guess the questions are:
- Is it ok to write an activity that does some kind of wait loop, or is it
a dumb idea? I realise that if the FIM service went down the activity would
be terminated.
- Clearly the Approval activity is doing asically what want. Is there any
way to tap into what it does?
TIA. And - are you still in Prague?
Carol
0 コメント:
コメントを投稿