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
In my experience, this is not what the Appian platform is made for. While we can, to a certain degree, work around this, your might end up with a rather complicated and hard to maintain application.
But, maybe this is just the way you are used to do things in your existing software environment, and there is an easy way to achieve the same goals in a different way. Do you want to give us some background on what you want to achieve?
great points thank you for replying - Help me understand what is the motive of Appian platform and what key use cases it can support? is it only recommended to use for workflows?
IMHO, Appian is designed to automate the operations of larger end-to-end processes. This is much more than workflows.