Field on Life Cycle Form

Hi, I'm trying to populate a field on a life cycle form from a URL. I found this snippit of could on the web, but I can't seem to get working in forms. I believe the this.getfield() is the line that doesn't work.
Any help would be greatly appreciated.
thanks in advance...Dave
----- form::docReady - (JavaScript, client) --------------------------------------------------------
myForm = event.target;
paramString = myForm.URL.substr(myForm.URL.indexOf("?")+ 1)
if (paramString.length > 0 )
          parameters = paramString.split("&")
          for each (parameter in parameters)
                    //create an array of key/value pairs
                    kvPair = parameter.split("=")
                    //set the field named "key" to "value"
                    fieldName = unescape(kvPair[0])
                    this.getfield(fieldName).rawValue = unescape(kvPair[1])

Hi,
the  this.getfield(fieldName).rawValue = unescape(kvPair[1]) is how Acrobat JavaScript works this may need to be converted to LiveCycle Designer JavaScript which is of a format
subformX.subformY.subformZ.resolveNode (fieldName).rawValue = unescape (kvPair[1]);
Where the subformX, Y and Z are the actual names of the subform that provide the route to the field that you wish to add the value to. 
hope this helps
Malcolm

Similar Messages

  • Problems with Safari, Acrobat, Intel Macs, and Life Cycle Form Mgr.

    Here is my problem:
    A Mac user using 10.4.10, with Acrobat Standard Ed v.7.0.9 installed,
    is having to approve purchase forms through Adober Life Cycle Form Manager
    through Safari 2.0.4. When trying to approve the PDF forms, it tells her
    she needs to have Acrobat v.7 installed, and only shows a white page.
    Went back and launched Acrobat 7.0.9, and did the "Detect and Repair"
    setting to verify the Adobe PDFViewer plugin was installed.
    Said it was, checked the Library/Internet Plugins folder and it was.
    Launched Safari, Safari's list of plug-ins does not show it as being installed.
    Trashed the Safari .plist file, relaunched Safari, same thing.
    Read on the Apple site that people were experiencing similar issues,
    Read on Adobe's site that for Intel Macs, should be using v. 8.01.
    Downloaded the 8.01 Acrobat Reader and installed it.
    re-launched Safari, success, it says the plugin, v.8.01 is installed.
    Go back to Adobe Life Cycle Forms Manager, go to view a PDF,
    at 100% screen size, PDF shows correctly. Zoom in on details,
    PDF goes blank, will not show details. Zoom back out,
    PDF goes white page, no info displayed.
    My Questions:
    1. is it an issue with Adobe Life Cycle Forms Manager and Safari on Intel Macs?
    2. Is there a way to get a proper plug in for Safari, so that Acrobat will read the PDFs
    instead of the default Preview?
    thanks in Advance

    bump
    anybody running ALCFM and Acrobat 8 with an Intel Mac,
    are you running into issues with approval of PDF forms?

  • Where in the MIDlet life-cycle should I create multiple forms with LWUIT ?

    Hi all,
    I must create two LWUIT forms in my application. Where should I create the two forms ? I created the first form in the startApp life-cycle method , and when I tried to create also the second form in the startApp method then there is a NullPointerException raised when running the application !
    So where , or how , should I create the second form ?
    Thank you very much indeed
    Edited by: andrianiaina on May 20, 2011 1:59 AM

    I think the problem here is that Arlhoolie wants all of the different TEBs to behave as if they were part of a single interaction that submits only ONE result to the quiz.  Using multiple TEBs in Captivate means that you have multiple scored objects and therefore multiple results being submitted to the quiz.
    If you want a single Success or Failure result submitted to the quiz based on the results from multiple interactive objects then there really is no simple way to do it.  But you could try using the Infosemantics Interactive Master widget to combine all the TEBs as slave objects that report to the Master Widget, which then reports a single score to the quiz based on the results from the slave objects.
    You can learn more about the Master widget here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/interactive-master
    http://www.infosemantics.com.au/interactivemaster/help
    You can download a free trial version of the widget here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/download-free-trial-widgets
    One caveat you should be aware of is that this widget is not HTML5 compatible.

  • Designing issue in Adobe Life Cycle in interactive form

    Hi,
      My design in Adobe Life Cycle is like,I have to show one image in left corner of the page and giving header and footer
    by using Static Text from Library.I have created the designing and running this application ,it is running fine.But my requirement is i have  to show 50 pages and each page should have same header and footer.How can i do it ?
    And how i will break the pages in to 50 pages.
    Thanks & Regards
    Muna

    Open the PDF file
    Click Ctrl+D (which opens up properties diaglo box)
    Switch to Security Tab
    Change security method to No Security
    If it asks for password - provide the password
    Click Save
    Try to re-open the PDF to ensure that it does not ask you to enter password
    now open the PDF file using LC Designer
    HTH
    --Santosh
    http://about.me/nskumar

  • Adobe Life Cycle Designer doesnt show Context Data

    Hi All,
    I have a requirement where I have a add a new field to the adobe form . I am able to add the new field but when I try to Bind it with the Context I am unable to see any context in the Adobe life cycle designer can anyone please let me know how to do this .Thank you so much in advance.

    [https://websmp103.sap-ag.de/swdc] goto this url and click on the installations and upgrade drop down to your left part of the screen --> then click on the search for installations and upgrades then type Adobe in the search box and press enter you will find all the Life cycle designer versions click on
    [NW 7.0 Presentation - Adobe LiveCycle Designer 8.0] this software will be added to the download basket.
    And you should have authorization for downloading the software your basis person should have access to the same..

  • Creation of BP through Web UI.with Life cycle stage concept.

    Hi,
    I am working on Life cycle stage.
    I have added the field " Life cycle stage" field in the Web UI.
    But now when i go to create a BP with a life cycle stage XXX, it throws a error saying "BP category 1 does not fit the data in category 2" and "Data contains errors and cannot be saved"
    Please help me in saving the BP thr web UI.
    Regards,
    Vinay

    Hi Tariq,
    I'm not sure if you have the latest SP - recently, a new BADI - BUPA_SET_DEFAULT was released which allowed defaulting of fields in the BAPI and Web UI scenarios. You can use that BADI to default the fields for country, name, and even other address fields on the Web UI.
    If you don't have this BADI in your system, do search for SAP notes, which will also have the documentation about this.
    Hope this helps you.
    Regards,
    Rishu.

  • How to Install ADOBE life cycle designer

    Hi All,.
    I am new to ADOBE forms, Please let me know how to install ADOBE life cycle designer step by step.
    Thanks&REgards,
    Archana.G

    Download the installer from Service Marketplace (http://service.sap/com/swdc). Use the search screen to search for Adobe LifeCycle Designer. You will get a compressed file with a .zip extension. Unzip that into a folder and you will find a exe called SapAldSetup.exe Double click it and the rest is cake walk.
    Thanks,
    GLM

  • Pdf live cycle  form through sap abap editor to validate user input by java script coding

    I am new to apply a java script in a Adobe form.
    So i need of help that i have 9 page form of HR module i need to verify every blank field and wrong entry field also.
    I look around a lot of code but still i am not able to perform good validation in a Adobe form.
    I am using SAP ABAP editor where i am making through PDF Live cycle FORM & try to put java script validation on the field.
    My problem is that how can i link or configured to Adobe form.
    Here are some event are given "mouseup","validate" or more are given.So how i can do.
    i wrote the code like
    / Get the field value
    var f1 = this.getField("VORNA");----why it is not working.Some thing is wrong?
    var v1 = f1.valueAsString;
    if (v1) {
    } else {
       app.alert("Field: " + f1.name + " is blank.", 1);
    //above code is not working.
    but here we used rawValue() method it works , but it popup message  javascript with window error.
    if( this.rawValue()==' ' || this.rawValue==null)---------this works
    xfa.host.MessageBox("First name is blank!");---------this works
    "VORNA" is "First name" field name binding with this value.
    How we can linked java script file with Adobe form.
    Kindly help me

    You're mixing code for an acroform with code for an XFA form. SInce you're creating the form with LiveCycle Designer, it wold be better if you posted this to the LiveCycle Designer forum, if you haven't already.

  • Form fields remain interactive after form is saved

    I have built a number of forms by importing static pdf's in to Live Cycle and applying the form fields and scripts there. Now I am finding that if I save the form and then go to Acrobat XI to enable the form so that Adobe Reader users can fill it out, then when they do fill out the form and save it the result still has all of the interactive form fields of the original form.
    The objective would be that the user opens the interactive pdf, fills it out, hits a Save As button, and the form will save as a static copy with their information in it and the original interactive pdf will remain and can be closed without saving their personal data.
    I do have the option of forcing the user to print instead of save, but the user is then prompted if they want to save changes when they finish printing and go to close the original.
    This was not an issue previously, so I would like to know exactly what I am missing in this very basic step.

    Hi;
    All of the fields in the downloaded "response PDF" are marked "Read Only".  You can change this using Acrobat by editing the form and unchecking the "Read Only" box in the form field Properties dialog box.
    Thanks,
    Josh

  • ADF application life cycle

    Hi,
    Can any one tell me how the life cycle of an application is taken care in ADF application?
    I have an ADF application. Once I logout of the application, and click internet browser 'Back' button to come to a page which needs the DB interaction, I need my application to go to 'Logout' page again and remain in there until I again login, because actually I am out of my application. But at present I do get the following error.
    javax.faces.el.EvaluationException: Error setting property 'form1' in bean of type..java.lang.NullPointerException
    I have the following code when I logout of the application.
    FacesContext ctx = FacesContext.getCurrentInstance();
    ExternalContext ectx = ctx.getExternalContext();
    HttpServletResponse response = (HttpServletResponse)ectx.getResponse();
    HttpSession session = (HttpSession)ectx.getSession(false);
    session.invalidate();
    response.sendRedirect("CRLIF001.jsp");
    ctx.responseComplete();
    return null;
    Is there any code that I need to write to fix this? Could any one please help me?
    Thanks,
    Venki

    Hi,
    actually it does what you tell it to do: It deletes the session and as such the form is not available. You may be able to use a servlet filter that checks the session ID and the user authentication. If you detect that the session has changed or the user isn't authenticated, you redirect him to the page you want
    Frank

  • Managed beans life cycle

    Hi,
    I thought I had a good grasp on <managed-bean> concept, but I wanted to understand better their life cycle since JSF framework takes care of it. JSF documentation doesn't seem to be very explicit on when exactly managed beans get created, when they get initialized, and when they are put into appropriate scope.
    I have an application that consits of large number of form (JSPs), close to 8 thousand JSPs. Depending on the usage scneario, it can use anywhere from 100 to 1000 of them at a time. I pretty much have one backing bean per one JSP page (form). Obviously, all 8 thousand backing beans would be declared in the faces-config.xml. I would like to make sure that only a few hundred of them are instantiated for each usage scenario as I only go through that many pages.
    Any help would be greatly appreciated.
    Thanks in advance,
    Vadim.

    Managed beans are created lazily - only when explicitly requested - and then immediately placed in scope. They will not be re-created until that scope goes away or their reference in that scope is explicitly nulled out.
    -- Adam Winer (EG member)

  • Life cycle or whatever it is...

    I think the reason why this doesn't work has something to do with the life cycle...
    The point is I need to render only the fields related with the selectedItem in the selectOneListbox and all the rendered items are required.
    My problem is, when the SelectedItem is selected all the fields shows the 'blank field' message and it doesn't render the fields related to the chosen selected item. The feeling I have is that the value associated with the selectOneListbox never updates...
    Here is a selectOneListbox where the value "#{editInterfaceBean.networkInterface.linkType}" is associated with the item selected (or should be...)
    <h:outputLabel for="linkType">
         <h:outputText value="#{msgs.linkType}:" />
         </h:outputLabel>
         <h:selectOneListbox id="linkType"
              size="1"
              onchange="submit()"
              immediate="true"
              value="#{editInterfaceBean.networkInterface.linkType}">
              <f:selectItems value="#{editInterfaceBean.linkTypes}" />
         </h:selectOneListbox>
         <h:panelGroup />Look that the required and rendered fields are associated with the same method:
    <h:outputLabel for="dslLogin"
    rendered="#{editInterfaceBean.dsl}">
         <h:outputText value="#{msgs.login}: " />
         </h:outputLabel>
         <h:inputText id="dslLogin"
              value="#{editInterfaceBean.login}"
              rendered="#{editInterfaceBean.dsl}"     
              required="#{editInterfaceBean.dsl}">
         </h:inputText>
         <h:message for="dslLogin" styleClass="errorText"
              rendered="#{editInterfaceBean.dsl}"/>This is the method that the rendered and required field are associated with. Observe that it return the value associated with the value field on the selectOneListbox.
    public boolean isDsl() {
         return this.networkInterface.getLinkType().equals("dsl");
    }

    Hi guys! Well, I tried the valueChangeLisener, didn't worked. In the end I decided to send global messages, validating in the bean, not in the page... it's not really the best thing to do but... works.
    Thanks anyway!

  • Creator Page Life Cycle Callback Methods

    Hi,
    In JSC Field Guide, we can read that in with JSC 2 we can use Page Life Cycle Callback Methods.
    It 's a good thing but what about compatibility with JSF implementation ?
    Best regards,
    Regis

    Hi,
    Could you please explain what you mean by "compatibility with JSF implementation"?
    Cheers
    Giri

  • SAP HCM Life Cycle

    Hi Expert,
    Can anyone help me with the life cycle stages of SAP HCM.
    I have a student who asked me what is the concept of SAP HCM, I explained about where was it started, what is the architecture, why is SAP preferred against other applications, modules covered, logic of integration... I would like to know if I am missing on anything as far as Concept is concerned.
    Thank you in Advance.
    Sejal

    Hi,
    There is nothing as such called lifecycle of SAP HCM.
    It is similar to an ERP application, and basically your organization first decides which of the ERP module they are going to implement, once they have decided to go for HCM, they wil opt for it.
    Again in HCM it depens on customer which module he is going to implement and HCM is vast it inlcudes PA, OM, TIME, PAYROLL, BENFITS, TRAVEL MANAGEMENT, LSO, Performance management, HR Forms and Processes etc.
    This implmentation has a life cycle - like
    Requirement gathering, Blue printing, Realization, implementatin (Configuration and coding), Custom implemenation, Integration if required, Testing (includes, UT, SIT and User acceptance testing), Documentation and hence Go Live.
    This is a huge process and requires domain / business / technical/ functional / Quality / Knowledge experts.
    Hope it helps you.
    Thanks & Regards, Swapnil Mishra

  • Page life cycle problem

    We suspected af:tree had a bug but we observed during debugging that our problem is due to page life cycle and we are searching a way to solve it at the best :
    Our problem is the following :
    1) we have in the same page a af:tree linked to a java bean data control that present some content in a hierarchy form (link an index) and a second part that contains some ui that represent the selected af:tree node content (linked java bean content). The second part ui's are updateable
    2) when we first load the page the af:tree is correctly rendered and we are able to navigate into into it without any problem (expand/collapse). The ui's are empty because we didn't select anything
    3) when a node is selected in the af:tree the correspoding data are loaded in ui's. That is perfect.
    4) when a second (another) node is selected we discovered that
    4.a) the af:tree was positioned to the new node selected that mean that we changed the context in our java bean
    4.b) the changes previously done in ui's were executed (eved nothing was edited) in the java bean and that in the wrong context.
    This situation cause a mismatch in our java bean data
    What is the best way to solve this ?
    Is this described somewhere in the documentation how to solve such problem in a same page ?
    Is ppr the way ?
    Thanks in advance

    Hi Frank
    What I was missing is that when a node is selected, a code from node details is setted as a parameter in the page, the page (outcome null in af:tree) is refreshed that will cause the ui's method binding to be executed again but after the parameter is setted. The ui's are built from the result a method that will get the corresponding java bean based on the parameter.
    is this data queried by you or is it part of the tree node information or detail leafes?
    They code is part of the tree node. It is setted into a page parameter. The ui's data is getted from a method (see below method iterator, methodaction from the page definition).
    When you say data gets executed upon changing the tree row focus, what does this mean? Do you have a submit defined upon focus lost for the tree?
    ui's binding is executed. The setter's are executed.
    So what is the desired behavior you are looking for ?
    The setter have to be executed before the java bean context is updated, i mean before the binding to the method action is executed
    Actually i have, when i click on a node in a previously loaded page:
    1) click on node
    2) set the parameter from selected node
    3) refresh the page
    4) execute what we can name a java bean finder method (a java bean method that select a xml node in xml java bean using jxpath with a xpath expression that is executed from the method action in the page definition)
    5) execute the setter from the binding (but into the wrong java bean because the method action change the java bean context)
    In fact, 5) has to be executed before 4) is executed
    That is my problem
    af:tree code :
                  <af:tree value="#{bindings.ClassificationEntryListclassificationEntry.treeModel}"
                           var="node">
                    <f:facet name="nodeStamp">
                      <h:panelGroup>
                        <af:commandLink text="#{node}">
                          <f:param name="selectedEntry"
                                   value="#{node.classificationEntryCode}"/>
                        </af:commandLink>
                      </h:panelGroup>
                    </f:facet>
                  </af:tree>Page definition :
    <?xml version="1.0" encoding="UTF-8" ?>
    <pageDefinition xmlns="http://xmlns.oracle.com/adfm/uimodel"
                    version="10.1.3.39.84" id="untitled1PageDef"
                    Package="view.pageDefs">
      <parameters/>
      <executables>
        <iterator id="ClassificationDocumentDataControl_rootIter" RangeSize="10"
                  Binds="root" DataControl="ClassificationDocumentDataControl"/>
        <accessorIterator id="classificationIterator" RangeSize="10"
                          Binds="classification"
                          DataControl="ClassificationDocumentDataControl"
                          BeanClass="classification.testcase.castor.Classification"
                          MasterBinding="ClassificationDocumentDataControl_rootIter"/>
        <accessorIterator id="classificationEntryListIterator" RangeSize="10"
                          Binds="classificationEntryList"
                          DataControl="ClassificationDocumentDataControl"
                          BeanClass="classification.testcase.castor.ClassificationEntryList"
                          MasterBinding="classificationIterator"/>
        <accessorIterator id="classificationEntryIterator" RangeSize="10"
                          Binds="classificationEntry"
                          DataControl="ClassificationDocumentDataControl"
                          BeanClass="classification.testcase.castor.ClassificationEntry"
                          MasterBinding="classificationEntryListIterator"
                          Refresh="ifNeeded"/>
        <variableIterator id="variables"/>
        <methodIterator id="findClassificationEntryByIdentificationIter"
                        Binds="findClassificationEntryByIdentification.result"
                        DataControl="ClassificationDocumentDataControl"
                        RangeSize="10"
                        BeanClass="classification.testcase.castor.ClassificationEntry"/>
      </executables>
      <bindings>
        <tree id="ClassificationEntryListclassificationEntry"
              IterBinding="classificationEntryIterator">
          <AttrNames>
            <Item Value="classificationEntryCode"/>
            <Item Value="classificationEntryCount"/>
            <Item Value="valid"/>
          </AttrNames>
          <nodeDefinition DefName="classification.testcase.castor.ClassificationEntry"
                          id="ClassificationEntryNode">
            <AttrNames>
              <Item Value="classificationEntryCode"/>
            </AttrNames>
            <Accessors>
              <Item Value="classificationEntry"/>
            </Accessors>
          </nodeDefinition>
        </tree>
        <methodAction id="findClassificationEntryByIdentification"
                      InstanceName="ClassificationDocumentDataControl.dataProvider"
                      DataControl="ClassificationDocumentDataControl"
                      MethodName="findClassificationEntryByIdentification"
                      RequiresUpdateModel="true" Action="999"
                      IsViewObjectMethod="false"
                      ReturnName="ClassificationDocumentDataControl.methodResults.ClassificationDocumentDataControl_dataProvider_findClassificationEntryByIdentification_result">
          <NamedData NDName="entryIdentification"
                     NDValue="#{param.selectedEntry}"
                     NDType="java.lang.String"/>
        </methodAction>
        <attributeValues id="classificationEntryCode"
                         IterBinding="findClassificationEntryByIdentificationIter">
          <AttrNames>
            <Item Value="classificationEntryCode"/>
          </AttrNames>
        </attributeValues>
      </bindings>
    </pageDefinition>Hope it is a little bit more clear

Maybe you are looking for