Flow of type “Screen flow” changes to “Autolaunced flow” when deployed via MD API
Last updated 2020-02-15 ·Reference W-6587230 ·Reported By 22 users
Flow of type “Screen flow” changes to “Autolaunced flow” when deployed via MD API. This ONLY happens on a screen flow that doesn't contain a screen element. If you have a screen in flow 1 of the repro steps then it works fine.
This issue can be reproduced in any fresh org following the below repro steps:
1. Create two flows with the following specifications;
> Type: Screen flow
> Components: Contains Start element and a Subflow element which references Flow 2.
> Type: Autolaunced Flow
> Components: Contains Start element and a simple variable text assignment element.
2. Retrieve the metadata for these flows through MD API using workbench/ANT.
3. Re-deploy the flows back to the org - observe that the flow type for “Flow 1” is changed to “Autolaunched”
Type for flow 1 is changed to “Autolaunched”
Type for flow 1 should remain set to “Screen Flow”
Reported By (22)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.