You are here: User Topics by Subject > Using Optional Advanced Features > Working with Localization Workflow > Localization Workflow Overview

Localization Workflow Overview

Localization Workflow is a powerful feature that enables the following functionality:

Sample Localization Scenarios

The following are some sample scenarios for when this feature can be especially useful.

Other Sample Scenarios

Centralized tracking of reader status: The compliance officer of a large corporation distributes copies of an evacuation procedure document to each building at the corporate headquarters campus. The document includes a questionnaire that assigned readers must successfully complete in order to mark the document as read. The compliance officer asks the owner of each site copy to replace the graphic of the main building floor plan with its building floor plan. She also needs to track who has read the evacuation procedure, including the master document and all site copies, and wants to periodically generate a questionnaire results report that includes all readers.

Automatic assignment of readers to translated copies: The director of human resources creates a harassment policy document in English and creates copies of the document that he sends out to an agency for translation into the company's five official languages. He needs to assign all users at all company sites to read the document in their preferred language (which may or may not be the same as the site's default language).

Typical Localization Workflow Process

The Localization Workflow process can consist of the following high-level steps:

Set Up

  1. Your organization buys the Localization Workflow module and a document control administrator (DCA) enables it in PolicyTech.
  2. The DCA creates a template with Localization Workflow enabled.

Use

  1. A document owner creates a master document using the enabled template and sets the document's publication date to some time in the future that is estimated to be after all localized copies of the master document will be completed.
  2. In the Properties Wizard of the master document, the owner adds localized copies by providing a title and selecting a document owner, template, site, and language for each copy. These copies reside in predraft status until the master document is approved.
  3. The master document owner opens each localized copy and sets the same publication date as the master document.
  4. The document owner submits the master document for review and approval.
  5. When the master document is approved and moved to pending status (because of the postdated publication), the localization copies are moved into draft status within their assigned sites and the copy document owners are notified. The assigned document owners then work on the copies by translating them or modifying them as appropriate for their local readers.

The assigned document owners submit the copy documents independently for local review and approval. Assuming that each of the copy documents is approved before the synced publication date, each copy moves into pending status.

  1. When the assigned publication date arrives, the master and all copy documents currently in pending status are published, and notifications are sent to all users required to read the documents.