I've seen some crazy process flows in SAS Enterprise Guide. Crazy-big, and crazy-complex, used by real customers to accomplish real work. But while these process flows represent a ton of work, this is usually a calculated investment to automate processes that would be difficult to capture in another way. For
Two popular SAS custom tasks have recently been updated for SAS Enterprise Guide 7.1. Most custom tasks that I've shared will work without modification across releases, but these two required a special rebuild due to some internal product API changes. The Project Reviewer task allows you to see a detail
SAS users, by definition, do not embrace the mysterious. That's one of the main reasons that they use SAS: to demystify some data or process. And so, when you (as a SAS user) have gone to the trouble of designing a process flow in SAS Enterprise Guide, you like to
What is the best way to organize your SAS work in a SAS Enterprise Guide project? There are no project templates or enforced structure, really, but isn't there a best practice? I don't have a single prescription for the best project organization. I believe that it depends on the nature
