| Author |
Message
|
| ucbus1 |
 Posted: Wed Dec 15, 2004 7:50 am Post subject: How to track a deleted Work instance? |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am not sure what happenned to work instance in Workflow and need to track it. It could be possible someone has deleted it from out-of-box client. If so, how to track it? Is there any FMCDB table that records this information?
Please let me know
Thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Dec 15, 2004 8:14 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Maybe if you had audit trails turned on , then maybe you can.
Otherwise I don't think there is anyway.
Moreover only the ones with process administration authority can only delete. So you can narrow the list of suspects. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 15, 2004 8:21 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ucbus:
Like Vennela says if you have Audit trail on you should be able to find the record that indicates the delete. It would be Event 21020, and the User Id column would give you the name of the logged in user that did the delete.
Also, if your Cleanup server has not yet run you should be able to find the Insance in the PROCESS_INST table. You would have to serarch for a Name = to the instance name.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Dec 15, 2004 1:05 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I think we have a problem:
1. I could not find it neither under instance list nor work item list.
2. I have checked the FMC_PROCESS_INST table and I could not find it either. Our clean up runs at midnight and this occurrend yesterday. So might have already gone
3.The table FMC_AUDIT_TRIAL is empty.Does this indicate the audit is not turned on.
4. I have checked with all the users who have authority and none deleted the work item. I have to believe since I had to show them what I was asking. They were not even knowing this
I am pretty much sure that we put this into Workflow.
my questions:
Is it possible, the Work instance got dropped by Workflow??
Any other place to make sure this? |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 15, 2004 1:36 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ucbus:
I am assuming that you are talking about a Process Instance disappearing, it is hard to tell since you are mixing terminology.
If the audit trail table is empty, then you are not using Audit to DB, but you may still be using Audit to MQ. Easiest way to tell is to dump all your FDL and using a text editor search for the keyword AUDIT_TO_MQ.
If you are auditing to MQ, then you must someplace have the queue defined and would have access to those audit records (at least you should).
If you are not auditing there is no way to get this information. Since the cleanup server already ran it is too late for it to be in the Instance table.
Once an instance is successfully created, I have never seen one disappear for no reason. It either ended normally, abnormall\ly or someone deleted it.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Dec 16, 2004 5:57 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Sorry for the confusion. I was talking about Process Instance only.
I have checked the FDL.. there was no audit. I guess the reason could be that when we enabled MQ_audit, it filled up the auditq so fast that we had to have another process to empty the queue. Also the db audit was not enabled. It could be because I felt the auditing slows down the process.
Since the cleanup server already ran we do not have a wayto check this.
Now which one you think I should enable? is it db audit or Mq-audit? What is the best practice.
Thanks |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Dec 16, 2004 6:26 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ucbus:
I am not sure there is a "best practice" it depends on your needs.
There is a difference in overhead, Audit to DB adds about 15% and Audit to MQ adds about 30%. So if you don't have cpu utilization to spare then Audit to DB adds less overhead. In either case you need to have some cleanup done. In the case of Audit to DB you will have to clean up the Audit Table periodically. In the case of Audit To MQ, you should have a queue monitor program running that will strip off the records. I would probably have the program running whenever MQWF was running, to avoid the problem you already noted (i.e queue filling up).
Also, if you do not need all of the Audit Events, you can consider using Filtered Audit. In this way you will only get the events logged that you really need.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
