Open Workbench 2.1.1 Issue saving some projects back to Clarity 13.3

[Stephanie_Dumbrill]

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. 

[Stephanie_Dumbrill]

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. 

[Allen Bollinger]

Stephanie,

Can CA provide the CLRT-73465 in greater detail? We are on Version 13.3.0.286 02 19 patch release and upgrading environments as we work to a July production upgrade. We seem to be encountering this particular bug at this time also.

Thanks,

Allen

[Stephanie_Dumbrill]

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. 

[System]

Stephanie_Dumbrill:

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. 

Thanks for letting the community know!