AnsweredAssumed Answered

sub-process not triggering a custom task

Question asked by Prateek Bhatnagar on Jun 29, 2016
Latest reply on Jul 14, 2016 by Mostafa Helmy

Like • Show 0 Likes0
Comment • 2

Hi all,

We have a requirement to call a custom task from within another custom task. To meet the requirement, I thought I will use sub-process node in the Custom Task 1(CT1), and in sub-process node, I will call Custom Task 2(CT2).

I ran CT1, it completed successfully but CT2 never got triggered (run history for CT2 didn't get updated). Has anyone run into this issue? Below is the screenshot from CT1 showing sub-process node setup to call CT2 (Update Service Indicator). Am I missing something here? I am on RSA VIA 6.9.1 P10.

Mostafa Helmy

Jul 14, 2016 5:58 AM

Correct Answer

I just tested this in-lab on 6.9.1 P14 and got the same behaviour, looks like Custom Tasks cannot call (or cannot be called from) Sub-process nodes. Please create a support case, referencing this discussion thread to be able to engage engineering resources and check the expected behaviour.

See the reply in context

No one else had this question

Outcomes

Paul Soczka

Jul 13, 2016 1:48 PM

If you open the details of a request which has completed successful involving this workflow, do you see the sub-task in CT1 showing green? If it does, then it would sound like an error to me. I know that custom workflows have sone odd behaviour at times but this is not one I am aware of. If you can confirm this is the case then we would want to have engagement from an engineering resource to confirm from a product behavior perspective.

Paul.

2 Replies

Paul Soczka Jul 13, 2016 1:48 PM
Mark Correct
Correct Answer
If you open the details of a request which has completed successful involving this workflow, do you see the sub-task in CT1 showing green? If it does, then it would sound like an error to me. I know that custom workflows have sone odd behaviour at times but this is not one I am aware of. If you can confirm this is the case then we would want to have engagement from an engineering resource to confirm from a product behavior perspective.

Paul.
Like • Show 0 Likes0
Actions
Mostafa Helmy Jul 14, 2016 5:58 AM
Unmark Correct
Correct Answer
I just tested this in-lab on 6.9.1 P14 and got the same behaviour, looks like Custom Tasks cannot call (or cannot be called from) Sub-process nodes. Please create a support case, referencing this discussion thread to be able to engage engineering resources and check the expected behaviour.
Like • Show 0 Likes0
Actions

sub-process not triggering a custom task

Outcomes

Related Content

Recommended Content