email concurrency

I am on TS 6.7.1 on linux. I have a requirement for concurrent task as follows
1. Get concurrent approvals from Group A
2. Send emails to Group B
3. Send Emails to Group C

from def on concurrency how would i make sure all these 3 concurrent job are done before transitioning to next job in my case is "Submit".

IS it possible to do a concurrency in a concurrency? can any one point me to a good snippet or an example which shows this implementation?

I would appreciate a post or snippet for the concurrency part.

Thank YOu

Find more posts tagged with

Comments

Adam Stoller

I am on TS 6.7.1 on linux. I have a requirement for concurrent task as follows
1. Get concurrent approvals from Group A
2. Send emails to Group B
3. Send Emails to Group C

from def on concurrency how would i make sure all these 3 concurrent job are done before transitioning to next job in my case is "Submit".

IS it possible to do a concurrency in a concurrency? can any one point me to a good snippet or an example which shows this implementation?

I would appreciate a post or snippet for the concurrency part.

Thank YOu

You mention your version and platform (thanks) but you don't mention whether you are trying to do this with a WFT or WFM (and in the case of WFT whether you're doing this with XML or TeamSite::WFconstructor) - all of which would help - but even so, your post is kind of confusing.

Are you saying that all members of group A would be reviewing something concurrently, and then all members of group B, and then all members of group C?

Or are you saying that you have three group-tasks (or review tasks) that you want to have concurrent (one each for groups A, B, and C) - and you want to make sure you don't go to the next task until all three reviews have approved the work?

This is semi-basic stuff - you should be able to find most of the information you need in the manuals and in the OOTB default and/or solutions workflows. Please spend a bit more time looking at those - and then if you still can't figure it out - provide a more detailed explanation of what you're trying to do, and what you've actually tried.

Bhargav Coca

I am sorry Adam for the above wage question. Somehow I did figure out how I can do a very succesful concurency task. With my limited knowledge I was been told that we can actually send out emails to a group as a single "External task" using the funtionality of how your email_map.cfg is defined. Is this ever documented?

For Example if my email_map.cfg looks like this...

[html]
########## Email_map.cfg#################

#####################################
[/html]

can we define our external task based on the group as owner? i.e.

[html]

owner="__TAG__('Managers');"
description="Success Email Task">

__INSERT__(get_cmd("iw_solution_email.ipl", "End"));

[/html]

I guess i am totally wrong, but is this something doable or should i be writing custom script for the same? Please advice

Thank You

Bhargav Coca

I understand it now, i was looking for some articles and found out that if we do something like this then it is fine

[html]

a) name should be set to groupID (solaris) or domainname\groupID (windows)
b) email should be set to a list of email id's separated by comma

For example:

[/html]

So i can do the same with my group and emails of all the persons in the group followed by a comma. that might work. But still i am skeptical about my external task, is that any good? i am assuming here my owner will be ""groupid"? please advice.

thanks

Adam Stoller

I understand it now, i was looking for some articles and found out that if we do something like this then it is fine

[html]

a) name should be set to groupID (solaris) or domainname\groupID (windows)
b) email should be set to a list of email id's separated by comma

For example:

[/html]

So i can do the same with my group and emails of all the persons in the group followed by a comma. that might work. But still i am skeptical about my external task, is that any good? i am assuming here my owner will be ""groupid"? please advice.

thanks

First - the problem with the above extract for email_map.cfg is that you need to make sure that "testgroup" is never the owner of a task (here it looks obvious that it would not be the case, but I've seen people try to do this for individuals where they put both an internal and external email address for the same user in the same mapping - don't)

Second - if you're using iw_solution_email.ipl - then you have to define PTs to use with it - these are generally defined as task-level variables. One of the PTs will process information about job owner, task owners, etc. in order to put together the headers for the email; the other PT(s) are responsible for processing the same job and task information to put together the body of the message.

In your case, you'd want to have a PT that looked at the grouptask specified as the target task for the email - and if not currently owned, look at the sharedby information and if it finds a group like "testgroup" then expand it and use that expanded information in the To: field of the email.

A number of organizations prefer to just map such groups to email (Exchange) groups on a 1:1 basis - so that the list of recipients associated with the group is handled in that system rather than in the email_map.cfg file.

Bhargav Coca

Yes Adam that explaina whole lot of it. Any group thingy can be done in tpl's and nothing is more simplar than that. I thought I would modify my tpl for intermediate tasks in the workflow. But i wanted to try using a concurrent task as my start task and have a successor of an email task sson after that. Can this be done? I guess not.

But some how my requirements are that there needs to be concurrent email task followed by a email task to Content Contributor 1. i am doing some thing like this, but some how i am getting an error. can anyone point me out as where i am going wrong??

[html]

sub get_start_email_task_xml {
my ($i) = @_;
my $start_email_task_xml=<

owner='__TAG__(JobStartedEmail[$i]);'
description='Please review'
readonly="t"
start="t">

__INSERT__(get_cmd("iw_solution_email.ipl", "Email_Content_Contributor1"));

if (@submit_file != 0)
{
__INSERT__("\n");
for (my $i=0; $i < @submit_file; ++$i)
{
__INSERT__("
"comment='__TAG__(File_comment_$i);'/>");
}
__INSERT__("\n");
}
]]>
EOS
return $start_email_task_xml;
}
]]>
[/html]

and calling it from the start as follows

[html]

__INSERT__("
\n");
for (my $i=0; $i<__ELEM__('JobStartedEmail'); ++$i) {
__INSERT__( get_start_email_task_xml($i) );
}
__INSERT__("
\n");
]]>
[/html]

Some one point me in the right direction please.

Thanks

Adam Stoller

Yes Adam that explaina whole lot of it. Any group thingy can be done in tpl's and nothing is more simplar than that. I thought I would modify my tpl for intermediate tasks in the workflow. But i wanted to try using a concurrent task as my start task and have a successor of an email task sson after that. Can this be done? I guess not.

But some how my requirements are that there needs to be concurrent email task followed by a email task to Content Contributor 1. i am doing some thing like this, but some how i am getting an error. can anyone point me out as where i am going wrong??
...

Some one point me in the right direction please.

Thanks

What error are you getting? Can you post (as an attachment) the generated job specification file - so we can see the actual workflow specification as it gets created?

Also - since you're reasonably comfortable with Perl (or so it would seem) - you might look into using TeamSite::WFconstructor module for creating your WFTs - use perldoc on that module and look at some of the solutions/*.wft's for examples -- it won't specifically help with this issue, but it does tend to make wft development better IMO.