![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• A line starting with a semicolon (;) is treated as a comment line and ignored.
• Each command starts with a single character code (for example: F), followed by a modifier (for example: +).
• (optional) The P command enables prediction on the CDQP. See "Using Case Prediction to Forecast Outstanding Work Items" in TIBCO iProcess Modeler Advanced Design for more information about case prediction.
•
•
The R command must be the first character of the first non-comment line of the control file, otherwise it is ignored.
• Fields that are defined as CDQPs are assumed to exist in all iProcess procedures, and to have consistent type and size definitions across all procedures. No validation is performed to check this. (Any fields that do not exist will be treated as null or blank fields in Work Queue Manager.)
• FieldName is the name of the iProcess field to be defined as a CDQP. FieldName must be less than or equal to 15 characters.If the field is a composite field of the form TagName:FieldName, TagName must be less than 15 characters and FieldName must be less than 15 characters.
• FieldSize is the size, in characters, of the CDQP. FieldSize must be less than or equal to 255.
• WQMDescription is the name that will be used to represent this field in Work Queue Manager dialogs. WQMDescription must be unique, and must be less than or equal to 39 characters.
• P is the command used to enable prediction on the CDQP.F-FieldNamewhere FieldName is the name of the iProcess field to be deleted as a CDQP.
where QueueName is the name of an iProcess queue, which must be already defined in iProcess. Multiple QueueNames can be specified, separated by commas.
Q commands must appear after the CDQP definition section (F commands) in the control file. Any F commands that follow a Q command are ignored.After the Q command, you can add or delete field mappings for this queue, as follows:
• To add any FieldName already defined as a CDQP (see Add or Change a CDQP) to the specified queue’s mapping, use the command:C+FieldNameThe maximum number of CDQPs that can be mapped to a queue depends upon the FieldSize of each CDQP, and upon the number and size of any other standard selectable fields that are mapped to the queue. The larger the FieldSize, the fewer CDQPs you can map to the queue. For example, if each CDQP has a FieldSize of 255, and the default selectable fields are used, approximately 14 CDQPs can be mapped to a single queue, although this is not an exact calculation.
• To delete any FieldName from the queue’s existing mapping, use the command:where QueueName is the name of an iProcess queue, which must be already defined in iProcess. Multiple QueueNames can be specified, separated by commas.You can use the Q and C commands described above to define default user and group queue mappings. The default mappings will be used for all queues on the system that do not have their own mappings defined.
1.
− SW_DEFAULT_CASEDATAQPARAM_USER defines the default user queue mapping.
− SW_DEFAULT_CASEDATAQPARAM_GROUP defines the default group queue mapping.
2.
• If the queue has no mappings already, use the Q+ command to set up a queue mapping, but do not use any C commands to map fields.Q+QueueName
• If the queue already has field mappings, delete them using C- commands. For example:
The following control file fragment continues the example shown in Example CDQP Definitions, and illustrates the use of the different queue mapping commands:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |