Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Testing and Debugging Process Central Forms

Testing and Debugging Process Central Forms

After you deploy one or more process request forms and task forms, you can test and debug your JavaScript by using a browser JavaScript Debugger and enabling debugging in Process Central. You can also use the JSON Converter utility.
To debug your JavaScript in HTML forms, do the following:
  • Install or enable a JavaScript debugging tool in your browser, such as Firebug for Firefox, built-in debugging in Internet Explorer, or the Developer JavaScript Debugger in Chrome.
  • To enable debugging in Process Central, add the following command to the Process Central URL as follows:
    http://localhost:8080/activevos-central/avc/avc.jsp
    ?debug=true
  • Use the
    JSON Converter
    tool to check the conversion of JSON to XML and vice versa. Check what a JSON request form looks like in XML or generate sample XML data and convert to JSON. Access the converter at:
    http://localhost:8080/active-bpel/jsonConverter.html
When you make changes in your form and redeploy it, you can select
Reset Form
in Process Central to view the updated form.
With debug enabled, it is easier to debug jQuery functions. They get expanded into readable lines of code instead of the one long line of code that typically shows in a debug console.
For task forms, you can also use Development Mode for testing layouts without redeploying the form.
Tips for testing forms:
  • Be sure that your HTML forms are well-formed XML. Process Central validates forms and provides warnings if there are invalid tags.
  • Be sure to use lower-case element names that are schema-valid.
  • Check that all tags are properly closed with end tags.
  • In HTML markup, mixed types are not supported. For example, within an XML message element, you cannot add HTML tags, such as
    <contactName><b>Georgia Jane</b></contactName>
    .
  • HTML element ID attributes must end with
    $ID
    suffix, such as
    processRequestForm$ID
    . The
    $ID
    suffix provides a unique HTML element ID to avoid collisions with other forms.
  • JavaScript reserved words, such as
    in
    and
    out
    are not allowed as JSON data parts. If your schema contains an element named as a JavaScript reserved word, you may see a blank form in some browsers. To correct the problem, you must change the JavaScript portion of your form as shown in the example:
    Incorrect:
    getText(parametersTaskInputPart.
    NewOperation.in
    ) where
    in
    is an input message for NewOperation.
    Correction:
    getText(parametersTaskInputPart.
    NewOperation["in"]
    )


Updated March 30, 2020