CDR Tickets

Issue Number 3306
Summary Global change of references from former InScopeProtocol
Created 2011-02-15 11:36:52
Issue Type Improvement
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To alan
Status Closed
Resolved 2011-02-17 12:05:25
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.107634
Description

BZISSUE::4998
BZDATETIME::2011-02-15 11:36:52
BZCREATOR::William Osei-Poku
BZASSIGNEE::Alan Meyer
BZQACONTACT::William Osei-Poku

Not too long ago we decided to retire the global you developed to fix the problem created by the old transfer process (creating a new CTGovProtocol instead of using existing InScopeProtocol) OCECDR-2959 because it had been in production for a long time enough and also since the underlying process that created the problem had been corrected. But recently I have come across a couple of Summaries and InScopeProtocol documents that had links to blocked transferred trials. It turned out that users are linking to these blocked trials without checking to see if there are corresponding CTGovProtocol trials. So far, all the ones we identified have been fixed and users have been advised to check to make sure that they are not linking to blocked trials. But, assuming your code is still available, I am proposing that the global be scheduled back into production but perhaps let it run weekly instead of daily. It is unlikely that the global will identify a lot of these problems on a daily basis but at it least it will help catch some of these situations from time to time.

Comment entered 2011-02-15 17:41:44 by alan

BZDATETIME::2011-02-15 17:41:44
BZCOMMENTOR::Alan Meyer
BZCOMMENT::1

William,

Just to be sure I'm thinking of the same thing that you are, I've
attached what I think is an old copy of the output of the report,
i.e., the email that was sent after each run.

Could you confirm that this is the right program to reinstate?

Thanks.

Comment entered 2011-02-15 17:41:44 by alan

Attachment Global.html has been added with description: Example email sent by the global change after a run.

Comment entered 2011-02-15 17:48:20 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2011-02-15 17:48:20
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::2

(In reply to comment #1)
> Created attachment 2083 [details]
> Example email sent by the global change after a run.
>
> William,
>
> Just to be sure I'm thinking of the same thing that you are, I've
> attached what I think is an old copy of the output of the report,
> i.e., the email that was sent after each run.
>
> Could you confirm that this is the right program to reinstate?
>
> Thanks.

Yes. That is the program.

Comment entered 2011-02-15 19:15:38 by alan

BZDATETIME::2011-02-15 19:15:38
BZCOMMENTOR::Alan Meyer
BZCOMMENT::3

Volker has reinstated the program.

We've arbitrarily set it to run every Wednesday night at 5:30 pm.
If that's not a good time for any reason, let me know and we'll
change it.

Comment entered 2011-02-17 12:05:25 by Osei-Poku, William (NIH/NCI) [C]

BZDATETIME::2011-02-17 12:05:25
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::4

(In reply to comment #3)
> Volker has reinstated the program.
>
> We've arbitrarily set it to run every Wednesday night at 5:30 pm.
> If that's not a good time for any reason, let me know and we'll
> change it.

This is Okay.
Verified. Closing Issue. Thank you!

Attachments
File Name Posted User
Global.html 2011-02-15 17:41:44

Elapsed: 0:00:00.001253