| Author |
Message
|
| rokual1 |
 Posted: Fri Feb 10, 2006 10:45 am Post subject: Levels in workflow |
 |
|
Newbie
Joined: 10 Feb 2006
Posts: 1
|
| Why are levels used in workflow? |
|
| Back to top |
|
 |
| jmac |
| Posted: Fri Feb 10, 2006 11:09 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It is my opinion that for the most part they are NOT used.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Feb 10, 2006 12:25 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Levels are used if you want to assign activities to staff based on their Level.
As JMAC said I never saw them being used.
_________________
-Ratan |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Sun Feb 12, 2006 4:02 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Not a very popular feature, but levels can be used to differentiate staff members from each other based on the notion of
"LEVELS" in workflow automation. There are a total of 10 levels available to use (0-9 for assignment in the build suite).
You can change the names of the levels, but cannot create new or delete existing levels.
These levels can be used as a measure when performing filtration of staff candidates for dynamic assignment to program activities.
Imagine a scenario where a problem occurs within your business process flow, and one of the program activities within the
flow is designed to handle such errors by writing to a queue based on the severity of the error. This queue is then monitored
by a team of specialists that have experience ranging from 1 to 10 years. Depending on the severity of the error you may
want a critical error be assigned to a staff member that is at a higher level(more years of experience and hence quicker
defect resolution), and perhaps less severe (low/medium) errors to staff member(s) of a lower level.
ROLES in staff assignment are more common. I would think if you have extremely large amounts of staffing, and assignment
going on within the flow, it might serve you some purpose. The expense of dynamic staff resolution should be considered
in any case though.
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| jmac |
| Posted: Sun Feb 12, 2006 4:09 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
IF you are going to use levels you must remember that a Person has only one level. Levels are not associated with anything other than the Person object.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| JasonG |
| Posted: Tue May 09, 2006 10:26 am Post subject: |
|
|
Novice
Joined: 02 Jan 2003
Posts: 24
Location: Buffalo, NY
|
| We ran into the same problem when we realized that if Level is an attribute of a person. If the person is identified as level 5, and plays many different roles then every role they play must be at level 5. We simply decided not to use the levels. |
|
| Back to top |
|
|
|
|
