Situations arise during development where dependencies have been taken on a service instance, but a need arises to be able to delete the service instance and re-register it, but maintain the bindings to smart objects.

Since this binding is done based on the GUID of the service instance, the GUID for new service instances (in the case of a re-registration) needs to a value that could be provided. This would bring management closer to feature parity with the Service Object Tester Tool and would afford the K2 developer more options when trying to mitigate problems.

This is even more important as K2 transitions more into a cloud model where the options for self service support/troubleshooting are even more limited.