I have a sink-NodeModel (with an attached NodeView) which is too complex to be made persistent using the load/saveInternals-mechanism. Currently, when saving an executed instance of this node and reloading the workflow, the node is still in the “executed” state, but the view-instantiation to fails.
Thus I would like my node to become reset automatically when a previously saved workflow is being loaded. This reset should affect only my node and not the complete workflow (so no “-reset”).
Is there any API or property to be set to cause the state of my node to change to “configured” when the workflow is loaded? Maybe some exception that I could throw in order to indicate that my node could not be restored even if it has been in “executed”-state when the workflow had been saved.
So far the only partial solution which came into my mind was to set a warning-message which indicates the user to reset the node.