Hi everyone,

I'm new to IBM Business Automation Manager Open Editions (BAMOE) but have over 10 years of experience with TIBCO BPM. While both tools are BPMN 2.0 compliant, I'm experiencing significant differences in their approach to workflow design. I would greatly appreciate your guidance on the following observations:

1. Calling a Subprocess: In BAMOE, we must provide the specific Called Subprocess ID at design time. The developer is also expected to know the exact input and output parameters of the called process. It doesn't seem possible to call a subprocess dynamically (i.e., deciding which sub-process to invoke at runtime based on data conditions). Is this correct?

2. User Task Assignment: Assignments appear to be static, where we simply write the name of an actor or group directly in the properties at design time. How can we make these assignments dynamic, for example, based on data from a process variable or an external system call?

3. Script Task: I've noticed there is no syntax or type validation for scripts (e.g., MVEL, FEEL) at design time. Are all validations for these tasks deferred to runtime?

My Questions:

• Are my observations correct?

• If yes, does this mean that a significant portion of the validation happens only at runtime?

• If my understanding is incorrect, could you please guide me to the right learning resources? The official IBM documentation, while useful, often lacks detailed explanations for the properties and usage of each activity/node.

I am feeling quite blocked. I'm not sure if this is due to coming from a TIBCO BPM background, which felt more developer-friendly in these specific aspects, or if I'm simply unable to find the right learning resources for BAMOE.

Thank you in advance for your help!

Regards

Kotresh Matt

Hi kotresh,

1. Yes, your understanding about sub-process is correct. You need to provide details about subprocess and input/output paramters at the desgin time only.  If you want to dynamically execute specific set of nodes based on condition then you can check the ad-hoc subprocess node.
2.  To assign values of actor or group  field using process variable, you can use #{processVariableName} for actor or group property. Runtime value of processVariable will be assigned for actor or group field. 
3. Script Tasks supports java expressions for 9.3.0 release. Syntax validation will happen at compile/build time. 

Hi everyone,

I'm new to IBM Business Automation Manager Open Editions (BAMOE) but have over 10 years of experience with TIBCO BPM. While both tools are BPMN 2.0 compliant, I'm experiencing significant differences in their approach to workflow design. I would greatly appreciate your guidance on the following observations:

1. Calling a Subprocess: In BAMOE, we must provide the specific Called Subprocess ID at design time. The developer is also expected to know the exact input and output parameters of the called process. It doesn't seem possible to call a subprocess dynamically (i.e., deciding which sub-process to invoke at runtime based on data conditions). Is this correct?

2. User Task Assignment: Assignments appear to be static, where we simply write the name of an actor or group directly in the properties at design time. How can we make these assignments dynamic, for example, based on data from a process variable or an external system call?

3. Script Task: I've noticed there is no syntax or type validation for scripts (e.g., MVEL, FEEL) at design time. Are all validations for these tasks deferred to runtime?

My Questions:

• Are my observations correct?

• If yes, does this mean that a significant portion of the validation happens only at runtime?

• If my understanding is incorrect, could you please guide me to the right learning resources? The official IBM documentation, while useful, often lacks detailed explanations for the properties and usage of each activity/node.

I am feeling quite blocked. I'm not sure if this is due to coming from a TIBCO BPM background, which felt more developer-friendly in these specific aspects, or if I'm simply unable to find the right learning resources for BAMOE.

Thank you in advance for your help!

Regards

Kotresh Matt

Hi kotresh,

1. Yes, your understanding about sub-process is correct. You need to provide details about subprocess and input/output paramters at the desgin time only.  If you want to dynamically execute specific set of nodes based on condition then you can check the ad-hoc subprocess node.
2.  To assign values of actor or group  field using process variable, you can use #{processVariableName} for actor or group property. Runtime value of processVariable will be assigned for actor or group field. 
3. Script Tasks supports java expressions for 9.3.0 release. Syntax validation will happen at compile/build time. 

Hi everyone,

I'm new to IBM Business Automation Manager Open Editions (BAMOE) but have over 10 years of experience with TIBCO BPM. While both tools are BPMN 2.0 compliant, I'm experiencing significant differences in their approach to workflow design. I would greatly appreciate your guidance on the following observations:

1. Calling a Subprocess: In BAMOE, we must provide the specific Called Subprocess ID at design time. The developer is also expected to know the exact input and output parameters of the called process. It doesn't seem possible to call a subprocess dynamically (i.e., deciding which sub-process to invoke at runtime based on data conditions). Is this correct?

2. User Task Assignment: Assignments appear to be static, where we simply write the name of an actor or group directly in the properties at design time. How can we make these assignments dynamic, for example, based on data from a process variable or an external system call?

3. Script Task: I've noticed there is no syntax or type validation for scripts (e.g., MVEL, FEEL) at design time. Are all validations for these tasks deferred to runtime?

My Questions:

• Are my observations correct?

• If yes, does this mean that a significant portion of the validation happens only at runtime?

• If my understanding is incorrect, could you please guide me to the right learning resources? The official IBM documentation, while useful, often lacks detailed explanations for the properties and usage of each activity/node.

I am feeling quite blocked. I'm not sure if this is due to coming from a TIBCO BPM background, which felt more developer-friendly in these specific aspects, or if I'm simply unable to find the right learning resources for BAMOE.

Thank you in advance for your help!

Regards

Kotresh Matt

Hi everyone,

I'm new to IBM Business Automation Manager Open Editions (BAMOE) but have over 10 years of experience with TIBCO BPM. While both tools are BPMN 2.0 compliant, I'm experiencing significant differences in their approach to workflow design. I would greatly appreciate your guidance on the following observations:

1. Calling a Subprocess: In BAMOE, we must provide the specific Called Subprocess ID at design time. The developer is also expected to know the exact input and output parameters of the called process. It doesn't seem possible to call a subprocess dynamically (i.e., deciding which sub-process to invoke at runtime based on data conditions). Is this correct?

2. User Task Assignment: Assignments appear to be static, where we simply write the name of an actor or group directly in the properties at design time. How can we make these assignments dynamic, for example, based on data from a process variable or an external system call?

3. Script Task: I've noticed there is no syntax or type validation for scripts (e.g., MVEL, FEEL) at design time. Are all validations for these tasks deferred to runtime?

My Questions:

• Are my observations correct?

• If yes, does this mean that a significant portion of the validation happens only at runtime?

• If my understanding is incorrect, could you please guide me to the right learning resources? The official IBM documentation, while useful, often lacks detailed explanations for the properties and usage of each activity/node.

I am feeling quite blocked. I'm not sure if this is due to coming from a TIBCO BPM background, which felt more developer-friendly in these specific aspects, or if I'm simply unable to find the right learning resources for BAMOE.

Thank you in advance for your help!

Regards

Kotresh Matt

Hi everyone,

I'm new to IBM Business Automation Manager Open Editions (BAMOE) but have over 10 years of experience with TIBCO BPM. While both tools are BPMN 2.0 compliant, I'm experiencing significant differences in their approach to workflow design. I would greatly appreciate your guidance on the following observations:

1. Calling a Subprocess: In BAMOE, we must provide the specific Called Subprocess ID at design time. The developer is also expected to know the exact input and output parameters of the called process. It doesn't seem possible to call a subprocess dynamically (i.e., deciding which sub-process to invoke at runtime based on data conditions). Is this correct?

2. User Task Assignment: Assignments appear to be static, where we simply write the name of an actor or group directly in the properties at design time. How can we make these assignments dynamic, for example, based on data from a process variable or an external system call?

3. Script Task: I've noticed there is no syntax or type validation for scripts (e.g., MVEL, FEEL) at design time. Are all validations for these tasks deferred to runtime?

My Questions:

• Are my observations correct?

• If yes, does this mean that a significant portion of the validation happens only at runtime?

• If my understanding is incorrect, could you please guide me to the right learning resources? The official IBM documentation, while useful, often lacks detailed explanations for the properties and usage of each activity/node.

I am feeling quite blocked. I'm not sure if this is due to coming from a TIBCO BPM background, which felt more developer-friendly in these specific aspects, or if I'm simply unable to find the right learning resources for BAMOE.

Thank you in advance for your help!

Regards

Kotresh Matt