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

Understanding the Process Request Form Template

Understanding the Process Request Form Template

When a user submits a process request form, the server must match the request to the service name in the PDD. Be sure that the service name shown in the form matches the My Role service name in the PDD (for the starting activity of the process).
In the generated form, find the line of code for the service name and verify the name:
<script type="text/javascript"> //<![CDATA[ // request form to submit requests and handle response var AeRequestForm$ID = function() { // this var mFormInstance = this; //
the service name
var mServiceName = "EstimationService";
Making Additional Modifications
If you wish to make additional modifications to a process request form, it is helpful to understand the template used to create the form and the HTML file that is generated from it.
Visual Parts of the Form
  • Title
    By default the title is based on the operation name of the receive activity's interface. It is in the top-most table of the HTML page.
  • Input Message Parts
    If the message is a single-part element, there is one table containing one row for each child element. There is a separate table for each element. If an element is repeating, two command buttons are added: Add and Remove.
  • Send Request command button
    At the bottom of the form, a command button is added to submit the request and start the process.
For multilingual support, see Adding MultiLingual Support to Process Central.
Script Section of the Form
The script contains the commands to format and display the form dynamically in Process Central. The script is JavaScript, containing JavaScript Object Notation (JSON) and jQuery syntax to provide functionality in the form as well as transport protocol. For details, see Customizing Task and Form Scripts: An Introduction.


Updated March 30, 2020