Development Guidance With Multiple Teams
I currently have multiple teams developing within Decisions locally. These teams will then import their respective projects to our single DEV environment. At times, teams will work on the same project at the same time. This causes a lot of wasted resources because the teams need to coordinate with one another.
Is there a better process for this? Do you have any recommendations?
Comments
-
The best advice I can give is to avoid developers working on projects simultaneously. There is a feature within Decisions to deter users from building on the same entity Object is Locked. This is an indication that a user currently has that entity open.
If you are unable to prevent concurrent development, I would suggest using the Decisions Repository. This will give you the option to rollback or revert to previous versions of a project. Overall, this instance will aid in managing projects, serving as checkpoint between DEV and QA and/or PROD. Projects can be pulled or pushed in either direction at any notice.
Howdy, Stranger!
Categories
- 4.3K All Categories
- 70 General
- 11 Training
- 206 Installation / Setup
- 1.1K Flows
- 109 Rules
- 268 Administration
- 212 Portal
- 496 General Q & A
- 708 Forms
- 338 Reports
- 3 Designer Extensions
- 48 Example Flows
- 56 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 184 Pages
- 5 Process Mining
- New Features
- 182 Datastructures
- 69 Repository
- 228 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 57 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 130 Lunch And Learn Questions