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.2K All Categories
- 67 General
- 11 Training
- 202 Installation / Setup
- 1.1K Flows
- 106 Rules
- 262 Administration
- 212 Portal
- 491 General Q & A
- 695 Forms
- 333 Reports
- 3 Designer Extensions
- 47 Example Flows
- 52 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 179 Pages
- 5 Process Mining
- New Features
- 179 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 78 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 83 Lunch And Learn Questions