Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determining gateway flow from data attribute #51

Open
hpl002 opened this issue Mar 5, 2021 · 2 comments
Open

Determining gateway flow from data attribute #51

hpl002 opened this issue Mar 5, 2021 · 2 comments

Comments

@hpl002
Copy link

hpl002 commented Mar 5, 2021

Feature request:

I have two new features that i think would come in very handy.

Adding colored tokens

Comparable process simulation approaches such as Colored petri-nets and CPN Tools allow for colored tokens. These tokens are basically just object which can contain any number of attributes.

adding actual task execution to tasks

here we could write additional attributes to these colored tokens which could then impact behavior further out in the process

Adding branching conditions

the token attributes should be evaluated and then used to determine process flow
This would allow for much more complex process behavior.

@hpl002
Copy link
Author

hpl002 commented Mar 5, 2021

Story

Screenshot 2021-03-05 at 13 28 36

For example in this credit card application process we would permit perpetual repetitions of the application dispute.

Meaning that the application can be rejected, and then the applicant is allowed to try to apply more than once.

Here we might want to add a condition that would allow the dispute to occur once, and on the second try we force a rejection.

Using only probabilities does not allow for this behavior.

@LeonBein
Copy link
Collaborator

LeonBein commented Mar 19, 2021

Sorry for the late answer.
There already exists the DataObject Plugin to support bpmn data objects with values that influence the simulation. I am not sure how elaborate the plugin is, but it contains possibilities to make decisions depending on the data and I think also to change the data on task termination.

In the example, one maybe would use a data object called "application", which is created at the start event and then updated at the according tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants