---
schema_version: "1"
id: 412523dae30919db26ed0066a20ac4cdc30d9e8a3b4cab861dc9a61c69ce9401
title: FlowDefinition
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_flowdefinition.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_flowdefinition.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: bf1740c7c137faf47e4399f19221a72ae0914233bd06502a608006d7733d5ba8
description: Represents the flow definition’s description and active flow version number.
---
# FlowDefinition

Represents the flow definition’s description and active flow version number.

![Important](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note_important.png)

#### Important

Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

![Important](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note_important.png)

#### Important

In API version 44.0, we recommend upgrading your flows to flow metadata file names without version numbers and discontinue using the FlowDefinition object to activate or deactivate a flow. Then use the Flow object to activate or deactivate a flow. For more information, see [Upgrade Flow Files to API Version 44.0](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_visual_workflow.htm#md_flow_upgrade).

If you deploy with flow definitions, the active version numbers in the flow definitions override the status fields in the flows. For example, the active version number in the flow definition is version 3, and the latest version of the flow is version 4 with the status field as Active. After you deploy your flow, the active version is version 3.

## Declarative Metadata File Suffix and Directory Location

FlowDefinitions are stored in the flowDefinitions directory of the corresponding package directory. The file name matches the flow definition's unique full name, and the extension is .flowDefinition.

## Version

[FlowDefinition](#meta_flowdefinition "Represents the flow definition’s description and active flow version number.") is available in API version 34.0 and later.

| Field Name | Field Type | Description |
| --- | --- | --- |
| activeVersionNumber | int | The version number of the active flow. |
| apiVersion | int | Reserved for internal use. |
| description | string | Description of the flow definition. |
| masterLabel | string | Label for the flow definition. In managed packages, this field inherits the flow’s active version name. To change this label from a subscriber’s org, edit the packaged flow name. |

## Wildcard Support in the Manifest File

This metadata type supports the wildcard character \* (asterisk) in the package.xml manifest file. For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).