As we make new releases, we sometimes deprecate old features. This page lists all the features deprecated per release.
Why are some features deprecated?
Over the years, we have added new features in every release. At the same time, some features are never or seldom used. The product will be bloated if we only add new features and do not deprecate any features. Most times, deprecated features have reasonable workarounds.
How do we decide which features to deprecate?
We work with customers daily across support tickets, conference calls, training sessions, community meets, etc. These interactions give us a fair idea of which features are rarely used.
What should we do if we need a deprecated feature?
Most of them work around. Discuss with your project manager. We are always open to feedback.
Before every upgrade, the customer is expected to test the release on the Test server.
Why don't you ask before deprecating the features?
There is no one way to get such feedback. We have 100s of customers; each customer has 100s of users. Everyone doesn't need to know everything.
There is no automatic upgrade. When you deploy the new release on the Test server, you are expected to test your use cases. You can share them with us; we will help with the testing.
Consensus on such matters is difficult to achieve.
No one wants to throw away something - like items hoarded in the loft or basement.
Deprecated Features List
Version | Feature | Workaround |
|---|---|---|
v10.3 | Recieve Receive Specimens | *Use Workflow |
v10.3 | Rapid Data Entry (participants) | *Use Workflow |
v10.3 | Register Multiple Participants | None |
v11.X | Specimen Tree in on the Participant page | None |
v11.x | Display headers in participant, visit, & specimen pages | None |
v11.x | Process Aliquots | *Use Workflow |
v11.x | Some JSON Configurations (see list below) | |
v11.x | Participant: Anonymize button | None |
v11.x | Participant: Specimen Tree | None |
v11.x | Participant: Specimen Tab | None |
Deprecated JSON Configurations
Set default value for child based on value of parent/primary specimen
Configure collection and received event fields based on specimen collection status
Hide the 'Copy first to all' link on derivative and aliquot pages
Set the default and hide the field in the derived/aliquots creation page
Populate the value based on the selection of other field value/s