Triggering Advanced Workflow processes in PHP customizations

RE: Triggering Advanced Workflow processes in PHP customizations

Matt Marum — Tue, 31 Jul 2018 14:39:55 GMT

You could also try to use aliases:

use Sugarcrm\Sugarcrm\ProcessManager\Registry as RegistryA;
...
use Sugarcrm\Sugarcrm\ProcessManager\Registry as RegistryB;

Etc.

This would allow you to define multiple local usages of this class within the same file (scheduledtasks.ext.php) without causing name conflicts. You would just need to make sure your alias names are unique.

PHP: Using namespaces: Aliasing/Importing - Manual

RE: Triggering Advanced Workflow processes in PHP customizations

Dennis Wangerin — Mon, 30 Jul 2018 16:13:52 GMT

Hi Marcel Lyyra,

When using that workaround in the Extension framework you need to make sure that it the following only loaded once per file:

use Sugarcrm\Sugarcrm\ProcessManager\Registry;

Let's say you have two schedulers where you want to use it:

./custom/Extension/modules/Schedulers/Ext/ScheduledTasks/jobA.php
./custom/Extension/modules/Schedulers/Ext/ScheduledTasks/jobB.php

If you add use Sugarcrm\Sugarcrm\ProcessManager\Registry; both of those files would be merged into the following single file and thus cause a PHP error as you described since the same namespace is used twice:

custom/modules/Schedulers/Ext/ScheduledTasks/scheduledtasks.ext.php

So adding this only to jobA.php should also allow to the namespace in jobB.php since both will be merged into one file custom/modules/Schedulers/Ext/ScheduledTasks/scheduledtasks.ext.php where the namespace would be loaded once then. This is the file that is used in the cache/ to actually run both schedulers.

Can you confirm if loading this through the Extension framework and making sure the namespace is only loaded in the first file resolves this issue?

RE: Triggering Advanced Workflow processes in PHP customizations

Marcel Lyyra — Wed, 18 Jul 2018 20:08:14 GMT

I'm having trouble because I have several PHP codes that set a value that triggers a workflow for multiple records. As I use this same workaround on every code, it has the same Registry path, which causes them to fail as it is located at the same file. So I was advised to change the Registry name for each code. I'm just not very sure as how to change the Registry on the workaround lines.

RE: Triggering Advanced Workflow processes in PHP customizations

Aaron Kerr — Wed, 23 May 2018 13:35:51 GMT

Thanks for this post! We had been banging our heads against a dev issue which made no sense for a couple of days. Fixed now.