Configuration Methodology

Hi Appian Community - I am new to Appian and excited to use it for my use cases. 

I have searched in documentations and didn't find anything related to configuration management aspect of design what I meant is - if I am creating one application it will expose some feature flags, some configuration placeholders for end user customization. what is Appian recommendation, do you have any patterns with examples which newcomers can use as a reference?  What are do and don't in that area?

Also, base vs overrides configurations client wise - if your app is being used by multiple clients.

Please provide guidance.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    As Mathieu has mentioned there is no specific recommendation documented. But you can use the help of constant or even a database which would store these configurations. If you have a multi-tenant system, you can have the mappings based on these configuration types and the tenant type. This will allow the user to handle configurations. Also if you are implementing the configurations via db., I would recommend marking the configurations with a version stamp and creating a separate dB to store the previous version which will allow you a track of updates.

Reply
  • 0
    Certified Senior Developer

    As Mathieu has mentioned there is no specific recommendation documented. But you can use the help of constant or even a database which would store these configurations. If you have a multi-tenant system, you can have the mappings based on these configuration types and the tenant type. This will allow the user to handle configurations. Also if you are implementing the configurations via db., I would recommend marking the configurations with a version stamp and creating a separate dB to store the previous version which will allow you a track of updates.

Children
No Data