Bizarre Email error

[hwa...@bcsglobal.com]

Hello,

I want to send different email subject and different email body to different people in a workflow process.

My chain of events is--- start ...some manual task...send email 1...send email 2...some manual task...end

However when i execute this process i get an error. Runmyprocess sends me "Email 1" but then stops at that step. It dose not send email 2. the settings for Email 2 are exactly like email 1 except subject and body of email.

Error received:

2014-09-08T21:08:37+0000 - Task "Notify_L" (id: 70[0] - status: ABORTED): Error while processing
-------
2014-09-08T18:48:30+0000 - Event Start "Start" (id: 0 - status: ACTIVE): Cannot compute request name : Error while processing {request_id} / {customer_name_}
Expression request_id is undefined on line 1, column 3 in Start.
-------
2014-09-08T18:48:30+0000 - Starting: Cannot compute request name : Error while processing {request_id} / {customer_name_}
Expression request_id is undefined on line 1, column 3 in temp.

I fail to understand why this is happening because it is an email step and not a manual task

Please help.

Regards,

[thoshino]

Hi,

The error message indicated that a process variable called

"request_id"

does not exist.

I think it is used in this expression

 {request_id} / {customer_name_}

Regardless of activity type (Email, Connector, Subprocess, Manual, Script), variable missing error can occur.

It seems that you have a process report for the instance open, can you check the parameters tab, and see list of available variables in 3 sections. Initial, Computed, and Internal.

request_id must be listed there for the email task to successfully complete.

If it is not, you must edit process design, add it anywhere previous, as input or output variable.

Best regards,

Taka

[Harvinder Wazir]

The variable request_id is present in the "Computed parameters section" of the Parameters tab. So this means the email should have functioned properly ?

So i am back to square one. What should i do next ?

regards,

--

Harvinder Wazir,

Customer Services And Innovation group

BCS Global Networks Ltd

5525 Eglinton Ave. W. Unit 128

Toronto, Ontario, M9C 5K5

Phone:     647-722-8516

Cell:         416-320-6472   

Web:        www.bcsglobal.com

 leading worldwide provider of video conferencing and collaboration services

London / Toronto / New York / Shanghai / Hong Kong

[thoshino]

Hi,

The error log, it has 3 lines:

2014-09-08T21:08:37+0000 - Task "Notify_L" (id: 70[0] - status: ABORTED): Error while processing 
-------
2014-09-08T18:48:30+0000 - Event Start "Start" (id: 0 - status: ACTIVE): Cannot compute request name : Error while processing {request_id} / {customer_name_}
Expression request_id is undefined on line 1, column 3 in Start.
-------
2014-09-08T18:48:30+0000 - Starting: Cannot compute request name : Error while processing {request_id} / {customer_name_}
Expression request_id is undefined on line 1, column 3 in temp.

1st (bottom) and 2nd line (middle) is clear.

I believe you have "dynamic label" for the process configured, and using those variables, which doesn't exist at those points for some reason.

You can add default values to it (by !"" notation) to avoid this.

Example would be:

${request_id!"undefined"} / ${customer_name_!"undefined"}

or

${request_id!"N/A"} / ${customer_name_!""}

something like this.

Then for the 3rd line (top one)

2014-09-08T21:08:37+0000 - Task "Notify_L" (id: 70[0] - status: ABORTED): Error while processing 

This one is the REAL reason why the process stopped working for you.

Sorry I was not able to identify this with my first reply.

Is there any further info in this error?

Any lines you skipped copying/pasting?

The issue is somewhere in Task named "Notify_L".

Error could be from Input variable (calculated before the activity),

Email or Connector setting (the activity),

or Output variable (calculated after the activity).

I hope this helps to narrow down the issue solving.

Best regards,

Taka

[Harvinder Wazir]

Hello Thoshino,

Thanks for your email. I do not think the findings you shared are accurate. Even so I did try inserting the null values as you suggested but it made no difference. I got same error.

You said error could be because of some error ( what error ? ) because the variables request_id and customer_name_ do not exist at the point in time in the process when error is generated. but these two variables are captured very well before in the process.

Also you said the Major error was due to input or output error on "Notify L" task. however there are no input or output variables configured. So this wouldnt be the case.

Could we have a look together on this process ?

Regards,

[thoshino]

Hi,

For later reference.

The blocking issue was email activity, message body referring to ${P_task_url} which should only be used in Manual task.

It was resolved by using get_next_url function instead.

http://docs.runmyprocess.com/API_Reference/FM/Request.html#get_next_url

The error message about request name was resolved by

${request_id!""} / ${customer_name_!""}

Best regards,

Taka