How about adding a condition before you set the fields?  You would only set the fields if they do not already have a value.  This logic would be after the data is loaded into the form for subsequent viewers.

If the Originator Name text box is empty

   then set the Originator Name Text box to the system property

Another option would be to only populate that value when the row is initially created.

If that helps, please click the Kudos button.

David

Do you have a place to save the original originator and form Submitter, and then read it back in when the form reopens? You have some options here, either storing this information in a SQL table with a unique ID related to the instance of the form, which you'd read back in on form intialize. Or, when the form is submitted, store these values as data field on your worklfow and give them back to the form as parameters for subsequent tasks.

i have a place to save the original originator and form submitter. How would I go about using  your second option:

Or, when the form is submitted, store these values as data field on your worklfow and give them back to the form as parameters for subsequent tasks.

And what would that look like once the workflow process is complete and people would like to view the form/information for history?

On the workflow process definition, create two data fields. We will call them "Form Originator" and "Form Submitter". On initial submit of your form, when you start the workflow process, you'll have the option to set data fields in the new workflow process instance. Pass along the values being displayed on your form to these workflow process data fields.

Create two new parameters on your form, also call them "Form Originator" and "Form Submitter". In the workflow when you create your task, pass through the data fields to their corresponding form parameter. Then in the form intialize rules, use these parameter values if they have a value.