Workflow
Attain is building workflows offering the following:

Process definition sharing: Work with process designs across multiple designers, enabling collaboration among business and technical users. Attain provides a unique modeling experience that supports multiple, interchangeable modeling canvases and tools. Attain ensures that the core process definition is the same, regardless of the canvas or tool used to model the process, by abstracting the view information from the process definition. The result is a solution platform that allows each participant in the process-modeling experience to use the environment that best suits their needs while enabling collaboration between participants using different environments.

Task wizards: Built-in wizards to configure standard task actions, like retrieving information from a user, sending e-mail or updating a back-end system. Attain provides an extensive toolset for building process-driven applications. The process designers provide the ability to use event wizards to provide specific functionality to a process. Event wizards for common tasks such as client interaction, integrating with SharePoint, sending email or integrating with forms technologies like InfoPath or .NET forms are available out of the box. The ability to kick-off other processes from within a process is also available.

E-mail notifications: Wizard-based template for sending process and business data via e-mail

Inter-process communication: Wizard-based template for starting or communicating with other processes running in the environment.

Actions and Outcomes: Allows process designers to separate what decisions, or Actions, users are able to perform and the results, or Outcomes, of those decisions. Attain provides the ability to build rules and policies that provide business logic to any process. Rules can be used to manage how tasks are started and finished, how a process flows from task to task, how tasks are assigned to users and even when tasks should be assigned based on working hours and time zones. Rules can also be used to determine if a task needs to be escalated due to an SLA or other business rule that has not been met. Rules used within a task or process can use any information available to the process, whether that information is entered via an InfoPath or .NET form or is line-of-business information. Attain also provides the ability to assign tasks based on roles. Roles can either be static, including a set list of users every time, or can be dynamic, pulling in users based on process data or other business logic. In addition, users have the ability to delegate or redirect tasks to users on an ad-hoc basis, making it easy to dynamically route tasks based on business needs that change on a regular basis without having to make changes to the process itself.

Process and Activity Data: Data fields that can be used within a process to store process-specific information

Business entity integration: Wizard-based integration with business entities to retrieve and update data in line-of-business systems

Object Browser: Tree-view control giving process designers access to configuration and environment information, process data

User Worklist: Provides a single location that displays all tasks assigned to a user

Business Process expertise

Competence to implement outside of systems

Robust performance

99,999% availability

Visualize current processes status during runtime

Business Process design, Roles, Directory integration, Actions, Rules, Resuable components