Setting up Conditions

English Language - Forum Advanced OpenSales, Workflow, Portal support
1

Hello,

we want to achieve that emails are send when a value of a field is changed to something specific. For this case: Field: ‘Status_B’ is changed to ‘Plan’.
What we did so far can you see in the screenshots. For the first conditions emails are being send when e.g. Field Name is changed and Status_B is Plan.
For the second condition no emails are being send. How do we have to set up conditions so that emails are only being send when Status_B is changed to Plan?

2

Edit: I’ve set up the following for a non-custom module AOS_Invoices and the workflow runs as expected. Is there any hook or file that I’m missing for my custom module?

3

Edit2: After some investigations I’ve found the problem in having too many audited fields. Is there a limit? Would be nice to know if there is one.

4

Edit3: Workflows do not work on audited fields, can anyone confirm this? This is a real issue for us. How can we have both - workflows working with auditied fields?

5

you need to provide the version of your SuiteCRM, if you want us to confirm something that is not working, we need to have what you have.

best regards

6

Hello Mike,

sorry. We’re using 7.6.4 with Sugar 5.2.3.

7

ok, I’ll test this on my system but let me ask you, why you have two conditions like “any change” and also when change to Plan? one condition when change to plan is enough to trigger the workflow, on any change should be used when you don’t have a particular valor to monitor, in example when a number field is changed and you can’t know the new value that can be.

best regards

8

Because emails were sent when someone has made changes to any other field and ‘status_b’ was ‘plan’.
Like status_b = plan and changes to the name will execute this workflow. This was not what we wanted to archieve with this workflow and that is why we have set it up to only fire when something has changed in status_b.

9

Oh right, you’re absolutely right, testing right now.

best regards

10

I can confirm that audited fields are not triggering workflow, thanks for finding this issue, I’ll check if there’s no issue created on github

best regards

11

I’ve logged an issue on the issue tracket https://github.com/salesagility/SuiteCRM/issues/1647

best regards

12

there was already an issue regarding this problem, and is fixed here https://github.com/salesagility/SuiteCRM/pull/1648

best regards