Advanced workflow - cannot change Action type.

Hi Bob Schumann,

Every time I have encountered this symptom, it's root cause was errant JS files in the file system. It is possible that one of the customizations installed or created in your application is causing this symptom in your instance.

To try to determine what might have introduced the symptom, are you able to determine any correlations between when the symptom began and any installed or modified customizations in your application?

Hi Patrick,

Thanks for your response.  We are using an on-demand instance and have few customizations in our instance.  I am migrating from the older workflow management processes and have not created a Process definition yet that required an Action.  Thus I have no real data to determine if my instance was ever able to create these definitions properly.

Best regards,
Bob

Hi Patrick,

Thanks for your response.  We are using an on-demand instance and have few customizations in our instance.  I am migrating from the older workflow management processes and have not created a Process definition yet that required an Action.  Thus I have no real data to determine if my instance was ever able to create these definitions properly.

Best regards,
Bob

Hi Bob Schumann,

If you have created a case with SugarCRM Support, please direct message me the Case number and I can look into it promptly.

If you have not created a support case, either:

1. Create a support case with SugarCRM
2. Direct Message me your application's URL, business name, and license key, and I can create a support case for you.

Edit: I have identified your application and I see the most likely root cause. I think this can be fixed in a matter of minutes once the case is created. Fixing it will require uninstalling one of your customizations, so the ultimate fix might involve getting an update of that customization from its developer. I will give you the details in the case once we're in dialogue there.

Additional Edit: If a customization is on this list, it is there because of a known issue that customization causes in Sugar applications.

In some cases, the root cause is simply an out of date version of the integration. In other cases, every version of the integration is incompatible with Sugar.

I hope this helps!