CASE PM-122543-19-202544:

Previously, in the ASMS Specialist, if a user changed the category of a case to a category of a different model without saving and reverted the selection to the original category to finally save, the system did not invoke the status service again when returning to the initial category. This resulted in a database inconsistency between the Model_ID of the original model and the intermediate model State_ID discarded, leaving the case in a crashed state and inoperable from the console. The issue most often arose when both models shared the same name for the initial state (for example, “Registered”), which prevented the interface from detecting the need to update the status ID when reverting to the original category.

Implemented a setting in the ASMS Specialist which ensures that each category change invokes the status service and correctly updates the State_ID corresponding to the active model. When saving the case, only the identifiers associated with the currently selected category persist in the system, eliminating the inconsistency between Model_ID and State_ID and regardless of the number of recategorizations performed before saving.