When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

shafaly — Tue, 17 Jul 2018 10:05:32 GMT

Hi Shubham Aware,

Can you please fetch this Expression rule in the script task before the node where you applied exception and store the value in the variable of type boolean and use the variable in the exception, instead of expression rule.

This should be working fine.

Hope this will help you.

Thanks

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

shafaly — Tue, 17 Jul 2018 10:04:55 GMT

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

wesleyj1387 — Mon, 16 Jul 2018 19:02:51 GMT

I agree, I think there is a limitation here. I am experiencing the same issue with a start event timer. I am getting the following error whenever I use a query rule or a!queryEntity:

ERROR:EVAL:@reason=index

This is related to the knowledge base article, but that article only mentions the load() statement. It would be great to have this fixed, but in the interim, could we include query rules and queryEntity() in the article or in the Appian documentation?

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Will Teoh — Mon, 18 Jun 2018 01:51:47 GMT

Not sure if it is due to the limitation that we can't actually query anything in the start node with timer.
I have tried to put a query in the timer start node to query the database table for a flag, but that couldn't work.

However, if you start the process manually, it works fine.

Perhaps someone from Appian can verify this. I suggest you log a support ticket to them to enquire about this. Although they told us to post our question in the community, but this can't be 100% sure that someone will answer us.

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Shubham Aware — Fri, 25 May 2018 12:27:21 GMT

i have tried with tp!id still same issue

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Shubham Aware — Fri, 25 May 2018 10:32:36 GMT

yes all basic functionality is working fine like retrieving data from report

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 10:32:30 GMT

ppid_int is the process properties id? I think it should be assigned to the tp!id i.e task properties id.

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Shubham Aware — Fri, 25 May 2018 10:30:48 GMT

yes i have created task report and passed that in constant (refer code snippet snapshot)

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 10:24:50 GMT

is the process id coming properly? did you try to print it out

Thanks,
Ak

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 10:22:37 GMT

Did you create a process or a task report before using this a!queryProcessAnalytics() ??

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Shubham Aware — Fri, 25 May 2018 10:16:07 GMT

Actually i have tried using ri! and pp!id also it throwing same error,
and also i have removed null check from it same situation here also.

I have tested queryProcessAnalytics() function with harcoded process id it's giving proper output.
I have passed any other condtion rather than queryProcessAnalytics() it's working properly

Don't know this happening

Thanks!!

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 08:53:09 GMT

And please check the a!queryProcessAnalytics() value before indexing the value to the expected value. Please check whether it is returning output of the desired form.

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 08:50:52 GMT

I see here that you have checked null for ppid_int. As far as i know the value of ppid_int should be null. Please define ppid_int as an ri in the expression rule and pass the pv!ppid_int to the ri. Can you try on this. This is likely to cause trouble.

If this doesn't solve the problem let me know for further discussion. And you can remove the null check as the value of pv will not be blank.

Thanks,
Ak

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

Shubham Aware — Fri, 25 May 2018 08:37:41 GMT

Hi abishekk109 (abhishekk109)

I have called this rule from timer condition while setting escalation

P.S. :- Value of ppid_int is set to pp!id before user input task

Thanks,

Shubham

RE: When i try to execute queryProcessAnalytics inside Escalation timer rule event it change it's status to Paused by exception

abishekk109 — Fri, 25 May 2018 07:28:58 GMT

Hi,

Can you please provide more info on this. Your expression snippet and how you have called it in escalation tab..

Thanks,
Abishek Kulothungan