Most Gateway functionality is implemented as workflows. A workflow is essentially a self-contained feature or process that implements a specific piece of functionality, such as generating reports, configuring security policies, or even adding a user to a user group. Gateway administrators can restrict specific workflows (and their associated UI) to specific user groups.
Workflows typically have an associated user interface (UI), displayed as pages in Gateway. Other workflows exist entirely behind the scenes, such as those that run an automated security or caching policy. (You usually only need to work with those if you're a custom workflow developer.) All workflows include scripts that actually implement their functionality.
Administrative workflows implement core Gateway functionality, such as configuring preferences, setting up user groups, managing permissions, and more. You can restrict access to these workflows, but can't otherwise modify them or their scripts.
Custom workflows are either workflows that you or someone at your organization creates, or BlueCat adaptive apps and plugins that run on the Gateway platform. Adaptive apps extend the functionality of Gateway with additional features and functionality. Custom-built workflows are sometimes proprietary tools, specific to their environment and the needs of the organization. Development of a custom workflow typically requires significant coding and scripting effort.
About Adaptive Applications: BlueCat Gateway Adaptive Applications are plug-ins and applications built on the Gateway platform. These applications provide specialized features and functionality. If you're using a Gateway adaptive app or plug-in, that app or plug-in will appear as a custom workflow (or series of custom workflows). For details on using an adaptive app, see its online guide in the BlueCat Product Documentation portal.