We are planning to do concurrent development using two different Appian sites,

saravanana over 8 years ago

We are planning to do concurrent development using two different Appian sites, It looks like Appian playbook is not recommending to do concurrent development. Does anyone have best practices or processes to FOLLOW to make this concurrent development easier? Is there better option to merge code base and objects rather than manually redo changes and make it sites are in sync?

Discussion posts and replies are publicly visible

Parents

0 Tom Ryan
Appian Employee
over 8 years ago

In order to 'merge' onto a single QA site, you can still follow the standard practice of application imports/exports. You can use the deployment automation tool for this if you prefer. There should not be any issues with this as long as no naming conflicts are introduced. For syncing objects you can do the same.

That said, I still don't see what the advantage to this approach is, considering you will have the additional overheads of syncing objects etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Tom Ryan
Appian Employee
over 8 years ago

In order to 'merge' onto a single QA site, you can still follow the standard practice of application imports/exports. You can use the deployment automation tool for this if you prefer. There should not be any issues with this as long as no naming conflicts are introduced. For syncing objects you can do the same.

That said, I still don't see what the advantage to this approach is, considering you will have the additional overheads of syncing objects etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data