Comment 7 for bug 1290618
Revision history for this message
| Santiago Baldassin (santiago-b-baldassin) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
I'm ok with having a consistent experience that's why I suggested that we should change projects to work as aggregate is working now :)
The problem with using workflows with multiple steps is that we have to add some logic to understand which of the workflows steps have been updated by the user and act based on that. In this particular case for example, let's say we wanted to update the aggregate name, the workflow with the two tabs would be opened and the name will be updated.
Now in the workflow handle method we don't know if the user updated the aggregate info or the aggregate hosts or both. So we'll have to add some logic to determine what changed and all of this to let the user update the aggregate name :)