<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>App Atlas (AI-powered Appian reverse-engineering)</title><link>/b/appmarket/posts/app-atlas-ai-powered-appian-reverse-engineering</link><description>Overview
In many Appian implementations, documentation is often incomplete, outdated, or scattered across multiple repositories. When new teams, vendors, or support engineers take ownership of an existing application, they spend weeks understanding t</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator></channel></rss>