Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi All,
I am working on an Expense Reimbursement System POC in Appian.
We have three different user roles: Employee, Manager, and Finance Team, each with separate interfaces. I need to implement an AI chatbot in all three interfaces that can answer user questions based on claim data.
What is the best approach to design and integrate role-specific chatbots in Appian? Should each interface have a separate chatbot configuration, or can we reuse a single chatbot with dynamic context?
Also, how can we ensure the chatbot responds based on the logged-in user’s role and related data?
Thanks in advance.
Discussion posts and replies are publicly visible
Hi jananyi790908 ,as per your usecase, you can use a single record chat component and UI, and dynamically pass the inputs.I recommend to use record level security for the record type, ensures chatbot only givws output from which the loggedin user is a member of certain group.
Yes, we can give dynamic context using - Additional Instructions, parameter in the component configuration->Behaviour.FYI - Please check the relevant documentation - docs.appian.com/.../Records_Chat_Component.html
Use one reusable a!recordsChatField() with role-based record-level security on the Expense Claim Record Type and dynamic additionalInstructions per interface/role. No need for separate chatbot configurations unless each role needs completely different prompts or data sources.