https://sws.books.cedarhillsgroup.com/categories/use-cases/Recent content in Use Cases on SWS - Unlock Your PeopleSoft Data for AI, Modern Apps, and IntegrationsHugoenhttps://sws.books.cedarhillsgroup.com/docs/use-cases/ai-agents/Mon, 01 Jan 0001 00:00:00 +0000https://sws.books.cedarhillsgroup.com/docs/use-cases/ai-agents/<p>AI agents, chatbots, and Retrieval-Augmented Generation (RAG) pipelines need clean, structured data from systems of record. PeopleSoft is the system of record, but the path from PeopleSoft data to an LLM-friendly response normally goes through a development project — gather requirements, write a bespoke web service, migrate the code, encode the response, ship it. By the time the agent team gets the data, the prompt has moved on.</p> <p>SWS shortcuts that loop. The data layer becomes configuration, and the agent team can iterate without an Application Designer migration for every change.</p>https://sws.books.cedarhillsgroup.com/docs/use-cases/Mon, 01 Jan 0001 00:00:00 +0000https://sws.books.cedarhillsgroup.com/docs/use-cases/<p>SWS sits between PeopleSoft and the systems that need PeopleSoft data. The pages in this section document specific patterns we have seen work well in production — what the architecture looks like, which SWS features make it possible, and the trade-offs to plan around.</p> <p>If you are evaluating SWS for a specific scenario and do not see it covered here, <a href="https://www.cedarhillsgroup.com/about-us/contact-us/">contact Chris Malek</a> — we likely have a pattern for it.</p>