Symantec Workflow – it is a graphical .NET platform for designing and creating process applications and their forms. Using its tools and advanced logic, you can edit and implement both standard, pre-defined processes and construct your own.
Being primarily a platform intended for construction of security-related processes, it can also be used to automate the organisation’s business processes as well, which enables better control and shortening the time to perform tasks, at the same time reducing the amount of work and tasks through automation.
Symantec Workflow enables creating processes that integrate other Symantec tools or systems into unique business processes of the given organisation. As a process platform, it also enables creating processes that require employee interaction (e.g. decisions), or ones intended exclusively for humans and supporting their work (e.g. document flows).
In addition to the basic process automation capabilities, the Symantec Workflow solution contains a website (Process Manager) designed for managing various parts of business processes, such as tasks, documents, data, etc. The Process Manager website is the main user panel (in Forms and Workflow processes) and can be additionally integrated with Active Directory for the purposes of user authentication, management and appropriate access control. The Process Manager website also provides broad customisation options, e.g. by changing pages, symbols, web parts, etc., which enables preparing an interface optimally adjusted to the user’s needs.
Applications created on the Symantec Workflow platform can contain various interfaces for user interactions, from e-mails, to web forms, to devices (e.g. handhelds) or simple task lists. When creating new processes, you can decide what type of process it is going to be, if it is going to require user interactions and through what interface, or create a fully automated process operating in the background. Processes are created in the working area of a graphic designer containing a hierarchical design tree, toolbars and available components.
• Decision-Only – processes fully utilising the platform’s logic capabilities, but without the need for user interactions, although they are possible as well. Projects of this type are most commonly created for interactions with back-end systems, data processing or automating decisions based on defined business principles. Decision-Only processes are characterised by high efficiency and can be run as web services or DLLs. This enables developers of other applications to use these projects as components for their applications.
• Workflow – these are processes requiring user interactions, usually task-based. These processes move to further stages based and depending on decisions taken by users. Tasks generated in such processes are assigned to users, and subsequently the process awaits their completion or takes a defined action if the task wait time is too long. Workflow projects have extensive capabilities and are excellent for complex processes, for example document flows, various types of acceptance, e.g. by superiors or appropriate departments. Aside from user interactions, interactions with other systems are possible as well.
• Forms – it is the ideal type for projects requiring user interactions, often individual ones (as with applications not based on tasks, e.g. conference room booking management, sales representative activity reporting, etc.). When creating processes of this type, you can decide if they are going to be available only as web forms, or also – or exclusively – for mobile devices. If web forms are chose, the project creates an ASPX application that can be run on Microsoft IIS servers.
Forms generated in Forms projects are also perfect for creating various polls and surveys, statistical views and dashboards.
• Integration – in such projects, contrary to others, component configurators are not used. These processes are primarily used to create new components or data types of various kinds, intended to be used in other types of processes. An integration engine and definable parameters are used here, which serve as basis for generating the source code, which can also be compiled.
• Monitoring – projects of this type are used when it is necessary to utilise the platform’s logic capabilities, while the processes must be run in accordance with schedules but do not require user interactions. These applications usually run in the background of other processes and are perfect for performing logical analytical tasks, monitoring the work of other applications, monitoring data according to specific criteria and performing set actions or, for example, running scripts.