LiveCycle Workspace ES: how to disable/hide the complete button


When working with forms in Workspace, you automatically get a complete button which often hides the submit buttons on the form.  It is a common requirement to hide this complete button, especially if you have pre-submit validation scripts on your form, or multiple submit buttons depending on the context.


You can disable this button in the following ways:

  1. You can customize the Workspace interface in Flex Builder
  2. You can modify the standard rendering services (for e.g. you can remove the route to the last two steps “Workspace enable” and “Reader extend” in the LC7UpgradeRender service)
  3. Use multipe in-direct submit buttons on the form, that contain a call to the click event of the hidden FS_SUBMIT button


The submit/complete button will still be available on the card/list view in the Workspace todo list.  This enables users to submit the form without even opening the form itself in Workspace.  In order to disable this button in the card view, you have two choices.  Firstly you can specify the ‘Form must be saved’ setting in ‘Form Data Mappings’ in Workbench.  The other option is to change the “client_routes_formViewOnly” to “true” in the workspace global settings, as described here:

under: Workspace Administration Help > Importing and Exporting Global Settings > Workspace ES global settings

Additional Information

To understand the situations when the complete button is displayed, and when the form submit buttons are displayed, please refer to the following description of the Inject Form Bridge service.


Adds javascript code to an Adobe PDF form or Adobe Acrobat form to enable it to function within LiveCycle Workspace ES. The PDF form must have been created using Adobe LiveCycle Designer ES, version 8.2, or Adobe Acrobat 7.0.5 or later.

If your process uses Adobe XML forms (XDP files), you can render the form to PDF and then use the Inject Form Bridge operation. To render to PDF, you use the renderPDFForm operation that the Forms service provides.

Workspace ES provides a Complete button that users click to submit their forms. However, forms can also include submit buttons. When the Inject Form Bridge operation is used on a form, Workspace ES either hides the submit button, or disables the Complete button.

Form design


The form includes no submit button.

Workspace ES disables the Complete button and users cannot submit the form.

The form includes one submit button.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes a button (indirect submit) that points to a submit button (direct submit)

Indirect-submit buttons always take precedence over direct-submit buttons, even if multiple submit buttons exist. Workspace ES always shows the indirect submit buttons.

Workspace ES hides the submit button and enables the Workspace ES Complete button.

The form includes multiple indirect-submit buttons that point to one or more direct-submit buttons.

Workspace ES disables the Workspace ES Complete button. The user must click the appropriate button on the form to submit it.

The user can still save a draft version of the form or take the form offline

The form includes either an indirect- or direct-submit button in a repeating subform.

Workspace ES excludes these buttons for submitting the form in Workspace ES.

Note: When the submit button, that was added to the form design with the Process Fields,  is hidden, the button still provides the functionality for submitting the form.

Submit requests are handled by Workspace ES, which acts as an intermediary between the LiveCycle ES server and the form. Also, forms can be used both offline and online.

reference: (180833713)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.


When reading XML data into a process variable in LiveCycle ES you may receive the following exception:

Target exception: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
at bsh.BSHMethodInvocation.eval(
at bsh.BSHPrimaryExpression.eval(
at bsh.Interpreter.eval(
at bsh.Interpreter.eval(
at bsh.Interpreter.eval(
at com.adobe.workflow.qpac.script.ScriptService.execute(

This particular exception occurred using the Script QPAC to read in the XML data using script as follows:

String clean_xml = patExecContext.getProcessDataStringValue("/process_data/myxmlbranch");

clean_xml = clean_xml.replaceAll("(<)","<");

clean_xml = clean_xml.replaceAll("(>)",">");


This script works fine in LiveCycle 7, but after upgrading to LiveCycle ES, the script throws the error.


There are some unexpected characters in the XML data stream.


In this case there were quotation marks at the start and end of the XML stream.  Such characters were stripped away automatically in LiveCycle 7, but LiveCycle ES is more strict with the format of the incoming  XML.  You must remove the unexpected characters manually and then it will process the XML without problems.

Additional Information

If a LiveCycle 7.x process, that is upgraded to LiveCycle ES, includes the Script QPAC, the Script QPAC may contain script that was developed using the LiveCycle 7.x API. To ensure compatibility with LiveCycle ES, the script may need to be rewritten based on the LiveCycle ES API.

In this case the getProcessDataStringValue() and setProcessDataValue() methods of the patExecContext embedded object are available in ES just as they were in LiveCycle 7 so there were no changes necessary in the script.

reference: (180833653)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)