-
Notifications
You must be signed in to change notification settings - Fork 1
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
Task order #85
Comments
I'm not sure I understand the bug. Why does it matter? For equivalency? To generate a workflow? Perhaps we need to explore automatic workflow generation based on a set of tasks and a meta-flow to consider potential problems? |
Let's consider a constraint :
In the XML code, the representation is the following : The problem is that the constraint in the FM will be the one in the XML code : |
? No we should have. Is there something wrong? |
Maybe it is not clear.
but not :
|
Fix the task order issue for the merging step.
Description : The graphical order is different than the tasks order in the XML code. When a user duplicate a task, this task is graphically located according to the user wishes but it is not the case in the XML code. As a consequence, constraints are distorted due to a bad order.
Example :
original workflow :
modified workflow (tA is duplicated as a new task tB) :
Proposition : Consider the graphical order
The text was updated successfully, but these errors were encountered: