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

Designer

Designer

Configuring Custom Columns for Task Roles Filtering

Configuring Custom Columns for Task Roles Filtering

In the Task Role Filters section of the
.avcconfig
file, you can add the task column names you want to display for a category (folder) of tasks. There is a default configuration of column names, and you can add to or replace the columns displayed.
  • To add standard WS-HT column names, see WS-HT Task Property List elsewhere in this help
  • To add custom column names see Creating Custom Task Properties elsewhere in this help
  • To localize the column names, see the example below
Default Configuration
The default configuration for
taskColumn
uses standard WS-HT task properties (all prefixed with
Task
):
<avccom:taskColumns> <avccom:taskColumn property="Task.Id">Id</avccom:taskColumn> <avccom:taskColumn property="Task.Status"></avccom:taskColumn> <avccom:taskColumn property="Task.Priority"></avccom:taskColumn> <avccom:taskColumn property="Task.Name"></avccom:taskColumn> <avccom:taskColumn property="Task.PresSubject"></avccom:taskColumn> <avccom:taskColumn property="Task.CreatedOn"></avccom:taskColumn> </avccom:taskColumns>
To replace or add to these columns, you can add your own column specification, using a custom task property, such as:
<avccom:taskColumn property="first">First Name</avccom:taskColumn>
You must create the custom column names as part of the task definition in a People activity.
To localize the column name, you can specify a key from a message properties file that you create. For example, the column name below is specified as
${bundle.key}
:
<avccom:taskColumn property="Task.CreatedOn" type="dateTime">${bundle.key}</avccom:taskColumn>
For details on creating a message properties file, see Adding Multilingual Support for Task Forms.
The following sample Task Role Filter section illustrates the use of custom columns for Process Central.
<!-- Example - adding a new category/folder called Hello Tasks. This folder will appear in the All role. --> <tns:taskRoleFilterDefs> <tns:taskRoleFilterDef id="ae-avc-role-all" name="${ae.avc.role.user.name}"> <tns:taskFilterCategoryDef id="custom-cat" name="Hello Tasks"> <avccom:allowedRoles> </avccom:allowedRoles> <!-- Define custom columns that appear in Process Central (or remove/comment out root element to use default column list provided out of the box). --> <avccom:taskColumns> <!-- Task.Id, Task.Status and Task.Name are standard WS-HT columns. --> <avccom:taskColumn property="Task.Id">Id</avccom:taskColumn> <avccom:taskColumn property="Task.Status"></avccom:taskColumn> <avccom:taskColumn property="Task.Name">Task Name</avccom:taskColumn> <avccom:taskColumn property="Task.PresName"> Display Name</avccom:taskColumn> <!-- You can also specify the column data formatting via the type attribute. Useful values are date, dateTime and boolean. The column display name can also be externalized via ${18n.key} method. --> <avccom:taskColumn property="Task.CreatedOn"type="dateTime"> ${bundle.key}</avccom:taskColumn> <!-- The property names 'first' and 'last' are WSHT task presentation parameters defined in your tasks (custom properties). --> <avccom:taskColumn property="first">First Name</avccom:taskColumn> <avccom:taskColumn property="surname">Surname (Last Name)</avccom:taskColumn> </avccom:taskColumns> <avccom:taskFilterDefRef ref="ae-avc-user-open-all"/> <avccom:taskFilterDefRef ref="ae-avc-user-open-unclaimed"/> <avccom:taskFilterDefRef ref="ae-avc-user-open-claimed"/> <avccom:taskFilterDefRef ref="ae-avc-user-open-suspended"/> </tns:taskFilterCategoryDef> </tns:taskRoleFilterDef> </tns:taskRoleFilterDefs>

0 COMMENTS

We’d like to hear from you!