<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Use Cases on SWS - Unlock Your PeopleSoft Data for AI, Modern Apps, and Integrations</title><link>https://sws.books.cedarhillsgroup.com/tags/use-cases/</link><description>Recent content in Use Cases on SWS - Unlock Your PeopleSoft Data for AI, Modern Apps, and Integrations</description><generator>Hugo</generator><language>en</language><atom:link href="https://sws.books.cedarhillsgroup.com/tags/use-cases/index.xml" rel="self" type="application/rss+xml"/><item><title>Use Cases</title><link>https://sws.books.cedarhillsgroup.com/docs/use-cases/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://sws.books.cedarhillsgroup.com/docs/use-cases/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;If you are evaluating SWS for a specific scenario and do not see it covered here, &lt;a href="https://www.cedarhillsgroup.com/about-us/contact-us/"&gt;contact Chris Malek&lt;/a&gt; — we likely have a pattern for it.&lt;/p&gt;</description></item></channel></rss>