ActualFiniteState Kind is being reset to "Mandatory" when adding new Possible States

[stepjah]

Prerequisites

• [x] I have written a descriptive issue title
• [x] I have verified that I am running the latest version of the COMET-IME
• [x] I have searched open and closed issues to ensure it has not already been reported

Description

When adding / changing(?) Possible States, the previously defined respective ActualFiniteState Kind is not persisted properly but reset to MANDATORY leading to manual re-work and issues in the Parameter-to-State-Mapper

Steps to Reproduce

Logs

• [x] There are no logs regarding the issue
• { ] I have attached a log file or included the relevant section in this issue

System Configuration

• COMET version:
  • [x] COMET-IME: 10.1.1.1
  • [ ] Other:
• Web Services:
  • [x] CDP4/COMET Web Services version: 7.0.6.0
  • [ ] OCDT WSP version:
• Environment (Operating system, version and so on):
  • [x] Microsoft Excel (32/64 bit): 32
  • [x] Windows OS (32/64 bit): 64
  • [ ] Additional information:

[stepjah]

This issue is still there for COMET-IME 9.5.0 and Webservice 7.2.0.0

[stepjah]

@samatstariongroup @lxatstariongroup Can you please have a look here and see if there is a potential fix for this in an upcoming version? It is a quite frustrating and difficult to explain to the users that if you have >20 ActualFiniteStates and once you need to add another, you need to (from the top of your head) replicate the MANDATORY / FORBIDDEN properties for all of them...