| Author |
Message
|
| ucbus1 |
 Posted: Tue Nov 01, 2005 12:44 pm Post subject: Workflow people adminstartion utility |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am thinking of developing a utility that would do the following tasks.
a.Allow users to reset their passwords
b.Allow ( superviosr/manager) to change the authorizations of the users working under them
When performing b, I would like to propagate the changes to the buildtime and runtime as well.
Now here are my questions:
1.Besides the above are there any additonal functions one can think the utility should perform?
2. Has anyone of you tried to develop such a utility?
3. Can anyone of you give an archetecture direction?
-how to parse the FDL
-how to sync buildtime and runtime
4. Is it worth the effort? I am not sure how long IBM is going to support Workflow
5. Will it be of any commercial use?
6. Are there any commercially available products out there?
Please share your ideas/suggestions |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Nov 01, 2005 7:39 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Have a look at the Staff api in v 3.6 it might do everything you want.
I have not yet used it so I cant say for sure.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Fri Nov 04, 2005 8:55 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Jmac,
Thanks for the response. Unfortunately we are at 3.5 and not sure when will we be moving to 3.6.
All,
Has anyone used the staff API which JMAC mentioned? |
|
| Back to top |
|
|
| kotha |
| Posted: Fri Nov 04, 2005 10:26 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
If you are using 3.5, I dont think we have StaffAPI for 3.5. This is the new feature for 3.6. Correct me if I am wrong.
Thx |
|
| Back to top |
|
|
| OLearyocas |
| Posted: Mon Dec 19, 2005 11:39 am Post subject: |
|
|
Newbie
Joined: 25 May 2005
Posts: 3
Location: Ohio
|
We designed a change authorization tool that presents a supervisor with a gui and makes database delete/inserts behind the scenes in the staff tables rather than trying to format an fdl. When user starts the utility we retrieve from the Workflow DB the list of users they are authorized over currently and present that to them as the list of people they can change. Once they select a user the interface queries the DB to return the list of who the selected user is authorized to see and who is authorized to see them.
Within the interface we parse the lists that come back to limit them to only include users that were part of the original users authorized list. We present in two lists with a simple add remove button for either who can be authorized over selected user, or who selected user could be authorized to see. Original users makes as many contact admin and delettions as they want. Once they are ready they click update and we delete the selected user's listings and replace with the new list.
Only does this for runtime, though, so before doing any buildtime staff work it is necessary to synch up. Our runtime is server while buildtime is local though so we didn't try to do same for buildtime.
Make the list multi-select though as our users complained first day that they could only add/remove one at a time (even though we store all the changes for a single update). |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Mon Dec 19, 2005 5:36 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| Very interesting solution indeed. I never thought of interacting with runtime directly as I was always warned not to touch the runtime tables directly. I was asked always to use the API calls. |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Dec 19, 2005 6:44 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| OLearyocas wrote: |
| We designed a change authorization tool that presents a supervisor with a gui and makes database delete/inserts behind the scenes in the staff tables rather than trying to format an fdl. |
Making any changes to the MQWF tables is extremely dangerous, and could cause you grief in the future.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
