1 ACCEPTED ANSWER
That is available in the Properties section of elements that can be added to the form:
The "created by" values aren't populated until the form is actually submitted (created). Before then, you can use a custom action to copy the "current" values to another field if needed.
And these Properties values can't be mapped to a keyword, so you'd need to copy the value to store as a keyword too.
Is it a Unity form you are working with? If so, you should be able to add these fields to the form just like you would a keyword field:
Those first 3 would all pertain to the "created by user".
But it sounds like you are meaning an HTML e-form, not a Unity form. I don't see any created by user properties documented there either. But if you capture the current user information and then route the form to a workflow queue with system work, that system work would be executed as that user and you could copy those values to keywords or properties to work with them before the "current user" becomes someone else.
Or at the point the HTML form is submitted, any of the methods I mentioned for non-(Unity) form documents would still apply too.
