Astoria Workflow allows you to model any business process in your organization. It also helps you keep your content production processes on schedule and on budget. Astoria Workflow requires no programming; a one-day training class is all you need to master the configuration options. These options include:
- Transitions: What is the starting state? What are the possible next-states for the current state? Should the system do something before the transition occurs? Should the system do something after the transition is complete?
- Notifications: Who should be notified? Does the notification go to a group of people or to one person? Who gets notified as each workflow task is completed?
- Tasking: Is this a job to be done by one person, by one person out of a pool of people, or by everyone in the pool? When the task is completed, does it need to be signed electronically?
- Escalations: Who takes the job if it is not done in time? Who can override the default behavior of the workflow?
Transitions in Astoria Workflow may be signed electronically in compliance with 21 CFR Part 11 statutes from the US Food and Drug Administration. A transition configured for electronic signature requires the user to provide credentials, which are immediate authenticated. The signed transition becomes a permanent record that the user completed the appointed task at a specific date and time.