By "reached the end of their record retention timeline" do you mean A) you have a need to erase any record of these projects from Ariba or B) you would like to remove records from being searchable and used in Ariba? Or is there another reason?
We are looking at option A...these are records/contracts that would have been destroyed after whatever their applicable retention policy stated, and we are looking to have some way to mimic that in Ariba.
1 of 1 people found this helpful
I recently learned the same from Ariba technical support: that there exists no such purge capability or business rules such that Ariba customers can comply with records retention policies. This is a crucial piece of functionality of any content management system, and I too was surprised to learn of its absence in Ariba OnDemand. Absence of purge capabilities leaves customer companies exposed to information discovery long after contracts and other records should have been deleted from Ariba.
I therefore submitted ER 1-BE5029. Since Ariba has had customers in their OnDemand environment for several years now, customizable purge capabilities will become a hot topic (particularly Ariba customers who loaded any previously-executed agreements which may have subsequently expired). I proposed the business rules be customizable and that it would tie to customizable workflow for notification of records about to be purged.
Thanks Mike! Do you know if your ER has been accepted/prioritized? If not, I'll submit one too...the more demand the more likely it will happen sooner than later!
Thank you, Sybil. The status of my ER 1-BE5029 is "New", so I assume it has not yet been accepted or prioritized. I submitted on 11July2011. Please submit your request. I believe the need for archival/purge to comply with various records retention policies is self-evident for any content management system. However, having multiple requests may help alert Ariba to this gap in their solution. Incidentally, such a solution should help mitigate some of their storage costs long-term.
I was surprised to receive the following response to ER1-BE5029 yesterday. If compliance with your company's records retention/purge policy is a key part of your needs, I'd recommend you also submit an enhancement request.
"Thank you for submitting Ariba Enhancement Request 1-BE5029, This Enhancement Request was described as follows: Records Retention policy compliance.
After reviewing this Enhancement Request, we have determined that based on current priorities and resources we will not be able to implement this enhancement within the next 18 months. We will reconsider this enhancement at a future date."
Wow. That's disappointing to say the least...thanks for the update Mike
As a workaround to your problem, you could use access control settings to limit the visibility of workspaces needing to be archived to a single account. This was hinted at in a previous post. To do so, you could create a user account with a name such as "Archive User" and then do a mass update of projects to replace the workspace owner with the Archive User account, as well as change the access control for all such workspaces to Owner Only. In doing so you would limit the visibly of all such workspaces to the single account, removing all possible access of the workspaces from the general user base.
You may also need to replace the members of the "Project Owner" group in the workspace with the Archive User account, but again this can be done using the mass edit wizard. The entire process would be relatively quick to complete.
You would still need to filter the results out of any reports, but filters based on Workspace Owner to exclude the necessary workspaces should be relatively easy to add.
Thanks Kevin. I appreciate the idea and have two concerns with that approach: 1. There's not yet a means to set an archival date, so Mass Edit might be of limited use. 2. The approach only hides the workspaces from reports; it does not truly destroy them as most Records Management Policies would require.
We brought that up to our legal team when the issue first presented itself, but the issue is discoverability. It is my understanding (and I'm certainly not a lawyer!) that if anyone within our company or within Ariba can access these documents (even just a shell of the original) that the items are available for legal discovery...which leaves us out of compliance with our company's policy.
I was definitely glad to see this string of comments regarding the Contract Workspace/Request Archival Process. HP has a huge need for this functionality so that we can destroy the records that exceed our record retention policy. We are being told by Ariba that we are the only customer asking for this functionality. Hence, since we are the only customer, Ariba is not going to be working on it any time soon. It would be great to know all the companies that are looking for this functionality so that we can band together. Please respond if your company needs the ability to permanently your upstream data from your Ariba database.
As a point of reference, I wanted to make sure that everyone knows what changes happen to a workspace when it is deleted:
The Project "Object" is actually deactivated so that it is only accessible to users with Deleted Documents Access.
- Tasks and phases are set to inactive. All tasks are assigned to the Project Owner Group regardless of original Task owner
- Template answers are deleted entirely
- Team groups and members are deleted entirely except the Project Owner group which is set to inactive.
- Folders are set to inactive
- Main Agreement and Contract Addenda are set to inactive
- Subprojects are set to inactive and handled the same way as the deleted project
- All other documents are deleted entirely
So is this what happens now? or What is designed for the future? The problem with what you have stated is that the record can still be retrieved by someone with special access. We have 2 scenarios - 1. We would like to archive the records off of the Ariba Database into our Archiving system. 2. If we keep records in the Ariba database for their life according to our record retention policie, then once the contract workspace life has been exceeded we want to destroy the record in the Ariba database like it never existed.
Debra, this is the same need Reed Elsevier has (and likely 90%+ of other Ariba customers have). Well-articulated. Thank you,
I'm simply stating what happens now.
Was this ER completed by Ariba?
I have been approached by Ariba to submit a CRD (Customer Requirements Document) on this Records Retention / purge issue. Please let me know if you would like to contribute. Thus far, the most crucial components I've captured are:
- The ability for all data and attachments to be purged & destroyed in such a manner that it cannot be recovered or discovered following destruction.
- A configurable workflow which will route to a person(s) or group(s) within X days of the pending destruction/purge date and reminders every Y days thereafter.
- The ability to “save” or “rescue” a record/data from the automated/scheduled purge date.
- The ability to set predefined rules for a purge date to be automatically applied (e.g. X months/years following the Expiration Date of a contract, or Y months/years following the Closing Bid Date on a sourcing event, or Z months/years following an SPM survey).
- The ability for an Owner or Administrator to modify the purge date up until the date itself.
- The option to transfer those records to a portable media for “offline” storage when/if needed (e.g. for a record which is part of an active litigation or investigation).
I welcome your input as interested stakeholders as well. Thank you!
The ability for all data and attachments to be purged & destroyed
in such a manner that it cannot be recovered or discovered following destruction.
A configurable workflow which will route to a person(s) or group(s)
within X days of the pending destruction/purge date and reminders every Y
The ability to “save” or “rescue” a record/data from the
automated/scheduled purge date.
The ability to set predefined rules for a purge date to be
automatically applied (e.g. X months/years following the Expiration Date of a
contract, or Y months/years following the Closing Bid Date on a sourcing
event, or Z months/years following an SPM survey).
The ability for an Owner or Administrator to modify the purge date up
until the date itself.
The option to transfer those records to a portable media for “offline”
storage when/if needed (e.g. for a record which is part of an active
litigation or investigation).
Just wondering if you're still looking for contribution to the CRD as I am interested in contributing.
I am glad other enterprise customers have articulated this issue, my own organisation is similarly affected
My hope is that SAP leverage their extensive relationship with vendors like OpenText (Content Server) to provide a productised integration so that this can be offloaded / externalised from Ariba.
Information storage does not equate to information management
The use of CMIS may provide options to leverage OpenText or other industry leading ECM solutions that support this industry standard.
- See more at: http://exchange.ariba.com/message/8456#8456