Can I check the history of working on a file in Framemaker. To see who worked on a file and when?
Maybe there is some way, like in the inDesigne program.
FM has a limited Undo and Undo History feature, but is not the complete edit history of the file, nor does it show authorship. I wasn't quickly able to determine what cause the history to be discarded.
Traditionally, entities that needed that level of content journaling would store the files in a CMS (Content Management System), and recent versions of FM have much more fluid support for doing so.
Thanks Bob for you answer.
Is it possible to extract information such as the author or the date of creation of the file from the log file? If so, where to look for it?
Ireneusz.Pogroszewski: Is it possible to extract information such as the author or the date of creation of the file from the log file?
What log file?
Recent versions of FM (such as for FM2019) create a console message file:
but it is only for alerts and errors.
I'm not aware of any other log files, and specifically not any containing the information you want. The lack of it is why people have used CMS systems for stewardship of FM documents.
As Bob Suggested m Version controlling can be done via CMS, FrameMaker has very seamless integration with various CMS like SharePoint, Documentum, and especially with AEM.
Further, you can also use the "Track Text Edit " feature in FrameMaker to track edits done on your source file by Various authors.
Ref: Track Text Edit
pulkitn: … you can also use the "Track Text Edit " feature …
Thanks for mentioning that. Although it's been available for a decade or more, I've never used it. It seems to be geared toward management of a single review cycle of a book or document, and is not likely to be suitable as a long term journal of changes.
For example, it doesn't track everything. See Tracked and untracked text edits: Examples in the FM Help.
The changes are also apparently stored in the file, as conditional expressions, so would explode the file size over the life of the document (whereas, in a CMS, that overhead is in the database, and not the served instance of the document).