I figured there had to be some posts on this be but I could not find anything of relevance when searching.
We are currently are in a the process of implementing Citrix and rolling out the client for user access, we grew out of Web. But moving to the client based system leads to some issues/questions that I have mulling over, the biggest one for is right now is:
Since they will now be able to save versions of the templates locally what strategies are there for making sure that users are at least informed that their saved version is out of date? I was leaning to a version number cube that the sheets would check back in with and display a message if the version numbers did not match up. Has anyone else used something that has worked better.
Version Control - Moving From Web to Client
- George Regateiro
- MVP
- Posts: 326
- Joined: Fri May 16, 2008 3:35 pm
- OLAP Product: TM1
- Version: 10.1.1
- Excel Version: 2007 SP3
- Location: Tampa FL USA
- Steve Rowe
- Site Admin
- Posts: 2456
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Version Control - Moving From Web to Client
Hi George,
Your approach seems practical.
An alternative that I have used in the past is for the books that I care about is to protect them and make them read-only. This give you greater control on versioning etc and since they are using Citirx they will be opening files from a common location. It's a bit restrictive on users though....
Cheers
Your approach seems practical.
An alternative that I have used in the past is for the books that I care about is to protect them and make them read-only. This give you greater control on versioning etc and since they are using Citirx they will be opening files from a common location. It's a bit restrictive on users though....
Cheers
Technical Director
www.infocat.co.uk
www.infocat.co.uk