Clarity

We are currently investigating a reported issue with Open Workbench 2.1.1 intermittently not saving projects back to Clarity 13.3.0.  This is not the case for all projects.  

We are working as quickly as possible to determine the root cause and resolution.  We will provide feedback as quickly as possible via this forum and CA Support. 

We hope this notification helps you manage your implementation.  More to follow and thank you for your patience as we work through this issue. 

Is this the issue?

https://communities.ca.com/web/ca-clarity-global-user-community/message-board/-/message_boards/message/114720021?p_p_auth=2h6gIqeW&#p_19

Martti K.

Hi Martti -

It is possible it is the same issue as it appears to fit the pattern.

Since the user stated he already logged a case with Support, it is likely that it is part of the current investigation.  As we continue our investigation, we will post additoinal details as they become available.

Thanks,

Kate

This is really frustrating.  We've been FORCED to go back a use OWB v1.2.1 as the issue doesn't result with that client version.  Unfortunately, that version doesn't properly handle Clarity's v13 role mapping (duplicate roles mapped to requiremennt name field though) so we still have usability ISSUEs.  Experience thus far with OWB v2 and v13.3 not ideal at all.

Thanks for the feedback Pat.

We understand the urgency and are working to come to a resolution for you as quickly as possible.

Thanks,

Kate

Just wondering again...

Is  the OWB that  comes already developed by CA or still by ItDesign as the splash screen suggests?

Martti K.

It also concerns me that the OWB version (v2.1.1) remained the same.  I believe they are listing a Clarity 'build' # after the core client version, but it honestly can only be viewed in the OWB about menu.  If your IT group or individual looks in the control panel / programs & features component of the laptop/computer ....there is no way to know what build version of OWB is loaded on the machine.  Since we are having to uninstall v2.1.1 and put v1.2.1 back onto machines, it would be appropriate to have clear versioning so that we can leverage our SMS solution to help identify SW version and allow us to complete automated push software installs for OWB.  I fear that we will see more OWB versions as there are several defects already reported.    

nosreme:

It also concerns me that the OWB version (v2.1.1) remained the same.  I believe they are listing a Clarity 'build' # after the core client version, but it honestly can only be viewed in the OWB about menu.  If your IT group or individual looks in the control panel / programs & features component of the laptop/computer ....there is no way to know what build version of OWB is loaded on the machine.  Since we are having to uninstall v2.1.1 and put v1.2.1 back onto machines, it would be appropriate to have clear versioning so that we can leverage our SMS solution to help identify SW version and allow us to complete automated push software installs for OWB.  I fear that we will see more OWB versions as there are several defects already reported.    

 

Clarity Version		V13.3.0	V13.3.0.2
Open Workbench Version (shipped)		2.1.1 (13.3.0.286)	2.1.1 (13.3.0.286.02.19)

 

You are correct, the OWB version currently displays just the version number.  We are working with our team to modify that for future releases to include a build/patch number appended to the version.  

With the current version, the create and/or modified date for the OWB file can be used as the determining factor as the date for the OWB 2.1.1 iteration that shipped with Clarity 13.3 base version is November 14,2013 and the date for the OWB 2.1.1 iteration that shipped with Clarity 13.3.0.2 is February 19, 2014.

Hi,

We had the similiar issue mentioned by Stephanie when saving the project using OWB 2.1.1 version for all projects. In our case, we are able to save it after updating PRACTTHRU on PRASSIGNMENT table with null. Also OWB is updated  the practthru value to its original value, which is same as prior to sql update value. I know CA is not recommended to update it directly and working with CA.

Thans

Hello everyone.  Thank you for your patience as we work through the issue outlined above. 

We are targeting next Wednesday, May 14th to release an emergency patch on 13.3.0 to address defect CLRT-73465, which is the root cause for some projects not being able to be saved back to Clarity.  

As with all of our patches, this patch will be cumulative and include the fixes from 13.3.0.1, 13.3.0.2 and 13.3.0.3.  You will be able to apply this patch and receive the other fixes fixes as well so no need to apply 13.3.0.3 and then this patch.   The fix will require a refresh of Open Workbench on the client side.  

We hope this helps to keep you informed.  We'll let you know when the patch is available.  Thank you again for your patience. 

As an update to this issue we have released a Patch (13.3.0.4) to address this issue in Clarity 13.3/Open Workbench 2.1.1.  The patch is available for download on support.ca.com. 

This patch contains one new fix for defect CLRT-74573.  The issue has to do with a null pointer exception being created.  Below are a simple set of steps you can use to replicate the issue that was addressed.  Because of this null pointer exception, the project would not save back to Clarity.  The steps are: 

1. In Open Workbench create a project and task.

2. Assign a resource to that task.

3. In Clarity, post a timesheet to have some actuals for that task.

4. Open project in Open Workbench and Open resource properties -> calendar, make next Monday as holiday.

5. Try to save back to Clarity. Open Workbench throws error.

This patch is a cumulative patch so you only need apply this patch to also install the fixes included in the earlier Clarity 13.3 patches.  This fix requires a Client Side installation.  

Thank you for your patience while we worked through this issue.  Our apologies for any inconvenience this has caused you and your users. 

I seem to be confused here as the root cause / steps to reproduce listed are quite different in the Patch 13.3.0.4 release notes...........

---------------------------------------------
Issues Fixed in 13.3.0.4:
---------------------------------------------

CLRT-73465 : OWB Does Not Save Just Delta

Steps to Reproduce: 
1. Open OWB then connect to abitu01-vm95527:1213
2. Open project Aditi-CVB21100
3. Click the project tab then the manage link with baselines on the OWB ribbon
4. Select the last baseline and click the ok button.
5. Attempt to save the project.

Expected Result: OWB saves project successfully to clarity
Actual Result: OWB throws error.

Previous post references defect # CLRT-74573 that isn't in the release notes at all. 

CLRT-73465 is the correct defect to check. CLRT-74573 is the number assigned to aggregate all defects fixed with the patch.

Sorry for the confusion.

Hi Pat -

Both sets of Steps to Reproduce are correct.  The root cause of the issue was the handling of a null curve, which is generally the result of something occurring 'under the covers'.  The STR that Stephanie listed above was posted to assist with forcing the null value to enable testing as the original reported STR (posted in the Read Me file) is specific to baselines and not all customers use baselines.

Thanks,

Kate

Thanks Steph, Kate and Connie for following up on this important issue!