No matter how much flexibility or openness a company intends to design into their software or application, somewhere, someday, someone is going to want to modify it.
The world around us is full of change. In fact, change is a constant component of every companies reality rather than the exception. So it is of no surprise that our efforts to design a business process management (BPM) design tool would also have to be open to change.
Here is the good news.
Knowing that there would be a need to debug custom workflow steps within your BPM application we designed FlowWright to fit into your work environment. We built the debug custom workflow steps functionality into the product from the start.
No need for complicated work around. No need to revert back to an older revision of the application code that does not have this customer step. No need to delete entire sections of code either.
Debug custom workflow steps within a workflow process requires these simple workflow steps:
- Implement the custom step according to the specified interface
- Compile the code to a DLL
- Place the DLL in the following directory: C:\inetpub\wwwroot\cDevWorkflow\bin
- Configure the custom step in the Configuration Manager
Turn off the cDevWorkflow engine services
- Put a break point into your code and attach Visual Studio to the w3p.exe service (You might need to run Visual Studio with Administrator privileges)
- Create an instance that contains the custom step
- Execute the instance using the UI
- Navigate to the "Workflow Instances" menu item and click the toolbar button "Run Engine"
Note: Once the instance starts to execute this edited custom workflow step, it will jump into the code you created within Visual Studio
Having a workflow design tool that makes the inevitable occurrence of change seem ordinary...... Priceless!
A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.