Is there a way to keep a record of when, by whom and what files are destroyed from the EPDM recycle bin?
Is there a way to keep a record of when, by whom and what files are destroyed from the EPDM recycle bin?
Hello Ashkan,
I am not aware of any method to accomplish this.
Best Regards,
Joy
Hello
You can write a trigger on table documents which will log every deleted records from this table
Best regards
Daniel
Hi Gentleman,
Maybe I misunderstood, the question asked about 'destroy' - which is not recorded.
Best Regards,
Joy
Hi Joy
When you delete file from localview this file is marked in database Deleted = 1
When you destroy this file record is deleted from database and trigger can catch this action (from deleted table) and make new entry in your log table.
I try to make this trigger and let you know
Best regards
Daniel
Hi Daniel -
Cool - I'm assuming you are talking about creating a SQL trigger on the table?
Will that work if the user does not do a Delete, but, rather a Destroy right away?
Cheers,
Joy
Hi Joy
Exactly, i was talkin about SQL trigger. I was not precise sorry
I thought to create a table i.e.named LOG in the EPDM database. To DOCUMENTS table add a trigger which can catch any deleted record.
This deleted record are de facto destroyed files. Information about deleted record trigger will put in LOG database.
For Report feature from EPDM i can create query to the SQL database to view those deleted records/destroyed files.
I think it would work
Best regards
Daniel
Hi Daniel,
After conferring with the experts here is some advice:
Do not put custom tables in the vault database – it is not supported and will lead to problems.
You could probably sort it out with a view from another custom database.
Triggers can be tricky as well since they could add overhead.
Triggers with dependencies could also cause future upgrades to fail because of constraints kicking in.
Best Regards,
Joy
Hi Joy
Thanks for advice i will keep it in mind
Best regards
Daniel
Hi Daniel,
After conferring with the experts here is some advice:
Do not put custom tables in the vault database – it is not supported and will lead to problems.
You could probably sort it out with a view from another custom database.
Triggers can be tricky as well since they could add overhead.
Triggers with dependencies could also cause future upgrades to fail because of constraints kicking in.
Best Regards,
Joy