THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Paul Nielsen

www.SQLServerBible.com

Business Process Design Q?

I’m adding a business process feature to my app and before I start coding, I thought it might be a good idea to vet the design past a few smart yet critical folks.

 

The basic idea is around the concepts of events and actions. An event might be something like a sale, or attending a seminar, or calling tech support. An action is a scheduled action that someone must perform or check on, or an automated action such as sending a letter.

 

An event can be manually triggered or automatically triggered by a number of system functions or data points being such as a foreign key being applied (association), a data policy being fired or resolved (the app has a rule-based data policy feature), or a workflow state change (objects within classes can have workflow states). Lastly, another event being fired or resolved can trigger an event.

 

When an event is fired it schedules a number of automated actions (n) number of days from the event.  Actions belong to an object and have a FK to the ActionConfig. 

 

An action can be manually fulfilled or canceled, or it can be automatically fulfilled by another process, or by another association (FK) being applied to the object in question.

 

EventConfig (name)

  |    \

  |   EventTrigger(the things that can trigger the event)

  |

ActionConfig(events that are scheduled)

  \

   \  Object

    \  /      

  Action (the actual scheduled events for an object)

 

The application already has a strong workflow state feature. Every class can have inheritable workflow states with a prescribed workflow state path (A -> B, B -> C, B -> D, C -> D, etc.). If the class has workflow states then the objects must have a workflow state. Workflow State is a part of the association design – think of it as a FK with intelligence. So there’s already some business process flow in the app.

 

My question to you is, does this look robust enough for scheduling normal business process flow? What am I leaving out? Do the names event and action seem appropriate and obvious? Any other ideas?

 

Published Friday, July 10, 2009 12:00 PM by Paul Nielsen

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Mike Brunt said:

This looks logical to me Paul.  For things like this and also for application analysis I often use a MindMap.

July 10, 2009 1:28 PM
 

Lori said:

Paul,

Is it set up so that an Action can spawn an Event that then has other associated Actions?  That's one of the things that we had to look at.

July 10, 2009 2:48 PM
 

Mike C said:

Hi Paul,

A few q's:

-You're coding this in SQL?  Or a client-side language?  

-It almost looks like there could be some sort of polymorphic relationship between action and event, or at least a common parent to inherit from.  Is this how you see it?

-Do ActionConfig and EventConfig allow you to define business rules for your actions and events, or more of the administrative details?

Thanks

Mike C

July 12, 2009 9:38 AM

Leave a Comment

(required) 
(required) 
Submit

About Paul Nielsen

Paul Nielsen believes SQL is the romance language of data. As such he’s a hands-on database developer, Microsoft SQL Server MVP, trainer, and author of SQL Server Bible series (Wiley). As a data architect, he developed the concepts of Smart Database Design and Nordic – an open source O/R dbms for SQL Server. He lives in Colorado Springs.

This Blog

Syndication

News

news item test
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement