you may configure the Lock fields after signing the digital signature.
In the Livecycle designer thru the properties of this field: Object
Properties -> Signature TAB. Here can exclude the submit buttion or any
other fields if required, not to lock after signing.- Raghu.
We had this issue with email formats other than plain text. Can you try
the current process with a plain text email?. If this still having
issues double check the variables and settings of the process. Please
check the attached image for the settings of email process and adminUI
of the variables used. - Raghu.
Used SOAP, REST and servlet/http submission, for servlet submission you
may find more examples online. On this forum you can check this:
http://forums.adobe.com/message/3970459#3970459For SOAP use, data
binding is not for all fields on the form, need to bind the webservice
to create a data connection using "New Data Connection" using "Data
View" TAB on form, with this can submit the xml to webservice to further
processing. Is there a way to submit xml in this case, using SOAP in pdf
If its restricted to SOAP call only, use Submit button (Submit type),
with LC SOAP Process as data binding. Now assign the whole xml into a
variable on pdf before sibmit and bind/send the variable value to SOAP
input. Here xml will be your LC process input not the PDF. Then
re-create the PDF using this xml on LiveCycle process, hope the template
is available for the LC process. This way we can have the PDF available
in the process, if not using REST and export the whole PDF. Other than
this i am...
Method1: This method only works in same PDF window.On the click of the
submit button, based on the webservice result we can close the PDF. As
you already having in the "Out Str", this variable having detailed
message kind of thing, so it would be easier if you have one more output
variable to know if this submission is success or failure or can use the
"Out Str", it self to compare and close the PDF.Here i am using
"strResult" to hold webservice success or failure using true/ false
To get always o/p as Base64, you may configure this property under
EndPoint TAB of your service/process. If you are already using, please
ignore this.From AdminUI, Click on the SOAP endpoint link under endpoint
TAB, then Select the "Default protocol for output BLOB objects:" value
as "Base64" from drop down. This setting will reset to default to every
new deployment (application undeploy and deploy). What is the o/p
variable data type of this process? as we are not using FIPS, no idea
the above ...
We are using WebserviceSettingBean in other way, if you already tried or
it wont suits ur requirement may ignore this method. This way still it
can be used as runtime wsdl and port across environments without
updating process each time.Double Click on WebserviceSettingBean
variable and on the opened pop-up click the browse button under Datatype
Specific Settings this will gives another pop-up to configure wsdl.
First time configuration need to give full path od the WSDL URL and it
uses that time...
Here are the details for the above question. We render/generate a pdf
using LiveCycle process, the rendered pdf will be on server side and can
be accessible for certain period of time, this is the configuration
setting on adminUI.In my project we are not distributing a form up front
and submit later at any time. We are generating/rendering the pdf on
demand using the data from the application while submitting the rendered
pdf we are invoking REST URL for one of the flows. In this case the pdf
I am using REST URL in both ways and i have no issues with it. Here the
PDF i am using while submit thru browser will generate on the fly and
its resides on LC server. In your case the pdf via browser is resides on
local machine or generates on demand?I am able to reproduce your issue.
When open the pdf with Google Chrome it is working as expected and the
same pdf in IE its throwing HTTP 403. In both cases the PDF is on local
This issue we had when submissions from outside of the network.
LiveCycle server on some company/organization network, but not all the
submissions will be from with in the company/organization network. If
this is the case even we turn of the authentication we cannot access the
URL from outside network. To resolve this, open as public URL for this
process: The same server can be accessed by some other name which will
not ask any type of authentication or security. with this we can submit