---
schema_version: "1"
id: 0b642349338f9328cc543a0b38278c9452ab5a13bed114f1c9f5f075b13e4401
title: Expose the Flow Runtime Version to Custom Screen Components
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_automate_flow_builder_expose_runtime_api_version.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_automate_flow_builder_expose_runtime_api_version.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 603d54b1056e87891dd975ed2e37ac4e8cff964c4fe7db9492e2377239a992ee
description: Control how your custom component for screen flows acts based on the flow runtime version with the new flowRole attribute. In your Lightning web component, create a property that has the attribute flowRole="flowRuntimeApiVersion". Then use the value of that property at runtime to execute conditional logic. Retain functionality in older flows while incorporating newer features in the same component.
products:
  - Cross Cloud
release: "262"
---
# Expose the Flow Runtime Version to Custom Screen Components

Control how your custom component for screen flows acts based on the flow runtime version with the new `flowRole` attribute. In your Lightning web component, create a property that has the attribute `flowRole="flowRuntimeApiVersion"`. Then use the value of that property at runtime to execute conditional logic. Retain functionality in older flows while incorporating newer features in the same component.

**How:** Add the `<property>` tag as a child of the `<targetConfig targets="lightning__FlowScreen">` tag. The `<property>` tag must include these attributes: a `name` of your choosing, `flowRole="flowRuntimeApiVersion"`, `type="double"`, and `role="inputOnly"`.

```
<targetConfig targets="lightning__FlowScreen">

    <property name="prop1" flowRole="flowRuntimeApiVersion" type="double" role="inputOnly" />
    
</targetConfig>
```