InfoPath Dev

We are looking to log comments regarding a deny request in a workflow. When ever some one denies a workflow we need for them to log their reason for denial. Is there a way to make that row that was just comitted read-only within InfoPath? What would be a good way for this to occur, if possible?

It's not clear how your workflow is built nor how InfoPath is related to the workflow.  Could you expound?

In a nut shell, there is a document which is created and designed in InfoPath. When a person creates a new item in the library, the workflow begins. The new document needs 6 approvals before the final step. The approval is done through two radio buttons (approve/deny) for each of the 6 sections. There is a rule which pulls the FirstName, LastName, and userId() and puts it in a read only text field as their digital signature.

In the event that one of the people deny the request at any of the 6 steps, there needs to be a comments section forcing the user which denied the request to provide a reason.

Keeping the orginal document, to have the orginator change some values then to restart the workflow without creating another item in the document library.

I have two real questions, is restarting the workflow on the orginal document possible without creating another item in the document library, if so, how? Second question is in regard to the repeating table, if I had a repeating table and the end user inserted a row to add a reason for the rejection and upon submission that the data was just input was frozen/readonly.  Basically having a Repeating Table to Insert new records but not delete/edit existing values in the repeating table.

 Does that make more sense?

Yes, all of that info is critical to resolving the issue, so thank you for adding.  What you've described sounds very doable and is in fact something I am doing currently with a pretty dynamic form, except I am not asking for comments upon rejection - that is all handled in person instead of through text, but it's certainly a viable option.

1. What actually IS this workflow?  What is it built in?  SPD, Visual Studio?
2. Why do you even need a repeating table for comments?  Isn't each approval for all 6 phases in a different section with its own buttons and own electronic signature fields (not actually using digital signatures from what I read)?  I would think you'd have a hidden multi-line text box that only shows up when the "reject" button is pushed and has validation on it that requires it to be filled.