Asset Status' and substates

[Jim]

I'm not sure if this is a concern or not but in my asset update tool I've been doing some testing and I thought the issue was in my app (in most probably is an issue either way) but I noticed I can populate a substate with the wrong parent state. 

 

I looked on Hornbill directly and I can actually do it within the software also see images below, I can achieve this in the app by editing the 'State' not submitting it and then editing the substate which shows me the new values, I've looked at the entity viewer and it does say it's hard coded but was curious if this was an issue or an accidental feature? 

[Frank Reay]

I reckon this is a bug as I have the same problem but have just never raised it as such. I have written a report which runs each week that outputs any of these mismatches.  If we can get it fixed then that would be great.

[ArmandoDM]

Good fternoon @Jim  @Frank Reay

can you please provide some replication steps on how you achieve this, as we've not been able to replicate this issue.

Regards

Armando
 

[Jim]

Interesting after the update this morning I can not repeat the issue. Essentially you could edit the State in the summary view, but not commit the save and then the substate would show the new substates based on the new State that hasn't been commited yet, you could then change the substate to a different states child states and commit the save without ever committing the State change leaving it on the wrong value.

 

Hopefully that makes sense? but seems like it has been fixed now

[Frank Reay]

Mmm well I can still do it as described by Jim.

Basically I changed the State from Operational to Retired (I have used Translations to give me different label names) but did NOT click on the green tick. The Sub-state box is then empty but if I click on it I get the drop down for the new State of Retired (but the State box above defers back to the previous Operational). So I can save this combination which should not be allowed...

[ArmandoDM]

Good afternoon @Frank Reay

the issue has been identified and fixed.  It will be available with the next build

Regards

Armando