I ran a document through a Business Process Workflow. After the document runs through, I update the Business Process Details showing it is in the COMPLETED Step and the Resolution. However, when I view the business process details, it shows no details. Also to note, I am unable to start a Business Process even though the business process starting rule is set and enabled. There are no errors being reported and I was able to test the Workflow Web Services successfully. See screenshots below.
Question
Question
Business Process Details not getting updated after document runs through Workflow
Answers
There's a known issue in the Client where it caches the list of processes when you open it, then it only loads instances for processes in the list. It's being addressed for next version.
This issue should be less visible to participants in the process since it's less likely they'd look for an instance immediately after its corresponding workflow has been created.
Was able to resolve the issue.
Logged in this morning and it tested successfully.
Yes, I was able to search on the instance that ran successfully. I also close and reopened the client several times to see if it resolved the issue.
Replies
Do you mean that you look at the Business Process Details pane in the Laserfiche Client and it does not list the instance?
Yes, that is correct. It also does not allow me to start or initiate the business process, even though I have it set to allow everyone to start this form. Not sure if the entire business process isn't working.
Does the instance show if you search for it in the Workflow Designer?
Do the details display if you close and reopen the Client?
Was able to resolve the issue.
Logged in this morning and it tested successfully.
Yes, I was able to search on the instance that ran successfully. I also close and reopened the client several times to see if it resolved the issue.
There's a known issue in the Client where it caches the list of processes when you open it, then it only loads instances for processes in the list. It's being addressed for next version.
This issue should be less visible to participants in the process since it's less likely they'd look for an instance immediately after its corresponding workflow has been created.
This issue has been fixed for Laserfiche 10.2.