Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to available_downloads/CollaborativeInformationManager/7.0.0/hotfix-03/  to download the hotfix.
This .tar file also has the Readme file inside. Please untar the file and look for the Readme file for Instruction on how to apply the hotfix.


Closed Issues in 7.0.0_hotfix3 (This Release)

1-8RBN6W
When the SaveRecord activity was executed with ProductIds and ProductExtns
as input parameters, an "Unique constraint violation" exception was thrown.
This has been fixed.

1-8RDJ9U    
When the InDocument passed to the following activities contained a master
catalog name instead of the master catalog ID, the activity failed to
process:
  - CheckRecordState
  - DeleteRecord
  - GetRecord
  - ManageRecordCollection
  - SaveRecord
This has been fixed.

1-8RS1EP
When a large number of incoming messages were received by the application,
the processing of messages became slow. This has been fixed.

1-8RS1H7
When a message was received or sent from the application, many internal
events were generated and slowed down the message processing. This has
been fixed. To improve performance, internal event generation for
Q_ECM_CORE_COMM_EVENT is now optional.

- For an outgoing message, pass following parameter as true to
  the SendProtocolMessage activity.
  &ltParameter direction="in" name="GenerateCommEvent" eval="constant"
  type="boolean"&gttrue</Parameter>

- For an incoming message, set the following property in the "Messaging
  Settings" Category of the $MQ_HOME/ConfigValues.xml file.
  com.martquest.commReceiver.JMS.receiver.generateEvent

  This property can be set as follows:
  &ltConfValue name="JMS Message Receiver Generate Event"
  propname="com.martquest.commReceiver.JMS.receiver.generateEvent"
  visibility="Advanced" description="Flag indicating
  whether to generate internal event on message receipt.">
  &ltConfString value="true" default="false"/>
  </ConfValue>

1-8T2L5B
The Send and WaitForResponse activity did not evaluate participants
(UserAddress for Send and ParticipantID for WaitForResponse) if the
login name was passed as input instead of member ID. This has been fixed.

1-8T45J5
The workflow transition evaluation using BeanShell (bsh) format took a
long time. This has been fixed by supporting a new format, java, in
the transition condition. Refer to section "CR 1-8T45J5 - Using the java format"
further in this readme for more information on the format.

1-8T45N7
When processing a large number of incoming messages, workflow selection
through the workflow configuration file took a long time. This has been
improved by caching process selection results.

1-8T45OF
When the dropdown for an attribute was populated using a rulebase and
the attribute had a read-only access for record edit mode (NOT for
Add mode), correct values were not displayed for the attribute on
the Modify page. However, correct values were displayed when the
record was seen on the View page. This has been fixed.

1-8T45U5
When a dropdown (with more than 1000 rows and multiple columns) for an
attribute was populated using a rulebase, it took a long time to display
the dropdown on the Add or Modify page. This has been fixed.

1-8T45W7
Instead of directly processing an incoming message of type mlXML, a duplicate
mlXML envelope was added to the original message. This has been fixed.

1-8T4LFM
When the logging level was set to DEBUG in the MqLog.cnf file, the login
credentials (userid/password) were logged in the elink.log. This has been
fixed.

1-8TCI3B
When a record collection passed to the EvaluateRuleBase activity had
only a reverse relationship name (for example, ContainedBy) defined,
during the rulebase execution, the EvaluateRuleBase activity did not
fetch forward relations (for example, Contains) for the relationship_record
link type variable. This has been fixed.