Regression on (ACT 1546 - Impossible to assign default flow on exclusive gateways)?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2013 04:00 PM
Hi,
I'm using 5.14 but am experiencing the same behavior as the Jira ticket (ACT 1546) claims to have fixed.
Regression?
-Lee
I'm using 5.14 but am experiencing the same behavior as the Jira ticket (ACT 1546) claims to have fixed.
Regression?
-Lee
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2013 05:59 AM
Like I said in the other post: do you see the designer or engine bug?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2013 05:21 PM
Sorry for the double post.
The designer is where I see the problem. Default flows are not preserved when importing XML models with default flows.
When modeling default flows in the designer, they are not present if you re-edit the same model. Nor are the graphical mnemonics present on the diagram in the explorer.
I have not tested with the engine as I don't want to use these if they're bugged. Instead I just add a conditional to every flow as a workaround
The designer is where I see the problem. Default flows are not preserved when importing XML models with default flows.
When modeling default flows in the designer, they are not present if you re-edit the same model. Nor are the graphical mnemonics present on the diagram in the explorer.
I have not tested with the engine as I don't want to use these if they're bugged. Instead I just add a conditional to every flow as a workaround
