Documentation Center

Changing a Quality Model while Tasks Are Active

While the primary review use case would have the quality model agreed upon and locked down before a project is created, in some situations it might be very useful to change the quality model while it is in use. For example, it is possible that during the review cycle, you realize that there was a missing error type that needs to be added to the model. WorldServer allow a quality model to be changed while in use. The changes will have the following effects:
  • In the Browser Workbench, any change takes effect immediately. The next time a user tries to report an error the new settings become available.
  • In desktop translation tools, the change is not immediately visible. The user has to re-export a kit from WorldServer to get the updated model definition.
  • When an existing value is deleted or changed, the change has no effect on the existing errors reported before the change. The severities and error types recorded for those errors do not change unless a user updates the error definition. If a user attempts to modify a segment that uses an error type or error severity that is no longer available, an error message is displayed forcing the user to select a new valid definition.
Changing a quality model while affected tasks are active should be discouraged. Generally, the quality model should be finalized before projects are created.