Maturity of "Invoke process" activity in process builder

Hi Experts,

I am facing a problem regarding to the "Invoke process" activity in process builder.The problem is that if the child process which the activity is calling, uninstalled or versioned it is not possible to reopen the activity inspector in process builder.If the child process template is uninstalled state then it is easy, installing the child process solves the problem, but if the child process is versioned then things become very difficult. The activity does not call the current version of the child process so if you want to update this, then there is no way to open the activity inspector.It just doesn't work.The only way to make the activity call the current version of the child process is deleting the activity, and redesigning this part of the process.

Do you have a solution of that problem?or are you doing in the same way too?

Thanks in advance

Find more posts tagged with

Comments

Miller-zzMST

Hi Imran,

It seems you met some bug. In my environment when I create a version for child proccess, the field 'Process Name' in parent process just becomes empty. Only thing I need to do is to open this activity, select again the child process, change mapping if it is requiered and save the parent process. So there is no problem to open the 'Invoke Process' activity again.

Which version of PB are you using? At the moment I have 6.6 patch 14.

Imran_Yusubov

Hi Konstantin,

Thank you very much for your reply, my environment is 6.7 sp1 but this thing is behaving in this way..

DCTM_Guru

I'm guessing that the activty just records the object ID of the child process at design time. There could still be a scenario where you want the parent process to still call the older version of the child process. I do agree with you that EMC could enhance this activity template.

As a workaround, is it possible to could use DQL Read activity to find the object ID of the current version of the child process and then pass this in to the invoke process activity?

Miller-zzMST

Hi!

Johnny,

As a workaround, is it possible to could use DQL Read activity to find the object ID of the current version of the

child process and then pass this in to the invoke process activity?

Great idea. Some time ago I think about it too, but in my project I had to abandon because of some requirements.

There is no out-of-the-box possibility to pass object id to Invoke Process activity.

Imran,

you could try to make some enhancement for the xCP workflow utils xCelerator. It has a 'workflow initiation' BOF module. One of it's input parameters is the 'process name'. I think it is possible to change this parameter some to 'process id'. But this module has one major disadvantage - you could pass to child process only some package, without process variables.

By the way, could you check the Process Builder's log (<Documentum_dir>\logs\processbuilder.log - by default)? Is there any info when you try to open 'Invoke process' activity?