nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TAG('iw_user')

Bhargav Coca

This should be working for some reason it is not.
I have a simple workflow with a single Author to approver flow. At the email stages the owner is iw_user (DOMIAIN\user1) and at the approver and author work stages the owner is (user1). Actually i am hardcoding user here. If i say the owner to be iw_user it gives an error, saying that the task owner is not valid.

So i thought i would get the user from iw_user and use it in the task, but some how this doesnt work too. here is my snippet

my $initiator = __TAG__('iw_user');
$_ = $initiator;
my @personal = split(/\/);

and i am using $personal[1] as the user.

Please correct me.

Thanks

Find more posts tagged with

Comments

Migrateduser

Are you using the code in the WFT or cgitask or externaltask.

Bhargav Coca

I am using this code in the wft. All i need is user for in my approver and author work stages. They wouldn't accept anything which is like 'DOMAIN\user1'

Thanks

Migrateduser

Try this
my $initiator = __VALUE__('iw_user');

<usertask owner=__INSER__($initiator); ... >
.........
</usertask>

Bhargav Coca

No it is not working. Its like this the workflow as such works , but the email which has to be sent before the approver task is not being sent out for the approver, since owner of the approver task is DOMAIN\user1.

If the owner is only 'user1' the email will be sent.

Hope it makes sense.

Thanks

Adam Stoller

No it is not working. Its like this the workflow as such works , but the email which has to be sent before the approver task is not being sent out for the approver, since owner of the approver task is DOMAIN\user1.

If the owner is only 'user1' the email will be sent.

Hope it makes sense.

Thanks

As batasari noted - you have to use __VALUE__() within the Perl context of a WFT, __TAG__() should only be used within the XML context of a WFT. (he does have a typo where he left of the T in __INSERT__() though ;-)

If you are using iwsend_mail.ipl or iw_solution_email.ipl - the fact that the username has the windows domain prefix in front of it should be handled by the script.

If you are using your own home-grown email script - you need to make sure to handle the windows domain prefix (if the userid@domain is valid - you can just strip off the domain, if you are using a mapping file, you should probably make sure the mapping entries contain the windows domain prefix or remove the prefix before looking them up - otherwise you won't get a match).

Bhargav Coca

Thank you guys, i am using the map file. I had to strip the user from the domain which is always appended to it. I used simple perl and got rid of it and used the value in my tasks and it works fine now.

Now that all my approver stages and emails are working i though to incoporate Success Email task before the end task and it doesn't like me. Here is the task and the varaibles which i am using there are defined below.

[html]

owner="__TAG__('iw_user');"
description="Please complete Success email task">

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

Where

my $success_email_header="$wft_dir/$this_dir/ccmail_header2.tpl";
my $success_email_body="$wft_dir/$this_dir/ccmail_htmlbody2.tpl";
[/html]

The above variable point to the right path where the tpl files exist. So i think my way of defining the path in the external task is wrong some where.

When i run the workflow there are no errors, the only thing is Success email is not sent to me.
Please advice.
Thanks

nipper

Now that all my approver stages and emails are working i though to incoporate Success Email task before the end task and it doesn't like me.

Lilley, don't take it personal. I certain you are a very nice person, this script does not like a lot of people. Smiley Very Happy

Try turning on debug, edit the ipl file and look for debug, add verbose as well.

They should create a file iw-home/tmp/iw_solutions_debug.log

Check that & see what it says. Often there is some miscommunication between the mailer and the TS box. In my case emails of me@company.com work but me@yahoo.com were bounced due to spam filters.

HTH

Andy

Bhargav Coca

Thank you Nipper. I would certainly follow your advice. I just wanted to make sure that my understanding of the external task is good. From the snippet i have pasted, i wante dot know if my way of referencing the tpl's is right.

My Mandatory approver email is working and the email sent to author if there was a reject is working. I thought if i can use the saem external task with approriate Succ and pred elments then my success email would work. But seems like its not that easy to get that working.

I appreitiate your reply and i would keep trying , and post you the solution as where i went wrong.

Thanks

ErrorMessage.jpg

Migrateduser

Check your externaltask job specification to see if the TPL's are set correctly. You need to use __INSERT__($success_email_header); & __INSERT__($success_email_body); to insert the header and body tpl's to externaltask.

Bhargav Coca

I got the right path, but still no email.

here is the debug snippet.

[html]

owner="NECELAM\\andy"
description="Please complete Success email task">

[/html]
Thanks

nipper

It is working with the same email in a different step in the same WF ?

Can you post the code that works ?

Bhargav Coca

yes it works, all other email stages work.

here is the snippet.
[html]

owner="__TAG__('iw_user');"
description="Please complete the author email task">

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

[/html]

Thanks

Adam Stoller

I got the right path, but still no email.

Step 1: Verify whether or not iw_solution_email.ipl is getting executed.
- If not, the problem is in the WFT code, otherwise...
Step 2: Verify that the PTs you are using with iw_solution_email.ipl work
- I believe someone already mentioned enabling debugging in the iw_solution_email.ipl script - I believe from there you should be able to see the results that occurred when it tried to run iwpt_compile.ipl on the workflow's XML data using your PT(s) - chances are this is where the problem is and you "simply" need to debug your PTs.