December 18 2016

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 both 12.2.1.1 and 12.2.1.2 small manual edits are now required to eliminate the errors on the generated form.

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

edAttTy Errors

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

edAttTy Error on Auto-Generated ADF Forms

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. 

ADF Form's Source Tab

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

Form Errors

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.

Search for the text "UPLOAD_TO_PROCESS"

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

Insert blank line into the source

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.

Live issues tab

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:

Duplicate IDs in the auto-generated form

To this:

Fix for Duplicate ID error

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.  Until this issue is corrected, we will need to continue to edit the auto-generated ADF forms.

About the Author

Dan Atwood

Dan has more than sixteen years of experience in all phases of design, development, and implementation of software applications using BPM. He has developed Oracle BPM, BAM, business rule and integration solutions for financial services, insurance, food cooperative, and telecommunications clients.

Join the Conversation

Bill Hodson
February 3, 2017

Thanks for the information, Dan.  

Hard to believe these errors are getting worse with each release. 

 

 

Enter your first name. It will only be used to display with your comment.
Enter your email. This will be used to validate you as a real user but will NOT be displayed with the comment.
By submitting this form, you accept the Mollom privacy policy.