Hide Submit Buttons
Hi,
I have 2 submit buttons.I wrapped them up in a subform.
1st button is used to send e-mail (used Javascript)
2nd button used to save this form to app server (defaulted Javascript code)
Now when user clicks 1st button I need to hide this 1st button & I did it using
this.presence = "hidden";
I also want to hide 2nd button simultaneously.when user clicks 1st button.How to do this?
button 1 click event
----- ADOBE_DATA.#subform[0].buttonform.submitToSAP1[0]::click: - (JavaScript, client) -------------
button 2 click event
----- ADOBE_DATA.#subform[0].buttonform.submitToSAP1[1]::click: - (JavaScript, client) -------------
rgds
vara
Edited by: Vara K on May 26, 2009 9:31 PM
Edited by: Vara K on May 26, 2009 9:46 PM
Hi Vara,
In the Button 1 click event write the following code.
submitToSAP1[1].presence = "hidden";
But it's better to change the name of the buttons instead of having like this :[1].
Regards,
Ravi
Similar Messages
-
Can I hide the Submit By Email button until a radio button is selected and then the Submit By Email button appears? Is there a script for that?
Yes, you can do that, but it will probably require that your form be saved as dynamic rather than static.
On the RadioButtonList item (not either of the buttons themselves, but the overall group item) on the Change event you could put:
(make sure you specify the item values - in my sample I did so with 1 being value for the Yes radio button and 0 being for the No radio button)
if (form1.MainForm.RadioButtonList.rawValue == "1")
form1.MainForm.EmailSubmitButton1.presence = "visible";
else
form1.MainForm.EmailSubmitButton1.presence = "invisible";
Then you'd want to set the default presence of the Submit button to "invisible" and save your form as Dynamic. -
Hi all,
I have an interactive form with a submit button that i displayed online thru webdynpro for the user to key in data. And when user clicked on the submit button, i will validate the data in the webdynpro action handler, and will send out a copy of the same form as an attachment in email.
But when sending this form in email, i do not want the email recipient to see the submit button when they open up the form to view. And the form should be in display mode as well.
So 2 questions:
1. how do i go about hiding the submit button and setting the form in display mode?
2. For setting the form in display mode... i currently uses cl_wd_adobe_services create_pdf method to generate the xstring for email, so i can set the enable = ' '. Any other way to do this if i going to use the xstring from pdfsource of the interactive form UI element?Hi,
For Hiding the UI elements in Interactive form try using Scripts (FormCalc).
The script for hiding the Submit Button is:
<path of the UI element in the Subform>.presence = "visible" / "hidden"
The Script for making a field editable / read-only is:
<path of the UI element in the Subform>.access = "readOnly" (Not Sure about the casing
For more information, refer to the bolg:
/people/juergen.hauser2/blog/2006/01/31/access-mode-and-presence-of-fields-on-adobe-interactive-forms
Regards,
Poojith MV -
No submit button in distributed form - JavaScript help
I have creted a from in Live Cycle Designer. After distribution submit button is not visible in Acrobat and Reader. I've looked at the form JavaScript and find out this part of code which probably hide submit button in Acrobat 9:
showAutoGenSubmitBtn = function(bShow)
var autoGenSubmitName = "%AUTO_GEN_SUBMIT_NAME%";
var fld = this.getField(autoGenSubmitName);
if (fld != null)
var b= this.dirty;
if (bShow)
fld.display = display.noPrint;
else
fld.display = display.hidden;
this.dirty= b;
// Hide the auto-generated submit button for Acrobat/Reader >= 9.0
if (app.viewerVersion >= 9)
showAutoGenSubmitBtn(false);
else
showAutoGenSubmitBtn(true);
I am not familair with JavaScript so I would apprecite if someone can help me how to edit it to make submit button visible.
Below is a complete JaveScrip of mentioned form.
Thanks
//@@FORMSWORKFLOW auto-generated script
AdobePatentID="B643"
var AdobePatentID = "AdobePatentID=\"B643\"";
// Show a dialog to ask the user's name and email during submit.
askUserIdentity = function(doc)
// string constants
var dlgStrings =
sDlgTitle: "Send Form",
sEmailLabel: "&Email Address:",
sNameLabel: "Full &Name:",
sSubmitLabel: "&Send",
sToLabel: "To:",
sSubjectLabel: "Subject:",
sSubjectContent: "Submitting Completed Form",
sAttachmentLabel: "Attachment:",
sFromLabel: "From:",
sErrorEmailRequired:"Please enter a valid email address.",
sErrorNameRequired: "Please enter your name."
var dlgElems = [];
dlgElems[dlgElems.length] = {
type: "view",
align_children: "align_left",
elements:
type: "view",
align_children: "align_row",
elements:
type: "static_text",
name: dlgStrings.sToLabel,
width: 80,
bold: true,
font: "dialog"
type: "static_text",
item_id: "sdto",
width: 270,
font: "dialog"
type: "view",
align_children: "align_row",
elements:
type: "static_text",
name: dlgStrings.sSubjectLabel,
bold: true,
width: 80,
font: "dialog"
type: "static_text",
name: dlgStrings.sSubjectContent,
width: 270,
font: "dialog"
type: "view",
align_children: "align_row",
elements:
type: "static_text",
name: dlgStrings.sAttachmentLabel,
bold: true,
width: 80,
font: "dialog"
type: "static_text",
item_id: "atch",
width: 270,
font: "dialog"
type: "gap",
height: 5,
width: 350
type: "static_text",
name: dlgStrings.sFromLabel,
bold: true,
font: "dialog"
type: "static_text",
name: dlgStrings.sEmailLabel,
bold: true,
font: "dialog"
type: "edit_text",
item_id: "emal",
width: 250
type: "static_text",
name: dlgStrings.sNameLabel,
bold: true,
font: "dialog"
type: "edit_text",
item_id: "name",
width: 250
type: "gap",
height: 5,
width: 350
type: "ok_cancel",
ok_name: dlgStrings.sSubmitLabel
var desc = {
resourceContext: "AcroForm",
description: {
name: dlgStrings.sDlgTitle,
elements: [
type: "view",
align_children: "align_left",
elements: dlgElems
desc.initialize = function(dialog)
var METADATA_ANNOT_NAME = "adhocFormState";
var PROP_INITIATOR = "initiator";
var initiator;
var annot = doc.getAnnot(0, METADATA_ANNOT_NAME);
if (annot != null) {
var arrProps = new Array();
arrProps = annot.contents.split(";");
initiator = getProperty(arrProps, PROP_INITIATOR);
var decodedFileName = unescape(doc.documentFileName);
var initVars =
sdto: initiator,
atch: decodedFileName
dialog.load(initVars);
desc.validate = function(dialog)
var values = dialog.store();
if (values.emal == "") {
app.alert(dlgStrings.sErrorEmailRequired);
return false;
if (values.name == "") {
app.alert(dlgStrings.sErrorNameRequired);
return false;
return true;
desc.commit = function(dialog)
this.result = new Object;
var values = dialog.store();
this.result.name = values.name;
this.result.email = values.emal;
var ret = app.execDialog(desc);
if (ret == "ok")
return desc.result;
else
return null;
askEmailClient = function(doc)
// string constants
var dlgStrings =
sDlgTitle: "Select Email Client",
sDlgText: "Please indicate the option which best describes how you send mail.",
sDesktop: "&Desktop Email Application",
sDesktopDesc: "Choose this option if you currently use an email application such as Microsoft Outlook Express, Microsoft Outlook, Eudora, or Mail.",
sInternet: "&Internet Email",
sInternetDesc: "Choose this option if you currently use an Internet email service such as Yahoo or Microsoft Hotmail. You will then need to save your form and return it manually to [email protected] using your Internet email service."
var dlgElems = [];
dlgElems[dlgElems.length] = {
type: "view",
align_children: "align_left",
alignment: "align_fill",
elements:
type: "static_text",
name: dlgStrings.sDlgText,
width: 350,
font: "dialog"
type: "radio",
name: dlgStrings.sDesktop,
item_id: "rad1",
group_id: "rgrp",
bold: true,
font: "dialog"
type: "view",
align_children: "align_top",
elements:
type: "gap",
width: 20
type: "static_text",
name: dlgStrings.sDesktopDesc,
wrap_name: true,
width: 342,
font: "dialog"
type: "radio",
name: dlgStrings.sInternet,
item_id: "rad2",
group_id: "rgrp",
bold: true,
font: "dialog"
type: "view",
align_children: "align_top",
elements:
type: "gap",
width: 20
type: "static_text",
name: dlgStrings.sInternetDesc,
wrap_name: true,
width: 342,
font: "dialog"
type: "gap",
height: 5,
width: 350
type: "ok_cancel",
var desc = {
resourceContext: "AcroForm",
description: {
name: dlgStrings.sDlgTitle,
width: 250,
elements: [
type: "view",
align_children: "align_left",
elements: dlgElems
desc.commit = function(dialog)
this.result = new Object;
var values = dialog.store();
this.result.send = values.rad1;
this.result.save = values.rad2;
var ret = app.execDialog(desc);
if (ret == "ok")
return desc.result;
else
return null;
AdobePatentID="B643"
// set a new property value to a property in the specified array.
setProperty = function(arrProps, propName, propValue)
var i;
var bSet = false;
for (i = 0; i < arrProps.length; i++) {
var propParts = new Array();
propParts = arrProps[i].split(":");
if (propParts[0] == propName) {
propParts[1] = propValue;
arrProps[i] = propParts.join(":");
bSet = true;
break;
if (!bSet)
arrProps[arrProps.length] = propName + ":" + propValue;
AdobePatentID="B643"
// get the value for a property in the specified array.
getProperty = function(arrProps, propName)
var i;
for (i = 0; i < arrProps.length; i++) {
var propParts = new Array();
propParts = arrProps[i].split(":");
if (propParts[0] == propName) {
return propParts[1];
return null;
AdobePatentID="B643"
showAutoGenSubmitBtn = function(bShow)
var autoGenSubmitName = "%AUTO_GEN_SUBMIT_NAME%";
var fld = this.getField(autoGenSubmitName);
if (fld != null)
var b= this.dirty;
if (bShow)
fld.display = display.noPrint;
else
fld.display = display.hidden;
this.dirty= b;
// Hide the auto-generated submit button for Acrobat/Reader >= 9.0
if (app.viewerVersion >= 9)
showAutoGenSubmitBtn(false);
else
showAutoGenSubmitBtn(true);I'm distributing the form in Acrobat Pro 9.
I created the form in Live Cycle Designer. Save, then open in Acrobat pro. Extend Features to Acrobat Reader, click the drop down box on Forms and hit distribute. I save a local copy. When I open the distributed form the buttons do fall silent, the Submit Button on the purple line up top still works, but that doesn't appear in reader and the people who will be completing the form all use reader. Any suggestions for a fix?
I'd like to distribute because that automates the tracking. It works undistributed. -
Hide the submit button programatically
Hi Friends,
i have standard page , in that, submit button is rendering programatically,i want to hide that submit button. do i need to extend standard controller to hide the submit button? here below code i have to hide the Activate button. can any one give guide to achive this solution.
standard controller process request code....
public void processRequest(OAPageContext oapagecontext, OAWebBean oawebbean)
super.processRequest(oapagecontext, oawebbean);
NegotiationCreationAM negotiationcreationam = (NegotiationCreationAM)oapagecontext.getApplicationModule(oawebbean);
String s = getCurrentStepCode(oapagecontext, oawebbean);
if(oapagecontext.isLoggingEnabled(1))
oapagecontext.writeDiagnostics(getClass().getName() + ".processRequest ", " currentStepCode " + s, 1);
mIsReviewPage = "Review".equals(s);
mIsItemDetailPage = "ItemDetail".equals(s);
mIsHeaderPage = "Header".equals(s);
mIsViewNetChangesPage = "ViewNetChanges".equals(s);
mIsUpdatePfValuesPage = "UpdatePfValues".equals(s);
if(!negotiationcreationam.isTemplate() || negotiationcreationam.isTemplate() && !mIsReviewPage)
OAWebBean oawebbean1 = oawebbean.findChildRecursive("SaveTemplateBtn");
oawebbean1.setRendered(false);
OAWebBean oawebbean8 = oawebbean.findChildRecursive("Activate");
oawebbean8.setRendered(false);
if(negotiationcreationam.isTemplate())
OAWebBean oawebbean2 = oawebbean.findChildRecursive("SaveBtn");
oawebbean2.setRendered(false);
if(mIsReviewPage)
OASubmitButtonBean oasubmitbuttonbean = (OASubmitButtonBean)oawebbean.findChildRecursive("Activate");
oasubmitbuttonbean.setRendered(true);
String s1 = null;
if("ACTIVE".equals(negotiationcreationam.getTemplateStatus()))
s1 = oapagecontext.getMessage("PON", "PON_TEMP_INACTIVATE", null);
else
s1 = oapagecontext.getMessage("PON", "PON_TEMP_ACTIVATE", null);
oasubmitbuttonbean.setLabel(s1);
oasubmitbuttonbean.setText(s1);
if(!mIsHeaderPage || negotiationcreationam.isTemplate())
OAWebBean oawebbean3 = oawebbean.findChildRecursive("ApplyTemplateBtn");
oawebbean3.setRendered(false);
if(!mIsUpdatePfValuesPage)
OAWebBean oawebbean4 = oawebbean.findChildRecursive("ApplyPfValuesBtn");
oawebbean4.setRendered(false);
if(mIsReviewPage)
setPageBtnsForReviewPage(oapagecontext, oawebbean);
if(!negotiationcreationam.isTemplate())
setEditButtons(oapagecontext, oawebbean);
if(negotiationcreationam.isAmendment() || negotiationcreationam.isMultiRoundDocument())
OAWebBean oawebbean5 = oawebbean.findChildRecursive("ReviewChangesBtn");
oawebbean5.setRendered(true);
if(mIsViewNetChangesPage)
setPageBtnsForReviewPage(oapagecontext, oawebbean);
OAWebBean oawebbean6 = oawebbean.findChildRecursive("EditBtn");
oawebbean6.setRendered(mDocIsEditable);
OAWebBean oawebbean9 = oawebbean.findChildRecursive("ViewDocumentBtn");
oawebbean9.setRendered(true);
OAWebBean oawebbean7 = oawebbean.findChildRecursive("OkBtn");
oawebbean7.setRendered(mIsItemDetailPage);
OAWebBean oawebbean10 = oawebbean.findChildRecursive("ReviewBtn");
oawebbean10.setRendered(!mIsItemDetailPage && !mIsUpdatePfValuesPage && !mIsReviewPage && !mIsViewNetChangesPage);
if(!mIsItemDetailPage && !mIsUpdatePfValuesPage && !mIsReviewPage && !mIsViewNetChangesPage)
addSideBar(oapagecontext, s, negotiationcreationam.isTemplate());
private void setEditButtons(OAPageContext oapagecontext, OAWebBean oawebbean)
if(oapagecontext.isLoggingEnabled(1))
oapagecontext.writeDiagnostics(getClass().getName() + ".setEditButtons ", " mDocIsEditable " + mDocIsEditable, 1);
if(!mDocIsEditable)
OAWebBean oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("HeaderEditButton");
oawebbean1.setRendered(false);
oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ItemsEditButton");
oawebbean1.setRendered(false);
oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ControlsEditButton");
oawebbean1.setRendered(false);
oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ContractsEditButton");
if(oawebbean1 != null)
oawebbean1.setRendered(false);
oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("SuppliersEditButton");
oawebbean1.setRendered(false);
Thanks in advance,
vamshiVamshi,
Extending CO would anyways be required in either of the approach. Now let me brief you which approach you can use :
1) If you need to hide the submit button while rendering of page, based on some logic, you can ahead with your approach extending the CO and in process request get refrence of submitbutton bean and use API, setRendered(false);
2) If this button needs to be hidden on some logic on a post event on the page i.e. in process form request, its better to have a tranient attribute and a PVO approach u worked on tutorial.
Apprach 1 can be used in case 2 also but in that case you would have do an extra looping on the page, by redirecting to same page retaining the AM. I hope this helps up to decide the approach.
--Mukul -
Hide and Display submit button on the Simple search page.
Heading 1: h1 Hide and Display submit button on the Simple search page.
I'm trying to set the enabled property of the submit button on the simple search page. The business case is to disable the button if the VO has not returned any rows.
The Submit button is on the page button bar.
regards
AbhiHi,
I have already added this in my ProcessRequest, the issue I am facing is it the submit button is disabled while I load >the page which is fine. but when I do a search and the query returns rows still the submit button is disabled.---Will nt reuired SPEL here..
---On go button click setsession value.
Follow below steps:
CO PR:*
OASubmitButtonBean continueBtn=(OASubmitButtonBean)flowLayout.findChildRecursive("continueBtn");
if(continueBtn != null && "D".equals(oapagecontext.getSessionValue("Flag"))
continueBtn.setDisabled(false);
else if(continueBtn != null )
continueBtn.setDisabled(true);
CO PFR:_
if(pageContext.getParameter("Go") != null)
oapagecontext.putSessionValue("Flag","D");
Regards
Meher Irk
Edited by: Meher Irk on Mar 22, 2011 7:48 PM
Edited by: Meher Irk on Mar 22, 2011 7:48 PM -
How do I hide the submit button?
I want a print button, not a submit button. People have to fill out the PDF, then print it.
If you go to the file menu and Save to PDF form you will be given an option to not use FormsCentral to collect data. When you select that option no submit button will be added to the form.
Randy -
How can I get one Submit button to perform three actions?
I have a 2-page form. One page is completed by an HR person, entering fields that describe a new role, new pay, new hours or a new location for an existing employee. The second page automatically repeats the name, location and job role fields, but also completes the IT requirements linked to the job role (such as whether or not the role needs access to a particular piece of software or not).
The users of the form will have varying degress of IT capability. I wan to enable them to press a single Submit button that does three things: first, print the first page of a two-page form AND e-mail the same page to one e-mail address. Second: e-mail the second page only to a DIFFERENT e-mail address.
I am not a Javascript expert - or even a beginner. Can anyone help? I need to get this ready for Tuesday! Thanks in advanceYou will need two buttons on your form to be able to do this.
One is the actual submit button (this will interact with th email system and do the submit). Note that you cannot write programs on a submit button. You will need to make this button invisible to the user. The second button will be a regular button which you can write programs on. Use teh click event of that button. This one will have logic to accomplish the things that you want ...here is some pseudo code to do this:
use print command and one of the parms indicates which pages to print.
Set up the submit button to hold the email address of the person recieving it.
Programmatically click the hidden submit button.
Note that the user will recieve a dialog from the mail client to OK before teh form will be sent.
Set up the submit button to change the email address
Programmatically click the submit button again
User will recieve another dialog to OK the email submission
Also you cannot email part of the form it will have to be the whole form. You coudl get a little more sophisticated and hide parts of the form but the whole form will be sent with the emails. This will need more programming on your part.
Paul -
Hiding submit button from an Infopath form in a Sharepoint Library document
I have a Sharepoint document library that is setup to collect submissions from a form that faces the public. Because it faces the public it needs to have the standard/familiar submit button. The problem is that when the form is submitted to the
document library and the document is reviewed, it still contains the button - which will be confusing/complained about by staff.
I attempted to use a hidden boolean field that would switch to "True" when the submit button is clicked and then use conditional formatting to hide the button before submitting through the data connection. But apparently, there is no way
to move the conditional formatting rules after the action rules that make the boolean swith.
I then tried to switch to a new view that was identical to my Main view before submitting but the button is still appearing on the submitted documents in the form library.
I'm wondering if anyone has experience with this? I have to think I'm missing something obvious.Please try this -
https://social.msdn.microsoft.com/Forums/en-US/5767ff6c-764d-479c-904e-22e40a697c6c/how-to-hide-custom-submit-button-after-form-has-been-submitted-infopath?forum=sharepointcustomizationlegacy
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful. -
Call BADI on click of a submit button in ESS
Hi All,
I am trying to call a function module ( i.e through BADI ) in a different browser by clicking on a submit button in Travel & Expenses Iview in ESS ( EP 6.0 ) but i didn't see any new window/ browser opened when i clicked on submit button.
The BADI is activated and its working fine because the same functionality is working good when i tested this through trans. code PR_WEB_1200. When i clicked on a submit button, a new browser was opened and the form was displayed the way we want in a different browser.
But when i tested the same in ESS, i couldn't see any new browser or window opened. If the BADI was called when i clicked on the submit button atleast a new browser has to open with a blank page.
Please guide me, If anybody knows, how to call a function module in a new browser by clicking on a button in ESS - Portal.
Thanks.
AnilHi Jayesh,
You can use the BADI BBP_CUF_BADI_2 to change the display from customer-defined fields to the SAP standard screen. This BAdI enables you to control whether the fields can be edited, and how they are displayed.
MODIFY_SCREEN method will Show/hide field display and restrict edit options.
For more information on BADI please go to SPRO -> BADI.
OR View the information on BADI's.
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
Hope above proves helpful to you.
Regards,
Rajeshree. -
I have a 5 page form and I need each page to go to a different email adress. I have put a different email submit button on each page, but is there a way to script the button to only send the current page and not any of the others? Or have one main email submit button that sends each page to a different email address? I am new to Adobe LiveCycle Designer ES, but I have a (VB) programming background, so it seems like it should be possible with code Thanks
Adobe LiveCycle Designer ES ver 8.2Hi,
The submit by email function will attach the complete form to the email. It cannot (afaik) split a form into five different PDFs.
However there are workarounds.
If you save the form as a Dynamic XML form in the save as dialog, then you can show and hide pages.
Here is an example of a form that changes the presence property of pages, depending on the choice selected from the dropdown.
http://www.assuredynamics.com/index.php/category/portfolio/showing-and-hiding-pages/
When it comes to something like this it is helpful to split the script. The mouseUp event fires before the click event.
For example for the email button on page 1, you can modify the script in the example to hide each of the pages 2-5 in the mouseUp event and then in the click event have the email script. In the postSubmit event you could have script to show all the pages again.
A word of caution - if the user has Reader then the form needs to be Reader Enabled, otherwise the submit as PDF will fail silently.
Hope that helps,
Niall
Assure Dynamics -
I need to email a PDF form to any person I want to. But when you add the Email Submit Button to the form it requires you to enter an email address. What if the email address is different every time? Is there a way to add an Email button so when the form user clicks on the Email button it brings up Microsoft Outlook and you can type in any email address that you want?
You need to have an email submit button that, when clicked, sends the email.. but you can set properties of that button and trigger it from another button. So hide EmailSubmitButton1 (or whatever it's called), create a new button, and add script like this:
// Set whatever address you like in the mailto: line
EmailSubmitButton1.resolveNode("#event.submit").setAttribute("mailto:[email protected]?subject=h i there", "target");
EmailSubmitButton1.execEvent("click");
This finds the submit button's submit node and sets it's target property to whatever you specify, and then clicks it.
Steve Tibbett, Developer
Adobe Systems -
How to hide all button except one in a PageButtonBar
Hello,
I am newbie to OAF.
And i am trying to do is, when i would clink on a submit button of my Update page(page is using Train. All the buttons are in a TrainFooter Region, whose lay out is pageButtonBar and Submit button only visible when i am on the last page of train, i.e. Summary Page) then all the button except one (Back to Search Page) will get hide.
Pls let me know where i need to work to do this, i try to do it in PR but no change get reflect.
Thanks,
UditHello Abdul,
Yes, i want only "Back to Search" Button on last page when i press "Submit" Button.....but before pressing submit...all button should be there on Summary(last) page except "Back to Search" Button....and when i press Submit Button then only page buttons get hide without any change in whole pageLayout.
Here is CO of my TrainFooter===========
PR====
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean);
OATrainBean trainBean=
(OATrainBean)pageContext.getPageLayoutBean().getLocation();
trainBean.prepareForRendering(pageContext);
int step = trainBean.getSelectedTrainStepRenderedIndex();
if(step + 1 != trainBean.getNumberOfRenderedTrainSteps()){
OASubmitButtonBean submitButton =
(OASubmitButtonBean)webBean.findIndexedChildRecursive("Submit");
submitButton.setRendered(false);
PFR==========
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
super.processFormRequest(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean);
if (pageContext.getParameter("Cancel") != null)
pageContext.forwardImmediately("OA.jsp?page=/oracle/apps/ak/Emptry/webui/EmpTrySearchPG",
null,
OAWebBeanConstants.KEEP_MENU_CONTEXT,
null,
null,
true, // retain AM
OAWebBeanConstants.ADD_BREAD_CRUMB_NO);
if(pageContext.getParameter("Submit") != null){
am.getOADBTransaction().commit();
throw new OAException ("Current Record is Updated!!", OAException.CONFIRMATION);
Pls let me know in any other confirmation.
Thanks,
Udit -
I have created a fillable web form using the FormsCentral app on my mac.
It has a couple of required fields, and a couple of show/hide fields.
It tests perfectly, and we sent out a link to the formscentral link to all staff and for some people it does not work. They can see the form and fill in data, but the show/hide stuff doesn't perform correctly and the submit button doesn't work.
Works for me in Safari and Firefox, and seems sketchy in IE - works for some but not others.
Any thoughts?The first thing to confirm is that the form is an HTML/web form and not a PDF embedded in the browser, if it is a PDF please see this FAQ: http://forums.adobe.com/docs/DOC-4142
Assuming you or your customers/users are having problems submitting the HTML/web form - the most common cause of show/hide logic not working and the Submit button not working is Javascript is not enabled in the web browser.
Some things to try (since instructions for each item vary per browser google the steps for the browser you are using):
Confirm that Javascript is enabled (required for FormsCentral forms):
http://www.javatester.org/javascript.html
Clear the browser cache
Try disabling browser plugins
If using Internet Explorer check to see if the page is in "Compatibility View" mode and if so try turning it off
Try a different web browser
I know that this is made more difficult by the fact that it is not you reporting this issue but your customers and you may not have acess to try the steps above...
If these steps don't resolve the issue please respond with the operating system you are on (Mac or Windows) and which web browser and version you are using.
You can send me the URL to your form at [email protected] so I can try in IE on Windows to confirm that in general it works (or identify an issue if it does not).
Thanks,
Josh -
Reader Extension and Submit Button
Hi,
I reader extended a form with the Reader extension web application.
The issue is when I start the process in the workspace and my form is open, the submit is not embed anymoe in the workspace.
How could I fix that ?When a PDF Form is shown in Workspace, the LC server actually attempts to make a modification to the form (called "augmentation") in which a scripting bridge is added to the form. This happens inside the Render Service used to show the form. Workspace needs this to happen so that it can instruct Acrobat/Reader in the browser to hide the submit button, thus allowing the Workspace UI buttons to be used instead. I know that if the PDF Form is signed then LC will not attempt to make this modification in case it breaks the signature. This is what might be happening here because when you reader extend a PDF there is actually a signature applied.
If this is the cause I can think of two suggestions off hand:
- You might consider Reader Extending the Form on demand as part of your render service by uploading your Reader Extensions Credential (the p12 / .PFX file) to Trust Store and then using it with the Reader Extensions Service in a new version of your render service.
- You can use LC Designer to add the "Form Bridge" to your form before you reader extend it with the web application and place it in your repository.
Maybe you are looking for
-
I am switching over to apple from a PC platform and I have tried to use migration assistant to transfer the stuff on my PC to my macbook pro. When i tried the first time the two went to sleep due the long time required to transfer 13 GB of data and t
-
PR type generated by maintenance orders
Hi Gurus, Where do you defined the type of purchase requisition generated by maintenance order ? Is it possible to have different types of PR depending on the material type of the component in the maintenance order ? Cheers Olivier
-
How to programmatically add users to WLS 7
Is there a way to programmatically add users to Weblogic 7? I'm building up a website and want to give my visitors an opportunity to register with the site. The code samples I found until now are not working cheers, michael
-
How do I remove a purchased app completely,
How do I remove a purchased app completely,from all apple devices
-
How to obtain richtextbox whose height adjusts to the appended text automatically without having scrollbar