Found a small bug on the app.

When you add a new Configuration, change it and then remove it, that configuration will be stored if you do the update.

For example:

If you have one configuration, you add the second. Then you change the default to something else.

You then remove that configuration to stay like it was before and you do an update. Now you have 2 configurations stored.

Script: Script_RST_ResourcePool_EditParameters.xml

The issue can be solved on the UnassignCapability method. Same for UnassignCapacity and UnassignConfiguration.

model.GetAvailableCapabilities() just needs to be called once I think.