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

Including Your Own Styles Scripts and Meta Data for Process Central

Including Your Own Styles Scripts and Meta Data for Process Central

In a new
avcconfig
file, there is a section where you can specify your own CSS files, scripts, and meta data for use in Process Central.
Instead of linking in CSS, scripts, and meta data in form and tasks, you reference it from a
.avcconfig
file in the
<centralIncludes>
section.
The
<centralIncludes>
section can include the following elements that are common
<head>
element in a XHTML file:
  • <script>
    . Add a reference to a JavaScript or other script that contains the functions you want to use in request and task forms. The syntax in
    <centralIncludes>
    is, for example:
    <script xmlns="http://www.w3.org/1999/xhtml" | type="text/javascript" src="myJquery.script.js"/>
    You can also use inline scripts, such as
    <script xmlns="http://www.w3.org/1999/xhtml" type="text/javascript"> var my_String = "Hello";
  • <meta>
    . Add meta data keywords. The syntax is, for example:
    <meta xmlns="http://www.w3.org/1999/xhtml" name="keywords" content="some keyword,another keyword" />
  • <style>
    . Use inline styles, such as
    <style xmlns="http://www.w3.org/1999/xhtml" type="text/css">p {background-color: yellow}</style>
  • <link>
    . Style sheet link. See example below.
When you create a new
avcconfig
file, by default, only one section of the file is generated:
<tns:centralIncludes> <link xmlns="http://www.w3.org/1999/xhtml" href="../example.css" rel="stylesheet" type="text/css"> </tns:centralIncludes>
To use your own style sheet:
  1. If desired, review the default Process Central CSS files. To do this, open Process Central and view the Page Source. Find the section of the source file linking to the CSS files and select a link. The style sheet for basic UI styles for fonts and colors is
    ae-avc.css
    .
  2. If desired, copy styles from
    ae-avc.css
    or other CSS and make your own modifications.
  3. In forms and tasks, use the class names from the CSS file, as desired.
  4. Deploy your CSS file.
  5. In an
    avcconfig
    file, add the name of the CSS in the <tns:centralIncludes> section and deploy the
    config
    file. For example:
    <link xmlns="http://www.w3.org/1999/xhtml" href="../example.css" rel="stylesheet" type="text/css">
    Where the
    href
    path can be one of the following:
    • relative path to this
      avcconfig
      file within your project
    • full
      project:/path/to/file
    • Absolute URL, such as
      http://domain:port/myCSS.css


Updated March 30, 2020