Interview with Kevin Dietz, Timpani Software, docbook for small teams

This week’s podcast features Kevin Dietz from Timpani Software. Timpani Software develops BuildBeat, a comprehensive automated software build management system, and MergeMagician, an automated merging server designed to work with your existing software configuration management (SCM) system.

It’s my pleasure to present Kevin Dietz so he can share his experience with dynamic publishing systems and the reasons for moving away from traditional publishing tools. Figuring out how to move from proprietary authoring tools to DocBook not only freed his content, but inspired a new product line for Timpani Software.


Interview with Chris Western, tformat and APP World

This week’s podcast features Chris Western from tformat. tformat is a PTC partner focused on the Arbortext Advanced Print Publisher (APP) (formerly known as 3B2).  Chris was hired at Advent, the original developers of 3B2 as a writer to document the product and it’s usage. In his tenure, he not only developed the product documentation but training materials as well. Since then, he has specialized in training on APP (3B2)

APP takes such a different approach, training is critical to develop stylesheets effectively and well.  When done well, APP development can be deployed as a lights out solution for the most difficult automated publishing tasks. APP is the publishing engine you turn to when you can’t achieve what you want to do anywhere else. It’s an extremely powerful product. Continue reading “Interview with Chris Western, tformat and APP World”

Common Questions: Workflow

Highlights of Workflow features supported in Arbortext Content Manager

This week’s topic: Workflow

Here are some highlights of Workflow features supported in Windchill:

Arbortext Content Manager supports standard workflows as well as sophisticated capabilities for routing change information to the correct process participants. Arbortext Content Manager provides tools to support the creation of processes that are unique or dictated by industry-specific standards.

Because document components share common security properties, permissions and workflows vary based on the version and lifecycle of the document. Content changes are tracked and traceable to the individual user who initiated them

Powerful configuration and workflow management capabilities enable users to choose whether to manage each component individually or manage entire documents with a single workflow.

The ability to “burst” Arbortext-authored documents into document components within Windchill, which enables configuration and lifecycle management, including check in, check out, revise, promote, and workflow capabilities, at both the component and document “assembly” level.

The ability to implement workflow-driven process automation to speed document review and approval, optimize change management, and deliver audience-specific publications in the appropriate format

Today, we’re answering some of the more common and general questions about Workflow support in Arbortext Content Manager. As always, if you have a question that we haven’t answered or if you want more details, remember to send us your questions or add them to the comments!

Question: GUI for Workflow

Does ACM have a graphical representation of the workflow?



Question: Automating output production

Can you automate the generation of deliverables by using a workflow?



Question: Translated content workflows

Can translated content be integrated into the workflow process?



Question: Creating outputs

Can a writer produce his or her own deliverables, including language-specific deliverables?



Question: Updating workflows

Can you update workflows on the fly?


There is an “Instance of a Workflow” and a “Template of a Workflow”. Changing the Template does not change any Instances currently running.

Question: Changing completed workflows

If content is being processed through a workflow that has changed and the change affects a process that has already been completed, does the process remain unchanged?


It depends on what you’ve specified should happen in this case

Question: Changing in-process workflows

On the other hand, if the content has not yet reached that point in the process, does the contents then get processed using the new workflow automatically?


It depends on what you’ve specified should happen at any point in the workflow (each case)