![]() ![]() Updates and improvements that we make could result in issues in future releases importing contact flows that are exported during the beta phase. The Flow Import/Export feature is currently in Beta status. To migrate tens or hundreds of flows, use the APIs described in Migrate flows to a different instance. ![]() If you want to keep using your offline data store as a source of truth, update the flow with the new format. After that, you can copy and paste within the updated flow designer. The importing process converts it to the new flow language. To copy a part of that flow and paste it into the updated flow designer, you need to import it into the updated flow designer. For example, for configuration control, you may have flow configurations in an offline data store. ![]() This option is most useful for scenarios where you have stored your flows in JSON offline. Option 2: Manually import the legacy flow using the updated flow designer. Your legacy flows are automatically converted. Option 1: In the flow designer user interface, opt in to the updated flow designer. To convert a legacy flow into the new format, you have two options: To copy and paste flows and blocks in the updated flow designer, the flow must be in the new flow language. Use the procedures described in this topic to import/export a flows from the previous flow designer to the new one, from one instance to another, or from one Region to another as you expand your customer service organization. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |