Issues in accessing workflow tasks from email.

Hi,

I have used iw_solution_email.ipl script (Template based script ) for generating notifications.
The script makes use of the template files(like ccmail_htmlbody.tpl) to generate the mail body.The tpl includes a reference to another tpl(ccmail_button.tpl) which adds a Finish button.
This button has a href to iw-cc/transitiontask?taskid=TaskNo,so that it links to the workflow task (with specified id) in a new browser.

However the behaviour that I observed for author and approver tasks were different.
For example :
a)For Author task,on clicking the Finish button a login screen is presented with the id/role of the user who is owner of Author Task.(I complete the author task and logout from TeamSite ContentCenter Professional.)
b)Whereas for Approver task,on clicking the Finish button it does not prompt for a Login,but directly connects to the approver task,with Approve/Reject options.However the task could not be completed.(The options for Approve and Reject are disabled).

Ideally it should prompt a Login screen so that appropriate user gets logged in and is able to complete the Task.

Is there anything that I am missing or is it that workflow tasks cannot be accessed from email with Template based email script.

Any clue would be helpful,
Thanks in advance.
Santosh

Find more posts tagged with

Comments

Migrateduser

I'm a fan of iw_solution_email.ipl in theory but I've had to tweak it quite a bit to make it more flexible by allowing more options. So, I use it quite a bit.

Can you verify that before you click on the link provided in the email that you're logged out of TeamSite and do not have any active cookies to identify as being logged in? You're right in that it should prompt you to log in if you haven't logged in for a while. But if it's been an hour or two and you click on the email link, it will most likely remember you.

Dave

Adam Stoller

Hi,

I have used iw_solution_email.ipl script (Template based script ) for generating notifications.
The script makes use of the template files(like ccmail_htmlbody.tpl) to generate the mail body.The tpl includes a reference to another tpl(ccmail_button.tpl) which adds a Finish button.
This button has a href to iw-cc/transitiontask?taskid=TaskNo,so that it links to the workflow task (with specified id) in a new browser.

However the behaviour that I observed for author and approver tasks were different.
For example :
a)For Author task,on clicking the Finish button a login screen is presented with the id/role of the user who is owner of Author Task.(I complete the author task and logout from TeamSite ContentCenter Professional.)
b)Whereas for Approver task,on clicking the Finish button it does not prompt for a Login,but directly connects to the approver task,with Approve/Reject options.However the task could not be completed.(The options for Approve and Reject are disabled).

Ideally it should prompt a Login screen so that appropriate user gets logged in and is able to complete the Task.

Is there anything that I am missing or is it that workflow tasks cannot be accessed from email with Template based email script.

Any clue would be helpful,
Thanks in advance.
Santosh

On my previous project I [finally] used iw_solution_email.ipl - the behavior I found was that the first time you received the email (or after 24 hours since the last time) you were taken to a login screen - regardless of whether you already had a separate browser session open and authenticated -- my guess, the mail system's initiated browser has a separate authentication token.

Once you have an authenticated token for TeamSite from the mail system - it's good (by default) for 24 hours - or until you clear out the cookies for your TS server from your browser. After that, you will again receive a login screen before taking you to the task details window.

If you're attempting to "impersonate" multiple users to test out your workflow - but all the mail is sent to you - you will need to clear out the cookies as mentioned above, between emails so that you will get the login prompt first.