Editor: restriction of dynamic instance creation for MI tasks

[yawlfoundation]

If an MI task has dynamic instance creation, it should be possible to restrict 
this to static via the configuration dialog. However, the check box for this 
feature is always grayed out. 

Original issue reported on code.google.com by marcello...@gmail.com on 10 Feb 2011 at 10:03

[yawlfoundation]

Expected behavior of the forbid button:
- is enabled when the MI has dynamic creation, otherwise it's grayed out
- if checked, when committing a configuration, dynamic creation will turn into 
static
- if unchecked, nothing happens when committing
- it doesn't override the MI settings until when committing a configuration. 
This is the same for the other MI configuration parameters

Also, I noticed that the other MI configuration parameters (increase of minimum 
and threshold, decrease of maximum) are not properly updated when the MI 
parameters are changed. Try this: create an MI task, set it as configurable and 
open the MI configuration dialog. You will see the correct values of your MI 
parameters in this dialog. Now go back to the MI parameters dialog and modify 
them. If you now check the MI configuration dialog, you will see that there are 
still the old values. 

Expected behavior:
- the content of the MI configuration dialog should get updated whenever the MI 
parameters are changed.
- if the MI configuration parameters are changed (e.g. there is an increase in 
the threshold or a decrease in the maximum no of instances) these values will 
be used to override the MI parameters when the configuration is committed, but 
not before
- [this should already be implemented] the value of the minimum after 
increasing it cannot exceed the value of the maximum. This thus constrains how 
much I can decrease the maximum
- ["] the value of the maximum after decreasing it cannot be lower that the 
value of the MI minimum. This thus constrains how much I can decrease the 
maximum
- ["] the value of the threshold after its increase cannot exceed the value of 
the maximum. This thus constrains how much I can increase the minimum
- what happens if I have set the MI configuration parameters but then I change 
the MI parameters? In this case, the MI configuration parameters should be 
reset to the MI parameters, and an info dialog should notify the user that the 
MI configuration parameters have been reset. 

For a more detailed explanation of how these values can vary, check chapter 18 
of the YAWL book

New feature:
- I think it's good if in the dialog of the MI configuration parameters we show 
another column with the current values of the MI parameters.

Original comment by marcello...@gmail.com on 10 Feb 2011 at 11:05