Locking and Checking in Frameless Skins using AzureDev Ops version control in RoboHelp 2020

[troyc61358404]

Is there a way to lock a Frameless Skin or other outputs similar to how you can lock content under the Author window? How exactly does RoboHelp 2020 maintain check in/check out status and version control priority if two people are working in the same project? There have been some issues with work being overwritten or not being saved properly between myself and another coworker.

[Peter Grainge]

I'm not a source control user but in the absence of any other answers...

I thought it was down to the version control software to control that. As I understand it, some software does apply a lock so that more than one user cannot work on a file, other software just warns. I can't speak for how Azure works and it may be an optional setting.

The skin is in the project folders so if you are checking everything in rather than just the topics,  that should put it under source control. How that works is a matter for the source control software, not RoboHelp.

I hope that is of some help. If not then try Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your support contact options.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information