Announcement

Collapse
No announcement yet.

"Event Sub-Process" with "Conditional Start Event" does not work

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Event Sub-Process" with "Conditional Start Event" does not work

    Hello! I reproduced this on the demo,

    "Event Sub-Process" with Event "Conditional Start Event" - does not work
    with "Timer Start Event" - works.
    Details on the screenshots.
    Please tell me: Is this a bug or am I doing something wrong?​


    Click image for larger version

Name:	Process Flowchart.png
Views:	180
Size:	47.9 KB
ID:	109197 Click image for larger version

Name:	Timer Start Event.png
Views:	145
Size:	113.7 KB
ID:	109198 Click image for larger version

Name:	Opportunity Amount - changed.png
Views:	144
Size:	126.3 KB
ID:	109199

  • #2
    'changed', 'not changed' conditions do not work in sub-process start events.

    Comment


    • alexisc
      alexisc commented
      Editing a comment
      I understand, thank you!

  • #3
    Workaround. Using a separate Workflow that will broadcast a unique signal when a field is change. A process will listen to that signal to start a sub-process. A signal name can be a concatenation of some name with a record ID.

    Comment


    • alexisc
      alexisc commented
      Editing a comment
      Yuri, if it's not too much trouble, give an example or describe it in a little more detail.

  • #4
    1. Create a Workflow for Lead. With a trigger 'After record saved'. Add a condition Opportunity Amount > changed.

    Add an action "Execute Formula Script" with this script:

    Code:
    $signalName = string\concatenate('leadAmountChanged.', id);
    
    bpm\broadcastSignal($signalName);​​
    2. In BPM Flowchart, add an Event Sub-Process. Add Signal Start Event into that sub-process. Specify the signal name for it:

    Code:
    leadAmountChanged.{$id}

    Comment


    • #5
      Works perfectly! Yuri, thank you very much for your help!

      Comment

      Working...
      X