feature/finished/IIA-2521: Set Default Values for Property Fields in Edit Panel for Concept FQN

[dukke]

Fixes: https://ikmdev.atlassian.net/browse/IIA-2521

---

This ticket also ended up fixing:

• A bug where if you fill out the form and leave the name for last the submit button will still be disabled even though you filled out everything.
• Grayd out prompt text in name textfield so that it doesn't look like an entered value
• Switch ComboBox types from using ConceptProxy to EntityFacade

[dukke]

@carldea did what you suggested and fixed another bug. So now besides fixing the ticket this PR is fixing:

• A bug where if you fill out the form and leave the name for last the submit button will still be disabled even though you filled out everything.
• Grayd out prompt text in name textfield so that it doesn't look like an entered value
• Switch ComboBox types from using ConceptProxy to EntityFacade

Thanks!

[carldea]

Can you use the State.ACTIVE instead of calling getFast()?

[dukke]

State is an enum. We can only get the nid and so we’ll need to do getFast

[carldea]

The statusComboBox items should contain all states as a State objects(enum). setValue(ACTIVE)
We should look at how we did this for the new StampAddController.java as it relates to the following:

• converter
• buttoncell
• cellfactory

[dukke]

@carldea
I was able to do the refactoring of the StampAddController and created the utility class like we discussed in the dev sync (also took the oportunity to correct some minor issues with the old code).

Regarding the FQN Controller and changing the combobox to use State instances, what I was afraid of ended up happening, unfortunately... when we change the ComboBox to have a collection of State objects rather than what we had, this change ends up trickling down to a bunch of other classes.
Let me explain, the AddFullyQualifiedNameController uses DescrNameViewModel which expects a ConceptEntity for the state. The DescrNameViewModel is then used in other name controller, edit FQN controller, edit other name controller, pattern controller, ConceptViewModel.

In conclusion if we change it to State, unfortunately we'll need to change in a lot of other places because it's all connected... With any change it will also bring with it the possibility of breaking Pattern and Concept editing/creation...
We might possibly want to create another ticket for this effort (using State enum for all these classes)?

[carldea]

Looks good!