Change Control is not a term you see used among FileMaker developers; in part, because it goes against many of the aspects of FileMaker that we all love.  However, data security concerns are leading to platform security concerns and to an increased demand from customers/clients that we document our Software Development Live Cycle and follow established Change Control policies.

 

Unfortunately, FileMaker ain't built that way.  There is no check-out/check-in of scripts, no logging of script edits, no code-compare features which highlight changes to a solution.

 

So, the Question is this:  What tools, tricks or techniques have folks found useful in trying to address the issue of Change Control and in documenting the Software Development Life Cycle?

 

Any suggestions would be greatly appreciated.

there are a few ways - using the DDR report you can use FMDiff to capture some changes - however they are broad changes and you it may be difficult to make comments on specifics 

 

Another thing some developers are employing is using GIT repository and storing the text of scripts or calculations there so that they can show changes over time. 

 

Keep an eye on https://www.geistinteractive.com/blog/    Todd will be blogging about at sometime in the near future.