All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
We found today that archived data related to requests posted through compose have been purged. I see there is a service to do this and it reads a parameter value which we can control and turn off by setting it to zero. (cMass.dbo.ztParam.PostingArchiveRetentionInterval) So we can stop this but this parameter was set to 5 days by default. Removing archives typically doesn't occur for a period of around 7 years. I would suggest changing this to 0 as default for future installations.
Hi Doug,Given that dspCompose has to ship with a default retention value of some kind, then I don't think there's going to be a single value that works for every situation. 0 might work well for a Pharma site, but over time could cause problems for many other sites and it's bad practice to ship with an infinite retention period.You could try to convince PM to change this, but I don't think it's anything we can enter as a bug. My understanding is that Pharma environments have extensive procedure guides. Could it not be that setting this parameter appropriately for the environment at hand be part of that procedure as a post-setup step?Regards,C.
Hi Chris, I agree it's not a code bug but wanted to make the issue known. dspConduct ships with an infinite retention period and to me this should be standard for all governance solutions. The practice of purging your audit trail should be an option in my opinion not a default setting.
Hey Doug, That's a fair point. I'll tag JP Grippa on this to see what he says.
Chris, I agree with you, but also see Doug's point. Please create a feature request and we can debate the pros and cons as part of the idea approval process.
Hi Doug,JP feels this should be a feature request. I'll get that started and let you know the request number.
Douglas Hoffman
This has been considered part of post installation configuration and is mentioned in the implementation guide for dspCompose as part of the Set Parameters task in implementation.
As you mentioned there is no best value and like all other parameters this needs to be set up front as part of post installation.
Archies should not be deleted for more than 5 days however and we will update the delivered parameter and help around this field.
I think we should ship with a default of 0, as that enables the same behavior as in dspConduct. Out of the box, Conduct and Compose function differently otherwise. Having too much data is an easier problem to solve than losing data and not realizing it.
Attachments Open full size