Hi Miruna,

I started manually associating the starting entry with the business process when I first noticed the problem, in an attempt to force it to show up on the entry. It didn't work but I haven't reversed it yet.  Still holding out hope I guess.

This is happening with new business processes as well. I just created a new business process and a new workflow to invoke it, with the same results.

[Edit: The business process had still not appeared half an hour after my initial test. I triggered the business process directly from the client, and then both the copy I had triggered and the one the workflow had invoked appeared on the document.]

It's probably the same issue discussed here: https://answers.laserfiche.com/questions/111809/Using-the-business-process-screen-as-a-built-in-instruction-panel-for-workflows

I think I've got this now. It's a security problem closely related to the threads in  your link.

In the workflow properties under "Make this workflow a business process", there are two options allowing client applications to Start or Display the process. I had Display selected. Without selecting Start here, the  Business Process starting rule is not created, and that rule is where the security is applied to grant groups access to the rule, either starting or viewing. 

I'm going to test adding the starting rule and securing it so the process can be viewed but not started. If I'm right about this, I hope future versions will at least make this interaction more intuitive.

From my tests it appears that Business Process history is only visible if:

• "Start this business process" is enabled in the workflow properties
• The "Business Process" type starting rule is enabled on the workflow
• The user logged into the client has or inherits  the "view details" right from the starting rule's security tab

The right to start the process can be turned off within the starting rule to keep the workflow out of people's starting lists.

This leaves me with one last question. Why is the option to allow viewing history from the client available in the workflow properties when the option to start the process from the client is not enabled?  

Yes, the workflow has to be marked as a business process for its details to be published to the associated entries. You don't need to check "start this business process" if you're going to have regular starting rules, but you do need to have "display this business process' information" checked. Otherwise, Workflow won't publish the history to the repository.

As for why the 2 options are independent, there are 2 parts to business processes: starting them through client applications and providing information/instructions to the user throughout the process. Say you have a BP that starts when a document is dropped into a folder and sends that document to 2 users for approval. You can provide the 2 approvers instructions when the document gets to them, then record their resolutions through business process step activities. Workflow also tracks reporting data so you could create metrics on how long each user takes to approve a document.