How To Retain Folder Structure In Check-Ins And Groups

How do you keep the folder structure when checking in folders/flows? Can groups be checked in as well? How can we account for hotfixes, and we want to develop while there's an issue on production?
Comments
-
In order to include a folder in every check in and retain its folder structure (with flows and objects that are part of different projects), you'll need to include the top-level folder in a common project. You can do the same thing for groups to include them in check-ins. Accounts are unable to be migrated, however the SAML login flow creates accounts for users, so this is a workaround. Our recommendation for the hotfix process (what to do when there's an issue in prod, but you're still developing so you want to branch with the fix) is as follows:
- Make change on prod, export flow/item
- Make a backup of dev flow/item
- Import change into dev
- Check in to repo/out on other environments.
- Reimport dev backup and make appropriate change that was made in the flow in the first step
Howdy, Stranger!
Categories
- 4.4K All Categories
- 86 General
- 13 Training
- 212 Installation / Setup
- 1.2K Flows
- 111 Rules
- 282 Administration
- 216 Portal
- 500 General Q & A
- 718 Forms
- 353 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 188 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 70 Repository
- 233 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 27 Active Directory
- 12 Version 7
- 36 Version 8
- 143 Lunch And Learn Questions