Hi..after searching a lot, I still have questions about limitations of flexible workflow over classical workflow. Can we use below features of classical workflow in flexible scenario? 1. Use of Fork. 2.Use of Process Control. 3.Use of Block. 4.Use of subworkflow. 5. Use of Event Listener There are many more step types where flexible workflow is limited. Can we achieve them or do we have any blogs which lists out all of these limitations.
@McCoy-TV
3 ай бұрын
Hi Bishnu, Thank you for your question. We can't provide a precise answer regarding the use cases of these specific features. The flexible workflow does offer options for Badi implementations for agent determination and start conditions. It might be possible to realize the features you're asking about by combining the standard functionality with Badi implementations, but we haven't done this ourselves. Keep in mind that flexible workflows are presented as a leaner, simpler alternative to the classical workflow. If your requirements rely on the above features, the classical workflow might be a better option due to its greater versatility. We hope this helps! Greetings Nick & Jazwin
@bishnutrivedi3089
3 ай бұрын
Thanks a ton for your response!! I will try to explore these options using Badi approach and see to cater the possibilities.
@mhtan88
9 ай бұрын
Can flexible workflow can apply for master data creation, update and delete?
@McCoy-TV
9 ай бұрын
Hi Mhtan88, thanks for your question. Flexible Workflows can as of yet not be applied to masterdata creation. It is mostly used to approve or reject transactional documents. Maybe this is something that they will add in the future but not for now. Greetings Nick & Jazwin
Пікірлер: 5