I've got several livecycle designer forms, saved as dynamic PDF's and uploaded into the Livecycle ES repository. These were created from existing .TDS files that shipped with LC designer.
I added the Livecycle Process Fields object to the form, but it fails to render buttons within the workspace (the user simply sees a submit button on the form).
I've noted that starting with a blank form containing process fields does, in fact, render properly in the workspace. I even tried copying components of the malfunctioning form into the blank form, with varying results -- sometimes it works, sometimes it doesn't. This _seems_ like a livecycle server bug to me based on the inconsistencies in the behavior that I'm seeing.
I've attached the form for your perusal.
Which render service are you using to render the form.
Remember, the form needs to contain the Form Bridge, which will take care of hiding the submit button. It ca be added at design time or a runtime.
I'm using the default render service on Livecycle 8.1
What makes me suspect this is a livecycle bug is that if I delete everything
from the form EXCEPT for the Process Fields elements, the form does render
correctly in the workspace.