Thanks for the questions. I'm including some responses below
Yes, it should have triggered a sync. There could be several reasons if it didn't. First, check the status of all services (the PLM 360 Sync and the Job Server). If they are both running, try to restart the PLM 360 Sync service. If everything is set up properly, try to wait a little longer. When you installed the sync service you were asked to choose the 'Wait Time'. Data only loads to PLM 360 in intervals of that 'Wait Time'
The reason for this is due to dependencies on other services that may not be running yet. Setting the service to 'Automatic (Delayed Start)' can help solve this problem.
WIth the first release of the PLM 360 Sync tool there will not be an option to sync DWF files. WIth future releases we expect to allow you to include the visualization file association with the item in Vault as an attachment to the item in PLM.
I do not expect that we will have a bi-directionali integration working with Vault 2013. For future releases, we will likely have additional capabilities in this area but it is highly dependant on the use case you have in mind. In general, our thought process is that each system will 'master' its own data and the Sync tool will allow a user in each system to reference data from the other system.
Regarding your first bullet point, what did you do to get from Released to WIP in Vault? Did you do a rollback then re-release? In other words, you released the same revision twice?
The problem with re-releasing an item in Vault is that PLM 360 doesn't have a rollback feature. So the rollback doesn't propagate to PLM 360. When you release the Vault item the second time, the sync tool thinks PLM 360 is up to date because it has the item revision from the first sync.
Here is something to try. Move the Vault item to obsolete and wait for it to sync to PLM 360. After the PLM 360 item goes to obsolete, move the Vault item back to WIP, make your edits and re-release. PLM 360 should then move back to Released with the proper updates.