Siebel IP17 Testing locally

Apparently Siebel IP17 has some problem for testing development related changes on local environment before pushing it to the server. Development related changes cannot be tested locally on the workspace also known as sandbox in IP17 but changes cannot be seen made in the objects until workspace get submitted and delivered the respository.

As per bookshelf, below are the steps to test changes/modifications locally:

1. Create a workspace 
2. Edit objects for example update the Applet control caption 
3. Checkpoint/versioned the workspace ( i suppose this is optional step) 
4. Modify the corresponding CFG file say "publicsector.cfg" cfg file as below: 

[Workspace]
Name = Main
Version = 41 -- The version of the workspace for which you wanted to test the changes

[InfraObjMgr]
RequestServerName = <SERVER_NAME>
RepositoryType = RUNTIME 

      5. Start thick client (dedicated client) to view the changes

You can even try mentioning your own workspace name like:

[Workspace]
Name = dev_umer_fieldupdate1
Version = 01

[InfraObjMgr]
RequestServerName = <SERVER_NAME>
RepositoryType = RUNTIME

But in this case it even would not let you log in.

Similarly, in the thin/thick client it is not possible to edit/view Workspace changes by opening Workspace directly, there is no hammer icon anywhere.