Solved: TWX Experience/Project Folder Management

bwhelan · ‎Feb 23, 2018

Hi all,

Just putting out a generic question to PTC and Users alike for comment: How are Users currently managing their TWX Studio published and locally stored Project files/folders? Is there currently a "Best practice" or recommended option that is used to manage both current and more historic project folders?

I'm thinking here about revision control and reverting to previous know-to-be-working projects should current projects go wrong/bad?

Any viable suggestions are welcome!

Regards,

Brian

dupatel · ‎Feb 23, 2018

@bwhelan I believe we do not have this documented currently however one way would be to take backup of local project under \Users\<UserName>\Documents\ThingWorxStudio\Projects\<ProjectName> before making changes and publishing them to Experience Server(ES).

Other option is to some Version Management utility or GitHub in which before making any changes to published project one should get a pull of latest changes from ES to work on. Then make the changes in project and push it back to the ES which can create new branches or version with details in description of the changes.

Currently, we only maintain the latest changes both locally and which is published on ES without tracking history of changes.So, basically you can maintain the project changes by keeping copy of Project Folder with versioning in a central repository. Before making any changes get the latest version of project from the repository and work again.

Hope it helps.

-Durgesh

View solution in original post

dupatel · ‎Feb 23, 2018

@bwhelan I believe we do not have this documented currently however one way would be to take backup of local project under \Users\<UserName>\Documents\ThingWorxStudio\Projects\<ProjectName> before making changes and publishing them to Experience Server(ES).

Other option is to some Version Management utility or GitHub in which before making any changes to published project one should get a pull of latest changes from ES to work on. Then make the changes in project and push it back to the ES which can create new branches or version with details in description of the changes.

Currently, we only maintain the latest changes both locally and which is published on ES without tracking history of changes.So, basically you can maintain the project changes by keeping copy of Project Folder with versioning in a central repository. Before making any changes get the latest version of project from the repository and work again.

Hope it helps.

-Durgesh

bwhelan · ‎Feb 23, 2018

Hi Durgesh,

Many thanks for the feedback. So I guess for now it is down to the individual to keep track of revisions and backups of projects? The problems may arise, though, where more than one individual may be working on one particular project... it could be hard to track revisions in these instances...

Food for thought Durgesh but many thanks for the reply!

Regards,

Brian

dupatel · ‎Feb 23, 2018

@bwhelan Agree Brian and we understand that the current Studio setup do not support multi tenancy in a better way. This is something we are trying to improve in our future releases.

-Durgesh