Skip navigation
Currently Being Moderated

How to remove submit buttons on workspace and use submit buttons on PDF instead?

Nov 9, 2010 12:24 AM

I am working with LiveCycle ES2. I will get submit buttons automatically render on workspace according to routes i designed after User component. However, I do not want that submit buttons on Flex. I would like to use submit buttons on PDF as designing in LiveCycle Designer.

 

Could you please give a suggestion on this?

 

Mac

 
Replies
  • Currently Being Moderated
    Nov 10, 2010 11:02 AM   in reply to Sittisorn Pichainchote

    I believe you add a standard button that fires the click event of the hidden button that actually submits the form.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 5:44 AM   in reply to Sittisorn Pichainchote

    You can change the render service an remove the "Enable PDF form for Workspace"step, which enables the communication between the PDF and the Workspace container.

     

    If you go under Presentation & Data and edit the Action Profile you'll notice the Default action profile is using "Render PDF Form (system)" to render the form.

     

    Open  "Render PDF Form (system)" and remove the "Enable PDF form for Workspace"step and see if that helps.

     

    The Render PDF Form (system) is in the Process Management (system) application. If you don't have that application installed, just do a File->Get Application.

     

    Jasmin

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2010 5:53 AM   in reply to Sittisorn Pichainchote

    Ok, here's another workaround.

     

    Put two submit buttons on your form. The Enable PDF for Workspace step looks for a submit button. If it find two, it doesn't which one to use and hide the complete button.

     

    Would that work?

     

    Jasmin

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2010 7:00 AM   in reply to Jasmin Charbonneau

    You would also want to ensure that the Adobe LiveCycle Form Bridge is not on the form.

     

    Here are some scenarios, from the Workbench help, which may help:

     

    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
    Result

    Design: The form includes no submit button.
    Result: Workspace ES disables the Complete button and users cannot submit the form.

    Design: The form includes one submit button.
    Result? Workspace ES hides the submit button and enables the Workspace ES Complete button.

    Design: 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.
    Result: Workspace ES hides the submit button and enables the Workspace ES Complete button.

    Design: The form includes multiple indirect-submit buttons that point to one or more direct-submit buttons.
    Results: 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

    Design: The form includes either an indirect- or direct-submit button in a repeating subform.
    Result: 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 form object to the form design 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.

     

    Hope that helps.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 29, 2010 1:23 AM   in reply to Sittisorn Pichainchote

    Very simple solution!!

     

    Place the Process Fields inside a Subform and hide the Subform.  Thats should work perfectly.

     

    I have attached the sample PDF herein. The form has two ordinary button (Approve & Reject) and the Process fields set.

     

    http://groups.google.com/group/livecycle/web/Page1.pdf

     

     

    Nith

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2011 7:59 PM   in reply to $Nith$

    Hi,

    Can you please attach the file again because the attachment is not working. It will be highly appreciated.

    Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2011 9:20 PM   in reply to avi_nyc
     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2011 9:37 PM   in reply to $Nith$

    Hi Nith,
    Thanks for the attachment. I have another question. I want this form to  travel across the process as the asset of the Task. In other words, my process  has 3 reviewers or users and this form will be reviewed by each one of them. but  everytime it is rendered on the screen of the user , he or she must see  different buttons..for example reviewer 1 must see submit and complete but  reviewer 2 must see approve and deny buttons. and each of these buttons can do  some action so that they can be passed to next user in the process....please  help!!
    Thanks!!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 5, 2011 1:23 AM   in reply to avi_nyc

    Do the following in form:

    1. Place all your required submit buttons on the form

    2. Place a hidden field on the form which is used to hold the current actor's role (e.g reviewer1, reviewer2 or reviewer3)

    3. Write some hide/show logic on docReady event of the form based on the current role (available in the hidden field)

     

     

    Now you should set the current role by some way. Here is an option:

     

    Prepare data process

    1. In the prepare data process, create a string variable (say CurrentRole) and make it as INPUT

    2. Assign this variable value to the hidden field on the form (Using SetValue activity)

     

    Long-Lived Workflow

     

    1. Double click on the Start Point acitvity

    2. Expand Presentation & Data panel from Process Property perspective

    3. You will see the variable created on Prepare data process appears here

    4. Just type any lieteral value (Say: Initiator)

    5. Do the same steps (1 - 4) on all your three AssignTask activity (just change the CurrentRole literal value)

     

     

    There you go..

     

    Nith

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 5, 2011 1:24 AM   in reply to $Nith$

    prepare.png

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 15, 2011 5:40 AM   in reply to $Nith$

    $Nith$, I wanted to display the Save (as Draft) button in Workspace without having a Complete button. I spent the last 5 hours trying to solve it in a variety of ways. Using multiple hidden submit buttons almost did the trick, although Workspace complains about multiple submit buttons, causing confusion among our users.

     

    Putting the Process Fields inside a hidden subform like you suggested works like a charm!

     

    Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2011 9:58 PM   in reply to c@tc.se

    Why don't you use the default Save button appears in the workspace? This button will save your form into draft folder and update the Task Status (as draft).

     

    PS: I hope the button will be visible only if you use XDP forms.

     

    Nith

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 14, 2013 3:43 PM   in reply to $Nith$

    Hi guys,

     

    Could you help me on this?

     

    http://forums.adobe.com/thread/1275094

     

    Thanks!

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points