Workflow configuration files

bmanifest_status.xml

Defines the workflow of build manifests.

This file is intended for administrators with advanced technical skills.

container_status.xml

If you have DRM, this file defines the workflow of containers, which are objects distinct from Product, Release, and Version.

This file is intended for administrators with advanced technical skills.

image_status.xml

Defines the workflow of images.

This file is intended for administrators with advanced technical skills.

lockActions.xml

Determines what non-user-initiated actions should lock objects (such as the system-initiated status change from tb translated to in translation when a localization kit is created).

This file is intended for administrators with advanced technical skills.

map_status.xml

Defines the workflow of maps.

This file is intended for administrators with advanced technical skills.

product_status.xml

If you have DRM, this file defines the workflow of products.

project_status.xml

This file is intended for administrators with advanced technical skills.

release_status.xlm

If you have DRM, this file defines the workflow of releases.

This file is intended for administrators with advanced technical skills.

resource_status.xml

Defines the workflow of resources.

This file is intended for administrators with advanced technical skills.

snapshot_status.xml

Defines the workflow of snapshots.

This file is intended for administrators with advanced technical skills.

topic_status.xml

Defines the workflow of topics.

This file is intended for administrators with advanced technical skills.

triggers.xml

Determines what actions occur automatically on objects when they are released or change status (works with xpathforids.xml, locidclasses.xml, RemoveProcInsTriggers.xml).

This file is intended for administrators with advanced technical skills.

See Create new trigger code.

version_status.xml

If you have DRM, this file defines the workflow of versions.