TECHNIQUES FOR MANAGING DISRUPTIVE BUSINESS EVENTS

• US 20090319285A1
• Filed: 06/20/2008
• Published: 12/24/2009
• Est. Priority Date: 06/20/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Friesenhahn, Dustin G., Harmetz, Adam, Fan, John D.
• Application Number:
  US12/142,804
• Publication Number:
  US 20090319285A1
• Time in Patent Office: Days
• US Class Current: 705/1.100
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Various technologies and techniques are disclosed for managing disruptive business events. A selection is received from a user to associate one or more items in a content repository with one or more disruptive business events. Once items are associated with events, the business processes around those items change based upon predefined event settings defined on the business events. As users interact with the one or more items associated with the disruptive business event during a normal course of business, one or more actions associated with the event settings are applied. Items associated with disruptive business events can be assigned at different levels in a hierarchy in the content repository. Other applications can retrieve data regarding the disruptive business events.

Claims

1. A method for adding and managing items associated with a disruptive business event comprising the steps of:

receiving a selection from a user to associate one or more items in a content repository with a disruptive business event defined in an events list, the disruptive business event having event settings that have been defined; and

as users interact with the one or more items associated with the disruptive business event during a normal course of business, apply one or more actions associated with the event settings.

2. The method of claim 1, wherein the one or more actions include logging changes that are made to the one or more items.

3. The method of claim 1, wherein the one or more actions include logging access details about the one or more items.

4. The method of claim 3, wherein the access details include a user name of a particular person accessing the one or more items.

5. The method of claim 1, wherein the one or more actions include saving search metadata to describe a search that was used to locate the one or more items.

6. The method of claim 1, wherein the events list is selected from a plurality of events lists that are part of a hierarchy of content repositories.

7. The method of claim 1, wherein the event settings include a request to add the one or more items to a records vault.

8. The method of claim 7, wherein the event settings can be applied to the one or more items in the records vault.

9. The method of claim 1, wherein the event settings include a setting used to ensure that the one or more items cannot be deleted.

10. The method of claim 1, wherein the event settings include a setting used to ensure that changes to the one or more items are audited.

11. A system for managing one or more disruptive business events for one or more content repositories comprising:

one or more content repositories for storing items of content;

one or more disruptive business events that have been associated with at least a sub-set of the items of content; and

wherein the one or more content repositories are operable to control management of the disruptive business events and the associated sub-set of the items of content to ensure that any actions associated with the sub-set of the items through the disruptive business events are applied as users interact with the sub-set of the items.

12. The system of claim 11, wherein at least one of the disruptive business events has been assigned to a particular lawsuit.

13. The system of claim 11, wherein at least one of the disruptive business events has been assigned to a particular audit.

14. The system of claim 11, wherein any item in the content repository can be associated with the one or more disruptive business events that are part of a parent chain of the content repository.

15. The system of claim 11, wherein the actions associated with the sub-set of items can include logging changes that are made to a particular one of the sub-set of items.

16. The system of claim 11, wherein the actions associated with the sub-set of items can include logging search metadata that is used to locate a particular one of the sub-set of items.

17. The system of claim 11, wherein the one or more disruptive business events are defined for items related to different levels in an organizational hierarchy in the content repository.

18. A method for sharing data for disruptive business events with other applications comprising the steps of:

receiving a request from a separate application to access data for a disruptive business event that has been associated with a sub-set of items in a content repository;

retrieving the data that was requested from the separate application; and

returning the data that was requested to the separate application.

19. The method of claim 18, wherein the request is received from the separate application through a web service.

20. The method of claim 19, wherein the data is returned to the separate application through the web service.