We are running into issues with our development practices in our Appian environm

helmuta over 10 years ago

We are running into issues with our development practices in our Appian environments. We are using development, test and production. Just recently we promoted an application to production and started modifying the same application in our development environment. We found an issue in production and since our development environment was in flux we went to test and made a correction and promoted the fix to production. Now we had to go back and retro fit or modifications to development so we would not loose our production fix.

Just recently we had two developers wanting to make modifications to the same application. One was a quick modification and the other was a longer running modification. Since the second required modifications to the cdt, data store and db structure we put it on hold until the first project was completed. This seems like a poor method for continuing to improve the process.

How have other people addressed this problem? In ...

Discussion posts and replies are publicly visible

Parents

0 Medhat Galal
Appian Employee
over 10 years ago

Technically affects the integrity of the model, just like two IDEs accessing the same Java file. Hence, the model is actually locked upon opening by the first designer. However, if the intention is to have two contained process functions need to be developed jointly, a sub-process can be created for each and then each developer can work within their respective area.

Is there a specific reason to have two designers work in the same model beyond the use case I mentioned?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Medhat Galal
Appian Employee
over 10 years ago

Technically affects the integrity of the model, just like two IDEs accessing the same Java file. Hence, the model is actually locked upon opening by the first designer. However, if the intention is to have two contained process functions need to be developed jointly, a sub-process can be created for each and then each developer can work within their respective area.

Is there a specific reason to have two designers work in the same model beyond the use case I mentioned?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data