On 05/03/2012 09:36 AM, stavae wrote:
>
> Ok, I think I was able to get it.
>
> I used Photobucket :
>
> http://i1240.photobucket.com/albums/...screenshot.jpg
>
>

Greetings,
You have the correct "structure" for your workflow in that it is a 2
step workflow. We then go back to the responses from Wolfgang and
myself which comes down to the following main points:


Email notification occurs when the WF arrives at the particular
activity, and not after (which includes when a Approver takes action).
The email is used to Notify the Addressee that:

1) They have a Task to Approve/Deny
2) Remind them they have a Task to Approve/Deny
3) They have a Task that has been Escalated
4) Anything you want to outline (This is for the Email Activity)
5) That the Workflow Request has completed and it was either Approved or
Denied.

Another way to represent this:

a) Email for Approval Activity happens when the WF arrives at the
Approval Activity. Not once a person takes action.

b) Email for Reminder (at Approval Activity) happens once it has arrived
at the Approval Activity and the specified interval has been reached

c) Email for Escalation (at Approval Activity) happens once it has
arrived at the Approval Activity and the specified time for escalation
has been reached.

d) Email for Email Activity happens once the WF arrives at that Email
activity

e) Email for Finish Activity happens once the WF arrives at the Finish
activity.



Once the Workflow has been Approved at "First Approval" it will then
move down the "Approved" path to your "Second Approval". Once there (at
the Second Approval) the email will be sent (if enabled and user has an
email address) and the WF will appear in the Approval Person's Task list
in the User Application.



As Wolfgang outlined, you can use the SOAP or REST endpoints to
Approve/Deny instead of the User Application UI




--
Sincerely,
Steven Williams
Lead Software Engineer
NetIQ