System to Manage Users' Accounts and Owned Data on Events Occurrences
Publication Date: 2016-May-13
The IP.com Prior Art Database
Disclosed is a system and methods to apply business compliant rules in the form of standard Application Programming Interface (API) calls/system commands in order to automatically orchestrate a user’s (i.e., employee or organization member) events in relation to the associated applications. A core system translates business rules for the employee events into standard API calls and system commands on the respective systems to ensure compliance to business rules.
Page 01 of 7
System to Manage Users
System to Manage Users'
Within an organization, each employee has an associated digital footprint comprised of electronically stored meetings , events, email, applications, permissions, profiles, etc. These footprints become complex and difficult to manage . Many types of events (e.g., dismissal, vacation, leave, promotion, etc.) require the proper handling of the user's information according to business rules.
Current methods and systems present several disadvantages. Taking action in response to executing employee events requires the involvement of several other employees. Because much of the process can be manual, it is subject to human error or noncompliance to business rules. The incorrect handling of changes represents a security risk. A method is needed to automatically manage the changes related to a user's events in order to maintain compliance with business rules .
The novel contribution is a system and methods to apply business compliant rules in the form of standard Application Programming Interface (API) calls/system commands in order to automatically orchestrate a user's (i.e., employee or organization member) events in relation to the associated applications.
A centralized system transforms an employee's events data and the associated business rules into standard API calls and system commands. The system to which the employee has access and/or is related then invokes/executes said API calls and system commands. All applications must implement the standard APIs and every implementation executes the actions according to specific systems.
One embodiment is to have every system install a module with all of the users' data onto the centralized system . The module implements the API and receives calls from the centralized system that is in charge of transforming employee events coming from the human resources (HR) system into API calls.
Another embodiment is to have a small module installed in the centralized system for every employee . This module knows all the systems related to an employee and uses the centralized system to redirect the API calls to the specific systems , which are in charge of implementing the API.
In an example embodiment, User A, an HR employee, is managing the case for User B, who will be on vacation for three months. Upon User A's approval, the centralized system translates the business rules into several actions, which standard API calls will trigger. In the core of each system, the calls require different implementations:
• Email: delegate/route emails to User C, User B's peer, for three months and delegate meetings to a manager
'' Accounts and Owned Data on Events Occurrences Accounts and Owned Data on Events Occurrences
Page 02 of 7
• Enterprise database on production: downgrade all access permissions to READ • Corporate social network: disable user account.
• Project Management System: move all pending items to User C until User B's return date
The business p...