Why would you want to lock to a specific UI version? That is one way to make sure any custom component you may have in production does not have any potential conflicts with a new UI release, until you’ve had a chance to test the new release out.
- Create a new player (let’s call it UI2860) based on the Flow default player.
- Delete the <script src=”https://assets.manywho.com/js/loader.min.js”></script> line of code. This is Ln 173 in the image.
Note the line number; you will come back to this place to paste code!
- Open the Flow UI 2.86.0 version page. This gives us a list of vendor and versioned assets.
- Copy the Vendor Assets code block. Do not close the page yet; we will come back for the versioned assets code block in a bit!
- Remember the line of code you deleted? Paste this code right there.
- Let’s go back to the Flow UI 2.86.0 version page again.
- Copy the Versioned Assets code block.
- Paste the code under the vendor assets code block from you just copy-pasted.
- Almost done! Just one more copy-paste left! Okay, flex your muscles. Copy this code block:
- Paste this after the versioned assets code which you just pasted.
- Click Save to save the player.
Selecting this player when running your flow will load the UI 2.86.0 version at all times.
If you would like to try a different version, select the assets from that release. Keep in mind though, that vendor assets will always come before versioned assets for the magic to work!
The engineer who helped with this documentation is a math wizard, whose idea of light reading consists of cryptography, and mathematical biology. Magazines are for children!