Web
Site
Search
Home
Why?
About Us
Do I have to register
Want to know more...
Our Promise to you
New to BPM
cDevWorkflow
Technology
Features
Architecture
Gallery
Screenshots
User Configuration
Step Data Types
Workflow Steps-Actions
Workflow Definitions
Edit Workflow Defintion
Render Workflow Definition
Workflow Instances
Render Workflow Instance
Instance Execution View
Workflow Tasks
ESB
Business Intelligence
Status
Videos
Configuration Manager
Building your first Workflow
Decision Example
Synchronize Example
Email Example
Task Example
Sub-Workflow Example
Example Workflows
Complaint Handling
Change Notice Management
Expense Management
Debt Collection Workflow
Hepatitis C Mutation Discovery
HR Job Requisition
Data Conversion
Customer Testimonials
Customer Solutions
Compliant Lifecycle Manager
Cloud HR Solution
Download
Community
Forums
FAQ
Installation
Configuration
Development
Product
Contribute
Partners
Customer Feedback
Education Institutions
Twitter Feeed
BPM Glossary
Blog
Buzz
Resources
Installation
Requirements
Create Database
Installation Instructions
Application Settings
Service Settings
Upgrade Instructions
License Activation
Configuration
Configure User
Configure Property
Configure Step
Examples
Samples
Change Notice
Leave Management
Custom Step
API Reference
Development
Engine Steps
Build Data Type
Build Step
Build Event Handler
How to
Extend Workflow tables
Integrate Workflow
Software Downloads
Version History
Support
Services
Workflow-BPM
Technology
Software Editions
Bug Reporting
Contact Us
Feedback
Partner Signup
Register
Login
cDevWorkflow
>
Example Workflows
>
Change Notice Management
The following workflow definition automates the process of initiating review and approval of changes to documents and drawings in a way that is compliant with a regulated company's described SOPs:
The process defined above involves the following steps:
The Change Notice (CN) is created and submitted
Workflow figures out who created the CN
Creator eSigns and submits the CN
CN is set to reserved status
CN type is determined
Based on the type, user selection is made for routing
Tasks are routed to users
If all approvers approve the CN, CN status is set to approved
If an approver rejects, then the CN goes back to the originator and goes back into the approval process
After approving CN status is set to closed
Copyright 2013 by cDevWorkflow