IP Library Granted Patent US 11,748,167
Granted Patent B2
US 11,748,167 · App. 17/818,422 · Granted Sep 5, 2023

Dynamic toggle of features for enterprise resources

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,748,167
App. No.
17/818,422
Filed
Aug 9, 2022
Granted
Sep 5, 2023
Kind
B2
Examiner
SUN, CHARLIE
Art Unit
2196
USPC
718/102
Abstract

A system, method and program product for handling potentially problematic events in an enterprise computing platform. A method is disclosed that includes: determining whether a received event includes a feature driven folder processing event; in response to a determination that the event is not a feature driven folder processing event, process the event and determine whether a file count for a folder is impacted; in response to the file count being impacted, evaluate the file count relative to a set of processing thresholds to determine which feature driven folder processing events are enabled for the folder, and to update associated metadata for the folder; and in response to a determination that the event is a feature driven folder processing event, using the computing device to check the metadata for an associated folder to determine whether a requested feature is enabled.

Claims (30)

1. A method for processing events for a content collaboration platform, comprising:

determining, by a computing device, whether a received event includes a feature driven folder processing event;

in response to a determination that the event is not a feature driven folder processing event, using the computing device to process the event and determine whether a file count for a folder is impacted;

in response to the file count being impacted, using the computing device to evaluate the file count relative to a set of processing thresholds to determine which feature driven folder processing events are enabled for the folder, and to update associated metadata for the folder; and

in response to a determination that the event is a feature driven folder processing event, using the computing device to check the metadata for an associated folder to determine whether a requested feature is enabled.

2. The method of claim 1 , wherein in response to a determination that the requested feature is not enabled, preventing processing of the requested event.

3. The method of claim 1 , wherein in response to a determination that the requested feature is enabled, processing of the requested event.

4. The method of claim 1 , wherein the feature driven folder processing event is selected from a group consisting of: a move operation, a copy operation, and a search operation.

5. The method of claim 1 , wherein the metadata associated with the folder dictates which features are enabled.

6. The method of claim 1 , wherein the content collaboration platform is implemented by an enterprise computing platform that processes events from an event pipeline.

7. The method of claim 6 , wherein the enterprise computing platform includes an application programming interface (API) for receiving events.

8. The method of claim 1 , wherein determining whether a file count for a folder is impacted includes determining whether a number of files in the folder increased or decreased.

9. The method of claim 1 , wherein the configuration settings include a threshold value for each feature driven folder processing event.

10. The method of claim 1 , wherein feature driven folder processing events do not include at least one of: a file upload, a file download, a file move, a new file creation, or a folder rename.

11. A computing system, comprising:

a memory; and

a processor configured to process events for a content collaboration platform, including:

determining whether a received event includes a feature driven folder processing event;

in response to a determination that the event is not a feature driven folder processing event, processing the event and determining whether a file count for a folder is impacted;

in response to the file count being impacted, evaluating the file count relative to a set of processing thresholds to determine which feature driven folder processing events are enabled for the folder, and to update associated metadata for the folder; and

in response to a determination that the event is a feature driven folder processing event, using the computing device to check the metadata for an associated folder to determine whether a requested feature is enabled.

12. The computing system of claim 11 , wherein in response to a determination that the requested feature is not enabled, preventing processing of the requested event.

13. The computing system of claim 11 , wherein in response to a determination that the requested feature is enabled, processing of the requested event.

14. The computing system of claim 11 , wherein the feature driven folder processing event is selected from a group consisting of: a move operation, a copy operation, and a search operation.

15. The computing system of claim 11 , wherein the metadata associated with the folder dictates which features are enabled for the folder.

16. The computing system of claim 11 , wherein the content collaboration platform is implemented by an enterprise computing platform that processes events from an event pipeline.

17. The computing system of claim 16 , wherein the enterprise computing platform includes an application programming interface (API) for receiving events.

18. The computing system of claim 11 , wherein determining whether a file count for a folder is impacted includes determining whether a number of files in the folder increased or decreased.

19. The computing system of claim 11 , wherein the configuration settings include a threshold value for each feature driven folder processing event.

20. The computing system of claim 11 , wherein feature driven folder processing events do not include at least one of: a file upload, a file download, a file move, a new file creation, or a folder rename.