When editing an Importomatic node, a change that would result in the Asset ID resolving a different version is not reflected in the Resolved Versions field of the Parameters tab, when flushing caches.
Steps to reproduce:
Set KATANA_RESOURCES environment variable to point at the plugins/Resources/Examples directory within the root of the KATANA install. This contains the MockAsset python plug-in that will be needed in the following reproduction steps.
Download and extract the attached assets.tar.gz into your system's default temporary file directory (the MockAsset plugin makes use of Python's tempfile.gettempdir() as a base directory of the asset database). For example, on Linux this will typically be /tmp. This tarball contains a simplified asset database that the MockAsset plugin will understand.
Launch KATANA and open the attached simple_asset.katana. This is a simple katana project file that has the PyMockAsset set as the asset plug-in, and an Importomatic node set up to point to the latest version of the asset found in the simple asset database that you've downloaded in the assets.tar file.
Edit the Importomatic node, and note that in a Parameters tab the version if the Elephant asset is set to "latest", which resolves to "3" in the Resolved Version column.
In a file browser or shell, navigate to the simple database's location on disk. Under the TestShow/TestShot/Elephant directory, duplicate the version 2/ directory and increment the version to 3/, to emulate a new asset version publish (i.e. copy 2/ to 3/).
Back in KATANA, Flush Caches.
Expected behaviour:
The Resolved Version field updates to show "3", which is now the latest version on disk.
Actual behaviour:
The Resolved Version field remains at version "2".
Workaround:
Edit another node, then edit the Importomatic once more. The Resolved Version field will have now updated correctly.