<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=269747997384049&amp;ev=PageView&amp;noscript=1">

AVIO Insights

Oracle BPM 12.2.1 ADF Auto-Generation Issue Solutions

Others may disagree, but I am a fan of creating the first cut of ADF forms for Oracle BPM using the human task's auto-generation feature.  While this worked well in previous releases, in 12.2.1.1, 12.2.1.2 and 12.2.1.3 small manual edits are now needed to eliminate the errors on the generated form.

There are now two types of errors caused by 12.2.1.x auto-generation - edAttTy errors and duplicate ID errors. 

Patches

While this blog describes the manual edits you can make to the auto-generated .jspx files to correct the issues:

  • If you are on 12.2.1.1, you can request a backport against bug 24683218 and then apply the patch provided.  Until this patch is provided, continue to manually edit the generated .jspx files as described below.
  • If you are on 12.2.1.2, you can apply patch 25333619 to prevent auto-generation errors from occurring.
  • If you are on 12.2.1.3, you should only get the "duplicate ID" errors described below.  I have not tried it yet, but Support suggested applying patch 26317255 to prevent these auto-generation errors from occurring.  If this does not work, manually edit the generated .jspx files as described below.

edAttTy Errors

The first type of error on the generated page causes "Referenced id edAttTy does not exist" errors throughout the form:

Image removed.

Although customer support document Doc ID 2192543.1 describes the issue, this describes how the forms can be fixed.  

1. In JDeveloper, click the Source tab at the lower left corner of the form that has the error. 

Image removed.

2. Scroll down and note the errors on the page.

Image removed.

All of the errors are caused by the auto-generation bug that did not create an element on the form with the id edAttTy.  To work around this issue, this text will be added to the ADF form:

                       <af:selectOneRadio label="#{resources.ATTACH_TYPE}"

                                         value="#{pageFlowScope.readAttachmentBean.selectedAttachmentType}"

                                         valueChangeListener="#{pageFlowScope.readAttachmentBean.toggle}"

                                         autoSubmit="true" id="edAttTy"

                                         layout="horizontal" immediate="true">

                        <af:selectItem label="#{resources.DESKTOP_FILE}"

                                       value="file" id="si1a"/>

                        <af:selectItem label="#{resources.URL}" value="url"

                                       id="si2a"/>

                        </af:selectOneRadio>

3. In the search field on the form, search for the text UPLOAD_TO_PROCESS.

Image removed.

4. As shown below, add a blank line above this element’s <af:selectOneRadio …

Image removed.

5. Insert the text copied from step 2 into the blank line.

6. Save the jspx page.  This should have fixed almost all of the errors in the jspx. 

Duplicate ID Errors

You will note that in 12.2.1, one or more errors will still exist on the page because elements have been given same id when the form was automatically generated.  The error message is:

While JSF allows duplicate IDs isolated by naming containers, ADF Faces requires IDs to be unique across the document.

1. To fix these, first go to the line with the error by double clicking the error in the Live Issues… tab.

Image removed.

2. Fix the issue by adding the text “dup” at the end of the id name.  For example, after double clicking an error change this text:

Image removed.

To this:

Image removed.

If there is more than one of these errors, repeat this step until all of the duplicate ids have been corrected on the form.  

3. Save the jspx page.  There should now be no errors on the page.

The ADF forms automatically generated based on human tasks should be able to be created without having to edit the source of the jspx file in the ADF project each time.  The patches suggested above will be of some help, but until this issue is corrected for all 12.2.1.x releases we will need to edit the auto-generated ADF forms. 

2 minute read