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

Working in Development Mode or Production Mode

Working in Development Mode or Production Mode

Generate task details forms that are easy for Inbox users to use.
You can view and update the rendered task details layout in an Process Developer task client without redeploying the BPEL process or even creating a new instance of the process.
In the Renderings tab of the Task Properties view, you can enable Development Mode for testing your renderings. In this mode, when you deploy the process, the rendering files are read from the file system.
Rendering files must be on the same machine as Process Developer when in Development Mode.
Development Mode works as follows:
  • You can edit the files, refresh the Process Developer task client, and see your results immediately.
  • The file location is displayed as project-based. Behind the scenes, the files are treated as file system-based, readily available for editing.
  • The rendering files are added to the deployment archive.
  • The rendering files are not cached.
Note
: If you do not enable Development Mode, you can logout and login to Process Central to view changes to your forms and configuration files.
When you enable the Development Mode, you can test your rendering files as follows:
  1. Deploy the process, start it, and sign in to the Process Developer task client. Sign in as one of the users you specified in the people activity assignments.
  2. In Designer, open a rendering file in an editor and make updates, as desired.
  3. Refresh the task client to see your changes.
To Remove Development Mode
:
When you are done editing the rendering files, you can do the following:
  • Disable Development Mode by removing the check mark in the Task Renderings tab.
  • In the Rendering tab, leave the file locations as project-based or edit the locations to make them Web-based.
  • Redeploy the process via a BRPD file or by creating a new PDD and BPR.
  • Deploy the rendering files as described in Deploying a Task Form and Properties Files.


Updated March 30, 2020