| Author |
Message
|
| Bobbo |
 Posted: Wed Aug 18, 2004 11:29 am Post subject: Create vs CreateAndStart |
 |
|
Acolyte
Joined: 17 Jun 2002
Posts: 50
Location: Buffalo, New York
|
Could someone give me a scenario where they needed to issue a "Create" and then at a later point had to "Start" the process? I find that I typically have to do both the Create AND the Start and cannot think of a scenario where I would need/want to do one without the other.
Thanks,
Bob |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Aug 18, 2004 11:35 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Then don't worry about it until you encounter such a situation. Just be informed that you have that flexibility there... |
|
| Back to top |
|
|
| Bobbo |
| Posted: Wed Aug 18, 2004 11:38 am Post subject: |
|
|
Acolyte
Joined: 17 Jun 2002
Posts: 50
Location: Buffalo, New York
|
That's what I've been doing. But...it would be nice to know how others have utilized the system. Know how others have solved their problems might lead me to solve my problems differently/better.
My assumption is that the ability to create only is there for a reason. What is that reason?
Bob |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Aug 18, 2004 11:58 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
For example I have a claims management system. I have a database which has the information that I would populate into a datastructure while creating a process instance. I have a nightly batch job that runs, reads the new records in the database and creates the process instances
The next morning the manager comes to the office. Based on the number of created instances he would employ the under writers. For example if he gets 100 claims then he would engage 10 under writers. If he is falling short in number, say if he has only 8 of them that can work, then he will start 80 claims instead of starting all the 100.
This is just imagination but tell me another way of doing it. |
|
| Back to top |
|
|
| Bobbo |
| Posted: Wed Aug 18, 2004 12:02 pm Post subject: |
|
|
Acolyte
Joined: 17 Jun 2002
Posts: 50
Location: Buffalo, New York
|
| Great! Thanks for sharing...you're getting my creative juices flowing... |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Aug 18, 2004 12:14 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
One other good reason to use this:
Create an Instance is a VERY expensive thing to do in the workflow system. Start the instance is not as expensive. Lets say you have a workflow system that creates several thousand new instances of Model A every day. What you could do to lighten the load during peak times is
1. Create the number of instances you anticipate needing during off peak
2. Write an Instance server, that simply serves up an instance when you need one.
3. Prior to starting the instance you can change its name, so you will still have a meaningful Instance name
4. Start the instance
Obviously, its a little more complicated than that, but I think you get the idea
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
