Aydin Toprak (topra)
Sr. System Architect
Pegasystems Inc.
topra Member since 2016 19 posts
Posted: February 23, 2017
Last activity: February 24, 2017
Posted: 23 Feb 2017 15:39 EST
Last activity: 24 Feb 2017 4:19 EST

Best practices to implement generic process


I have a question regarding the best practice approach for designing simple but also very clever workflow.

The workflow will probably have one main flow and may have some few sub flows but will be servicing around 250*300 different requests.

Each request (lets say a customer address change) should have "X" number of approvals, own sections (to be shown on the approval assignments) and some different data transforms and activities.

So I have many rules that must be selected by the type of the request, and consumed by its own flow.

What I think is to use a decision table and use one row for a flow type. This row contains the name of the rules (sections, Dts, and Activities .. etc). I can get the names of the rules from this activity but I am not sure If I can use them or not.

For example, even If I find the correct section name, I am not sure If I can set it to the correct flow action. When we create flow action, we select the section directly, I guess can not give a reference ... right ?

My idea might be totally wrong as I am quite new in Pega world.

The approach and doable solution counts. But If this kind of workflow brings so much complexity or so hard for maintenance, than we can think about separate flows as well.

What do you think ?

Any ideas are welcome!

Low-Code App Development Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.