-
Recently active
Hi everyone,I am looking for architectural and design recommendations for building a common Application Landing Page in Appian.The Setup:I am building this landing page within a separate, standalone "Common/Core" application. Because this is a centralized hub, I, as the developer, do not have design-time access to the downstream application groups. Furthermore, when new applications are deployed in the future, this landing page needs to automatically accommodate them without requiring code changes.Requirement:The landing page must display a dynamic list of applications. Crucially, an application should only be visible to the logged-in user if they belong to that specific application's personas/security groups. Because I cannot hardcode or directly reference these group objects, the solution must be fully data-driven or dynamically resolved.Questions for the community:What is the best-practice design pattern for this? Should we use a database-driven approach where applications register
Fabric データを取得する為の接続は、activedirectoryserviceprincipalを利用する。この時Service Seqret はKeyVaultより取得して動的に変更したい。Jdbc接続文字列を変更する方法は?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.