Search Business Process Details Size

asked on March 10, 2021

Is there a way in Syntax to search the size or count of Business Process Details?

A little context:
This morning a co-worker found a document that could not be opened. After digging into this document, I couldn't open it either. That was both in the Laserfiche Client and the Web Client. I could see preview and meta-data but the Business Process Details hung up, and crashed the clients when the document was trying to be opened.

Checking on workflow I found that the workflow for the document has been running repeatedly every morning for about 4-6 months. We had 7,416 times it's ran between 3 workflows.

I eventually had to make a duplicate of the document and delete the original. This allowed me to rerun the process again and find the issue, and get it filed. I've tried to search several times now with no success as I fear there are multiple documents with this issue.

Any help would be greatly appreciated.

Thanks

0 0

SELECTED ANSWER

replied on March 10, 2021

If you have access to the SQL database, you can run the following query to find entries that have business processes run on them:

SELECT COUNT(DISTINCT bpe_id) AS BPCount,
bizproc_entity_entry.tocid AS [TocId], toc.name as [Name]
FROM bizproc_entity_entry 
JOIN toc on bizproc_entity_entry.tocid=toc.tocid
GROUP BY bizproc_entity_entry.tocid, toc.name
ORDER BY BPCount DESC

I don't think there is a way to get this information directly from the client, other than searching for all documents with a business process history and going through them one by one:

0 0

View 1 previous reply

replied on March 11, 2021 • Show version history

Awesome, I'll give this a try and see what comes up, there are 4 databases I'll have to perform this search on, probably set it up to have Workflow send me a report on these every week or something.

We actually went through with a syntx query that looks like this:

({LF:BpName = "Workflow-BP"} & {LF:BpeCompletedDate>="3-10-2021", LF:BpeCompletedDate<="3-11-2021"}) & {LF:Modified="2021/03/11"} & {[]:[Document Date]<="2021/01/01"}

And then proceeded to check each document that was returned individually. Surprisingly we found 103 other documents with this method, and fixed nearly 90 of them. There are a small handful of ones left but we are working with our HR department to see what to do with them.

Thanks for the help

0 0

replied on March 11, 2021

So ran that query, and the original doc for this was not the worst offender.

I found 3 documents with over 120,000 entries, more than 20 documents with over 10,000 entries... and I've only searched one repository so far.

Thanks for you help on this.

0 0

replied on March 12, 2021

We can reproduce the crash (though, not at 7500 instances, but at a much higher number). Thank you for reporting it. Reference ID 309577.

0 0

replied on March 12, 2021 • Show version history

@████████ That's good to hear! Hope it can be eventually fixed.

Another factor of the crash was due to the system that was trying to view the document. It's about 5 years old, running windows 10, with 4 gb of ram with an i5 Intel processor and a 500gb HDD. So it struggles with much more than just this.

The strange thing is that I've opened up some of the documents with 17,000+ entries and although they took a while, they did eventually open, that document however always caused a crash even on Web Client. I made a copy of and deleted the original just in case something was wrong with it.

0 0

Question

Question

Search Business Process Details Size

Answer

Replies

Sign in to reply to this post.