CA Software 511 WSAD Plugin 20 PATCH 008 October 04 2004 - CA Technologies
{{search ? 'Close':'Search'}}

****************************************************************

CA Software 5.1.1 WSAD Plugin 2.0 PATCH 008
October 04, 2004

****************************************************************


****************************************************************
Contents
****************************************************************

1.0 Welcome

2.0 Fix Alerts

3.0 Installation Considerations

4.0 Patch installation
4.1 WINDOWS Installation

5.0 Problems corrected
5.1 Problems fixed in PATCH 001
5.2 Problems fixed in PATCH 002
5.3 Problems fixed in PATCH 003
5.4 Problems fixed in PATCH 004
5.5 Problems fixed in PATCH 005
5.6 Problems fixed in PATCH 006
5.7 Problems fixed in PATCH 007
5.8 Problems fixed in PATCH 008

6.0 Additional information on problems corrected

7.0 Contacting Technical Support

8.0 Downloads


****************************************************************
1.0 Welcome
****************************************************************

This Readme file contains installation considerations as
well as patch installation instructions, problems
corrected, known issues, and contacting Technical Support.


****************************************************************
2.0 Fix Alerts
****************************************************************

For each fix listed, you should view the information listed in
Section 6.0 for additional information.


Patch 7
--------
1710 - CHECKOUT FOR CONCURRENT UPDATE ON BRANCH VERSION FAILS
Users can now create additional branch versions.


****************************************************************
3.0 Installation Considerations
****************************************************************

* In addition to its WSAD Plugin PATCH, the Harvest 5.1.1 WSAD Plugin 2.0
also requires the installation of the following patches:

- HARVEST 5.1.1 PATCH.
- HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH.
- HARWEB 3.1 PATCH.

* Please refer to the README.TXT of HARVEST 5.1.1 PATCH,
the HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH, and the
HARWEB 3.1 PATCH for installation instructions.

* The minimum patch level requirements for this WSAD plugin PATCH are:

- HARVEST 5.1.1 PATCH 019.
- HARVEST 5.1.1 HSDK for WSAD 2.0 PATCH 019.
- HARWEB 3.1 PATCH 013.

* Please apply this PATCH/FIX to the corresponding WSAD installation.

* The PATCH files are cumulative; in other words, applying the latest
PATCH file provides all fixes.

For example: HAR511WSAD2PATCH005 contains all fixes from
HAR511WSAD2PATCH001 to HAR511WSAD2PATCH005.

* To apply a patch/fix go to the APPLY PATCH/FIX section.

* The difference between HAR511WSAD2PATCH005 and HAR511WSAD2PATCH005FIX,
is that the first refers to a publicly available PATCH (patch 5),
and the second refers to a set of intermediate FIXES available after
the PATCH (patch 5).

* Intermediate FIXES are usually included in the next publicly
available PATCH.


****************************************************************
4.0 Patch installation
****************************************************************

________________________________________________________________
4.2 WINDOWS Installation
________________________________________________________________

To apply the PATCH/FIX, perform the following steps:

1.- Shutdown Websphere.

2.- Copy the "<patch>.zip" file to the Websphere directory where
the plugins are installed (this should be the "plugins" directory,
which contains the directories "com.ca.harvest.<component name>.<version>").

3.- Decompress "<patch>.zip" file into this directory. This will
place the "com.ca.harvest.<component name>.<version>.zip" files
within the "plugins" directory.

4.- Decompress each "com.ca.harvest.<component name>.<version>.zip" file
into the "plugins" directory. This will create the additional directories
within the "plugins" directory, which contain the updated versions.

5.- Modify file: .harcontext located within: .metadata.pluginscom.ca.harvest.core
and change the version number to the new version number of com.ca.harvest.core.
For example, if the version is 2.0.3, then modify the following line:
<!DOCTYPE harvest SYSTEM 'platform:/plugin/com.ca.harvest.core_2.0.3/dtd/harContext.dtd'>

6.- Start Websphere.


****************************************************************
5.0 Problems corrected
****************************************************************

Note: An asterisk (*) indicates to refer to the section
"6.0 Additional information on problems corrected"

________________________________________________________________
5.1 Problems fixed in PATCH 001
________________________________________________________________

1262 - RESOURCE OUT SYNC ERROR IN WSAD
(*) 1646 - REPLACE WITH LATEST TRUNK VERSION FAILS WITH NO MEANINGFUL MESSAGE
(*) 1648 - REFRACTOR/ RENAME FILE NOT RENAMED
1656 - SYNCHRONISATION INCORRECT WHEN D TAGS EXIST
(*) 1675 - DISABLE SHYNCHRONIZE OPTION WHEN MORE THAN ONE RESOURCE IS SELECTED
(*) 1707 - INVALID VIEWPATH ERROR WHEN SYNCHRONIZING SUBDIRECTORY
1723 - DECORATOR MARKED INCORRECTLY WHEN FILE IS ALREADY CHECKED OUT
1730 - RECEIVED .PROJECT OUT OF SYNC ERROR WHEN UPDATING PROJECT PROPERTIES
1761 - DECORATOR MARKED INCORRECTLY WHEN CHECKIN FAILS FOR SOME FILES
1781 - WSAD 5 HANGS WHEN RENAMING A FILE IN A WEB PROJECT

________________________________________________________________
5.2 Problems fixed in PATCH 002
________________________________________________________________

1727 - IMAGE RESOURCE LEAK CAUSES IDE TO CRASH
1759 - DRAG AND DROP CAUSES A RESOURCE OUT-OF-SYNCH ERROR
1805 - REMOVING ONE PROJECT FROM A HARVEST CONNECTION CLOSES THE CONNECTION
1861 - CANNOT RESIZE PATH COLUMN WITHIN VERSION LIST WINDOW

________________________________________________________________
5.3 Problems fixed in PATCH 003
________________________________________________________________

1782 - CHECKIN FAILS FOR FILES RENAMED FROM UPPER CASE TO LOWER CASE OR VICE VERSA
(*) 1859 - "Replace with" OPTION DISPLAYS BOTH VERSIONS IN WORKSPACE RATHER THAN LATEST VERSION FOR RENAMED FILES
1868 - CANNOT CHECKIN A FILE CONTAINING NON-ENGLISH CHARACTERS

________________________________________________________________
5.4 Problems fixed in PATCH 004
________________________________________________________________

(*) 1727 - WSAD SHUTDOWN BY IMAGE LIMIT

________________________________________________________________
5.5 Problems fixed in PATCH 005
________________________________________________________________

(*) 1846 - UDP OUTPUT IN THE HARVEST LOG IN WSAD IS TRUNCATED
(*) 1964 - REMOVE ITEM CAUSES PROBLEM DURING SYNCHRONIZATION
(*) 2092 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED
(*) 2180 - CHANGE MESSAGE WHEN RENAME ITEM PROCESS IS NOT DEFINED
(*) 2262 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED BY ANOTHER USER
(*) 2293 - RENAMING AN ITEM CURRENTLY CHECKED OUT INCORRECTLY CREATES NEW ITEM

________________________________________________________________
5.6 Problems fixed in PATCH 006
________________________________________________________________

(*) 2264 - DELETING AN ITEM CURRENTLY CHECKED OUT REMOVES ITEM FROM WORKSPACE
(*) 2663 - SYNCHRONIZE OF WSAD IS SLOWER IN SP2

________________________________________________________________
5.7 Problems fixed in PATCH 007
________________________________________________________________

(*) 1710 - CHECKOUT FOR CONCURRENT UPDATE ON BRANCH VERSION FAILS
(*) 2217 - RENAMING A PROJECT TO AN EXISTING NAME GIVES INCORRECT ERROR MESSAGE
(*) 2415 - CHANGING PASSWORD IN HARVEST IS NOT PROPAGATED TO WSAD
2467 - IMPROVED THE SYNCHRONIZATION PERFORMANCE
(*) 2469 - NO ERROR MSG DURING CHECKOUT WHEN NO HARVEST CONNECTION EXIST
(*) 2536 - NO ERROR MSG DURING CHECKOUT WHEN CONTEXT PACKAGE NOT SET OR INVALID
(*) 2646 - INCORRECT ERROR MESSAGE DISPLAYED WHEN DOUBLE-CLICKING A FILE
(*) 2729 - HARWEB IS NOT COMPATIBLE WITH ECLIPSE 2.1
(*) 2732 - WSAD CANNOT LAUNCH HARWEB WHEN USING HTTPS
(*) 2769 - WSAD LOGIN FAILS AFTER CHANGING PASSWORD WHEN PASSWORD EXPIRES
(*) 2788 - SELECTING "MY PACKAGE" DOES NOT DISPLAY THE CORRECT CONTEXT
(*) 2801 - CONCURRENT MERGE "TAKE TRUNK" OPTION ACTUALLY TAKES BRANCH CHANGES
(*) 2873 - MULTIPLE CHECKINS/CHECKOUTS DURING RELEASE AFTER SYNCHRONIZATION

________________________________________________________________
5.8 Problems fixed in PATCH 008
________________________________________________________________

1875 - Confirmation before Replacing with Latest Trunk Version
2401 - HSDK CaVersionChooser API Returns No File Size
2700 - Ok Grayed Out in Harweb Context Dialog if Multiple Brokers in WSAD
2779 - Log view does not handle line separators.
2793 - Not Show Checkout Marks After Add and Reserve in WSAD
2796 - Sync Problem after Copy/Paste an Item
2982 - Cancel Button in Select Harweb Context Brings Harweb
3015 - Compare with Last Trunk Version Problem for R Tag Version
3081 - Add empty projects to workspace
3085 - Can Not Connect to More Time One Broker in WSAD
3120 - Sync Problem after Concurrent Merge in WSAD
3197 - Delete Item Problem When Broker Has Version Tag in WSAD


****************************************************************
6.0 Additional information on problems corrected
****************************************************************

1646 - REPLACE WITH LATEST TRUNK VERSION FAILS WITH NO MEANINGFUL MESSAGE

The following Error Message has been changed:

FROM: CAHReplateWithLatestAction.coMsg2

TO: One or more children of - %7B0%7D - is checked out.


1648 - REFRACTOR/ RENAME FILE NOT RENAMED

The following dialog has been changed:

FROM: "The file cannot be renamed unless it is checked in, Do you want to check it in ?"

TO: "File will not be replaced. Only references within this file will be renamed "


1675 - DISABLE SHYNCHRONIZE OPTION WHEN MORE THAN ONE RESOURCE IS SELECTED

Harvest WSAD plugin does not support synchronisation of multiple packages at a time.
Therefore, this option will now be disabled when more than one package/file is selected.


1707 - INVALID VIEWPATH ERROR WHEN SYNCHRONIZING SUBDIRECTORY

A user cannot synchronize a view path if that view path does not exist in the Repository.
The following message will be displayed if a user attempts to do so:

"Cannot synchronize view path which does not exist in repository"

1710 - CHECKOUT FOR CONCURRENT UPDATE ON BRANCH VERSION FAILS

In WSAD, you are not able to check-out version 1.1.1 to continue development on the branch
(creating version 1.1.2, 1.1.3 etc). You are forced to merge the version to trunk.

Steps to reproduce:
1. Set up a checkout process with concurrent update mode in the context.
2. Checkout an item: Bean2.java for concurrent update: creating: 0.1.1.
3. Try to checkout for concurrent update again on the item, fail with the error:
item repBean2.java; 0 has unmerged branch version in the check out package.
Not able to create new branch version

1727 - WSAD SHUTDOWN BY IMAGE LIMIT

The CA Software CM WebSphere Studio Integration now allows you to customize the label
decorations used on projects managed by Harvest. Go to Window, Preferences, Team, AllFusion
Harvest CM to update the decorator preferences. From this preference page, you have the
ability to enable/disable image decorations, as well as customize the text decorations.


1846 - UDP OUTPUT IN THE HARVEST LOG IN WSAD IS TRUNCATED

UDP output will still appear truncated in the log. Users will have to double click on the entry in the
log and a dialog box will appear showing the whole text.


1859 - "Replace with" OPTION DISPLAYS BOTH VERSIONS IN WORKSPACE RATHER THAN LATEST VERSION FOR RENAMED FILES

Rename a file in the WSAD Workspace, and then check into harvest to create a new version. Then
click "Replace with -> version in Harvest " and get the version compare window. Click this file's
previous version with its original name and perform "Get". Both of the files will incorrectly appear
in the workspace, rather than just the latest version.

1964 - REMOVE ITEM CAUSES PROBLEM DURING SYNCHRONIZATION

If a file is removed from workspace and synchronize with harvest, the file will be deleted. There is no
option to get back this file later on, even if other people checkin the same file or remove the "D" tag
from harvest.

Steps to Reproduce:
1. User1 and User2 do an "Add to workspace" of the same project in WSAD
2. User1 deletes version0 of a file1 & synchronizes with Harvest
-> D-tag with version1 is present in Harvest
3. User2 synchronizes with Harvest and file1 is deleted in his workspace
4. User1 creates a new file, calling it file1, which was previously deleted & synchronizes with Harvest
-> Version2 is created
5. User2 synchronizes with Harvest
-> A new delete tag Version3 is created
-> file1 does not appear
6. User1 synchronizes with Harvest
-> file1 does not appear anymore

2092 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED

If an item is checked out for update in a WSAD workspace, and if the reserved version is deleted from the
Harvest perspective, then the checkout cannot be undone.

Steps to reproduce:
1. Perform a check-out of a file
2. Go to harvest repositories perspective and delete the reserve tag
3. Go back to the navigator and try to synchronize the project or undo checkout.
4. Get an error: version not reserved for file: %7Bfile name%7D

2180 - CHANGE MESSAGE WHEN RENAME ITEM PROCESS IS NOT DEFINED

When trying to rename a file and no rename item process is defined in that state, the error message is misleading.

Current Error Message:
There is no rename item process in the current context.

New Error Message:
There is no rename item process defined in the current harvest state.

2217 - RENAMING A PROJECT TO AN EXISTING NAME GIVES INCORRECT ERROR MESSAGE

In WSAD renaming a project to a project name already existing in Harvest results in an incorrect
error message.

Steps to reproduce:
1. Launch WSAD/eclipse.
2. Add project say "A" to the workspace.
3. Rename project to B. Synchronise with Harvest.
4. Rename project B to A. The following error message is displayed:
Checkin failed, Please see output log for more details.
E020200118: Version not reserved for file.

2262 - CANNOT UNDO CHECKOUT IN WSAD IF RESERVED VERSION IS DELETED BY ANOTHER USER

After aN "R" tag version is deleted by another user, the first users cannot synchronize, checkin, or
undo checkout for this item.

Steps to Reproduce:
1. UserA adds a project into workspace.
2. Checkout a item for update.
3. Another uesrB adds this project into his workspace also.
4. UserB deletes the "R" tag version from the versoin list in Harvest Repositories field.
5. UserA trys to do Synchronize/checkin/undo check, He will always get error:
version not reserved for file : ....., checkin failed.

With this fix, if a user has checkout ">" mark on an item and the "R" tag version is deleted by another user, the
user can use "undo checkout" to remove the checkout ">" mark, so that the status of the item can be restored back.

2264 - DELETING AN ITEM CURRENTLY CHECKED OUT REMOVES ITEM FROM WORKSPACE

When a user receives the message "Cannot Delete File. Please check-in or undo check-out first."
Selecting OK will remove the file from the workspace instead of letting you checkin or
undo the checkout.

Steps to Reproduce:
1. Add a project into worksapce.
2. Checkout a item for update.
3. Delete this item in the workspace. Will get the message: "Are you sure want to delete the item?"
4. Click yes, Will get the error message: "File is checked out. Please check-in or undo check-out first."
5. Click ok, the file is removed from the workspace.

2293 - RENAMING AN ITEM CURRENTLY CHECKED OUT INCORRECTLY CREATES NEW ITEM

In wsad workspace, there is a project being managed by harvest. User checks out a file for update, makes changes
to this file, and saves it. If there is no rename process defined, then after the rename process fails, a new
version is created for this file in harvest.

Steps to reproduce:
1. Add a project to WSAD project. There is no rename process defined.
2. Checkout a file for update and make some changes to it, then save it.
3. Right click item and select "rename" to rename the file to a new file.
4. The rename process fails, but a new version is created in harvest.

2415 - CHANGING PASSWORD IN HARVEST IS NOT PROPAGATED TO WSAD

WSAD and Harvest store the saved password (option to save password on login page) in different ways,
different places. If a user changes their password in either workbench or administrator, they are
unable to use their WSAD Harvest connection and cannot use WSAD change password to correct the problem.
Likewise if a user changes their password in WSAD, they are unable to login into workbench or the
Administrator tool with the saved password. They can change the password and if the save password is
checked, the new password is saved.

Steps to reproduce:
1. Using Eclipse establish a Harvest connection and close Eclipse
2. In either Harvest Workbench or Administrator tool, change a user's password
3. Re-start eclipse and under the Harvest perspective select one of the projects. An error message is
written to the output log stating that login has failed.

2469 - NO ERROR MSG DURING CHECKOUT WHEN NO HARVEST CONNECTION EXIST

User creates a Harvest connection and adds the project to the workspace. The project is then closed
and the Harvest connection is discarded. The user can then reopen the project without the Harvest
connection. If the user starts typing in a file, a checkout is performed. Since the Harvest connection
is absent, there is no context set. An error is written to the log file, however, the user never
receives a notification and is unaware that a problem has occurred.

Steps to reproduce:
1. Create a connection to one broker.
2. Add to Workspace two Views.
3. In Navigator, close both Projects.
4. In Harvest Repositories, Discard Location.
5. In Navigator, open both Projects.
6. Start updating files. RESULT: The user is unable to update the file. An error is written to the log
file, but the user is never informed

With this fix, the user will now receive the following message:
"Context is not set. Please check your Harvest Connection"

2536 - NO ERROR MSG DURING CHECKOUT WHEN CONTEXT PACKAGE NOT SET OR INVALID

If the package defined in the WSAD connection has been promoted, and the user starts typing in a file,
WSAD does a check out, which fails and the user is never advised.

Steps to reproduce:
1. Create a new Harvest Connection and select a package
2. Add to workspace a view
3. In Harvest Workbench, promote this default package
4. In WSAD Navigator, open a file and start typing. RESULT: nothing happens. If the state has both
check out for update and check out for concurrent update, the check out mode dialog is displayed.
5. However, if you right-click on the file and Team -> Check Out RESULT: Error message says no package is selected.

With this fix, the user will now receive the following message:
"There is no package in your context. Please set your context package they try again"

2646 - INCORRECT ERROR MESSAGE DISPLAYED WHEN DOUBLE-CLICKING A FILE

When double click a file in the incoming/outgoing mode in synchronization field, in harvest log,
it shows an incorrect error message.

Steps to reproduce:
1. Synchronize WSAD workspace with harvest repository.
2. Using harvest client GUI, run 'Delete version' process to delete the latest version of a managed
resource from the harvest repository.
3. In WSAD, run Synchronize with Harvest. Double click a file in the incoming/outgoing mode
window to report the diffrences. The WSAD Log view reports the following message:
"E3080004: Error Message Format Error: HSDK_E_NO_VERSION_INVALID_ID"

2663 - SYNCHRONIZE OF WSAD IS SLOWER IN SP2

When comparing synchronization of WSAD between SP2 and Harvest511 PATCH016, sync in SP2 takes
longer time than in PATCH016.

Steps to reproduce:
1. Apply Harvest 5.1.1 Patch 16 (and the appropriate HSDK & Wsad Patches).
2. Time the Wsad Synchronize
3. Apply Harvest 5.1.1 SP2 (and the appropriate HSDK & Wsad Service Packs).
4. Time the Wsad Synchronize

For example: Synchronize 561 files in a wsad project:
Harvest 5.1.1 patch 16 - 45 sec.
Harvest 5.1.1 SP2 GA - 1 min 30 sec.

2729 - HARWEB IS NOT COMPATIBLE WITH ECLIPSE 2.1

When installing the current harvest plugin for eclipse 2.0 into eclipse 2.1, and you try to launch
harweb through eclipse 2.1, it will not be able to launch the harweb.

Steps to reproduce:
1. Install the harvest plugin module for eclipse 2.0 into eclipse 2.1.
2. Create a harvest context and click pull down menu -> Harvest -> My packages.
3. The harweb page does not show up and returns the following error message in the Harvest log:
"Unable to create a web browser handle."

2732 - WSAD CANNOT LAUNCH HARWEB WHEN USING HTTPS

When Harweb uses an SSL (Secure Socket Layer) connection, Harweb works correctly. However,
WSAD is unable to launch Harweb.

Steps to reproduce:
1. Configure TOMCAT4.0.6 to support SSL.
2. Configure Harweb to run as HTTPS protocol.
3. Lauch Harweb outside of WSAD to make sure it works ok.
4. In WSAD, try to lanch harweb by click "My Packages". Harweb page doesn't show up. The .log file
shows the following error:
"com.ca.harvest.jhsdk.hutils.JCaHarvestException: E03090003: ERROR: Could not connect to Broker: ****"

2769 - WSAD LOGIN FAILS AFTER CHANGING PASSWORD WHEN PASSWORD EXPIRES

When a Harvest user's password is marked as expired and a new Harvest connection is created in WSAD,
the user is presented with a dialog to change their password. After the user changes their password,
login fails.

Steps to reproduce:
1. Created hpasswd.cfg file using the hppolget command.
2. edited this file as follows:
# User Level Overrides
wsad.passwordchangenextlogon = true
3. Started WSAD
4. Created a new Harvest connection
5. Received password expiration dialog and changed the password
6. Successfully created the connection
7. When the connection was expanded a login is performed, which fails.

2788 - SELECTING "MY PACKAGE" DOES NOT DISPLAY THE CORRECT CONTEXT

In WSAD, when YOU select "My Packages" from THE Harvest Menu, a pop-up for a project selection
will display the details of the project selectd. Select different projects and it will still
display the "My Package" page and context details of the project selected in the first attempt.

Steps to reproduce:
1. Setup three harvest connections with the same broker, but different projects.
2. Select "My packages" from Harvest menu, pops up for a project selection, and select a project.
It will display the details of the project selected.
3. Select other projects for "My Package". It still shows the same page. The context is still
set to the first project.

2801 - CONCURRENT MERGE "TAKE TRUNK" OPTION ACTUALLY TAKES BRANCH CHANGES

When performing a concurrent merge if we select the option "Take Trunk Version", the resulting
version will contain the branch changes.

Steps to reproduce:
1. Check out a file in the Navigator view for concurrent update.
2. Modify the file.
3. Save.
4. Team --> Check In and Release.
5. In the Harvest view, run the concurrent merge process (take trunk option)
6. Compare the contents of the new version created against the contents of the branch version
and previous trunk version.

2873 - MULTIPLE CHECKINS/CHECKOUTS DURING RELEASE AFTER SYNCHRONIZATION

Synchronize with Harvest takes longer if items are selected rather than directories as Harvest
will execute individual checkins/checkouts for each item rather than collecting all of the items
and executing 1 process.

Steps to reproduce:
1. In Harvest Administrator, update "Checkin items" process to add UDP to echo "hello".
2. In WSAD, File -> New -> Example -> Enterprise Applications 1.2 -> MiniBank
3. Team -> Share Project -> (Select harvest connection)
4. Right-click MiniBankEJB -> ejbModule -> minibank.ejb
5. Right-click BankAccount.java -> Refactor -> Rename
6. Right-click minibank.ejb -> Source -> Organise Imports
7. Many items are checked out automatically and updated
8. Right-click->minibank.ejb -> Team -> Sync with Harvest
9. Incoming/Outgoing Mode window comes up.
10. Selecting from item level: Select items prefixed with "_" of which there are 18 of them.
11. Select Release.
12. 18 hci processes will be executed in sequence apparent from the harvest log.
13. Select top folder ejb
14. Select Release.
15. Only 1 hci process will be executed, hence this operation will run faster.


****************************************************************
7.0 Contacting Technical Support
****************************************************************

See SupportConnect.ca.com for the latest product information.
For further technical assistance with CA Software
Change Manager, contact Technical Support at 1-800-833-7528
Hours 0800-1800 CST


****************************************************************
8.0 Downloads
****************************************************************

Downloads
Operating System
Windows – 703 KB

 

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing