Methods and systems for performing change management at login

Abstract

A system and related method for change management at login. The method includes constructing an administratively prescribed target data store as a function of received administrative input prescribing a target feature and target feature-state, and related messages to push to a user upon occurrences of target feature mismatches and matches. Login information, including a username identifier, service provider identifier, and current use time-stamp are received for a user. A historical data store is queried to obtain a user status that associates the username identifier and the service provider identifier with a previously used feature, feature-state and a previous use time-stamp. The target data store is queried for the service provider. Determinations are made as to whether previous feature use matches target feature use. Messages are displayed responsive thereto.

What is claimed is: 
     
       1. A method for change management upon login, comprising:
 constructing, by a change management processor, an administratively prescribed target data store as a function of received administrative input; 
 storing, by the change management processor, the administratively prescribed target data store in a target data database; 
 receiving from an input system, by the change management processor, a login, the login comprising login information for a user, the login information having a username identifier and a service provider identifier; 
 responsive to receiving the login: (a) querying, by the change management processor, a historical data store having stored therein, a user status that associates the username identifier and the service provider identifier with a previously used feature and feature-state; (b) querying, by the change management processor, the administratively prescribed target data store using the service provider identifier, to obtain a target feature and target feature-state, a mismatch message, and a match message; and (c) determining, by the change management processor, whether the previously used feature and feature-state match the target feature and target feature-state, respectively; 
 displaying the mismatch message when the previously used feature and feature-state do not match the target feature and target feature-state, respectively; and 
 displaying the match message when the previously used feature and feature-state match the target feature and target feature-state, respectively. 
 
     
     
       2. The method of  claim 1 , further comprising, when the previously used feature and feature-state do not match the target feature and target feature-state, respectively:
 determining, by the change management processor, that the user is attempting to use an outdated version of the target feature; and 
 displaying an updated version available message responsive thereto. 
 
     
     
       3. The method of  claim 2 , further comprising:
 upon displaying the updated version available message, 
 determining that the user previously used the target feature with the target feature-state and subsequently reverted to using the target feature with the previously used feature-state; and 
 displaying a user prompt asking why the user reverted to the previously used feature-state. 
 
     
     
       4. The method of  claim 1 , further comprising:
 determining, by the change management processor, when a new feature is available; and 
 displaying a new feature available message responsive thereto. 
 
     
     
       5. The method of  claim 1 , further comprising, when the previously used feature and feature-state do not match the target feature and target feature-state, respectively:
 determining, by the change management processor, that the username identifier is not authorized to use any combination of the service provider identifier, the previously used feature, or the target feature; and 
 displaying a failed authorization message responsive thereto. 
 
     
     
       6. The method of  claim 1 , wherein:
 the service provider identifier is one of a plurality of service provider identifiers; 
 the username identifier is one of a plurality of username identifiers; 
 each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and 
 the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature and feature-state. 
 
     
     
       7. The method of  claim 6 , wherein:
 each service provider identifier of the plurality of service provider identifiers has at least one target feature and each target feature of the at least one target feature has a respective target feature-state; and 
 the target data database further has stored therein, for each of the at least one target feature of each service provider identifier of the plurality of service provider identifiers: the target feature-state, the mismatch message, and the match message. 
 
     
     
       8. A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, are configurable to cause the one or more processors to:
 construct an administratively prescribed target data store as a function of received administrative input; 
 store the administratively prescribed target data store in a target data database; 
 detect a login, defined as receiving login information for a user from an input system, the login information having a username identifier and service provider identifier; 
 responsive to the login: (a) query a historical data store having stored therein, a user status that associates the username identifier and the service provider identifier with a previously used feature and feature-state; (b) query the administratively prescribed target data store using at least the service provider identifier to obtain a target feature and target feature-state, a mismatch message, and a match message; and (c) determine when there is a mismatch, defined as the previously used feature and feature-state do not match the target feature and target feature-state, respectively; 
 display the mismatch message when there is a mismatch; and 
 display the match message when there is not a mismatch. 
 
     
     
       9. The non-transitory computer-readable medium of  claim 8 , wherein the instructions are further configurable to cause the one or more processors to, when there is a mismatch:
 determine that the user is attempting to use an outdated version of the target feature; and 
 display an updated version available message responsive thereto. 
 
     
     
       10. The non-transitory computer-readable medium of  claim 9 , wherein the instructions are further configurable to cause the one or more processors to:
 upon displaying the updated version available message, 
 determine that the user previously used the target feature with the target feature-state; and 
 display a user prompt asking why the user stopped using the target feature with the target feature-state. 
 
     
     
       11. The non-transitory computer-readable medium of  claim 8 , wherein the instructions are further configurable to cause the one or more processors to:
 determine when a new feature is available; and 
 display a new feature available message responsive thereto. 
 
     
     
       12. The non-transitory computer-readable medium of  claim 8 , wherein the instructions are further configurable to cause the one or more processors to, when there is a mismatch:
 determine that the username identifier has lost authorization to use any of the service provider identifier, the previously used feature, or the target feature; and 
 display a failed authorization message responsive thereto. 
 
     
     
       13. The non-transitory computer-readable medium of  claim 8 , wherein:
 the service provider identifier is one of a plurality of service provider identifiers; 
 the username identifier is one of a plurality of username identifiers; 
 each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and 
 the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature and feature-state. 
 
     
     
       14. The non-transitory computer-readable medium of  claim 8 , wherein:
 each service provider identifier of a plurality of service provider identifiers has at least one target feature and each target feature of the at least one target feature has a respective target feature-state; and 
 the target data database further has stored therein, for each of the at least one target feature of each service provider identifier of the plurality of service provider identifiers: the target feature-state, the mismatch message, and the match message. 
 
     
     
       15. A change management system, comprising:
 a historical data store having stored therein, a user status that associates a username identifier and a service provider identifier with a previously used feature and feature-state; and 
 a change management processor programmed to: 
 construct an administratively prescribed target data store as a function of received administrative input, the received administrative input specifying, for the service provider identifier: a target feature and target feature-state, a mismatch message, and a match message; 
 receive a login, the login providing login information for a user, the login information including the username identifier and the service provider identifier; 
 query the historical data store with the username identifier and service provider identifier to obtain the previously used feature and feature-state; 
 query the administratively prescribed target data store to obtain, for the service provider identifier, the target feature and target feature-state, the mismatch message, and the match message; 
 determine whether there is a mismatch between the previously used feature and feature-state and the target feature and target feature-state, respectively; 
 display the mismatch message when there is a mismatch; and 
 display the match message when there is not a mismatch. 
 
     
     
       16. The change management system of  claim 15 , wherein the change management processor is further configured to:
 determine that the mismatch represents that the user is attempting to use an outdated version of the target feature; and 
 display an updated version available message responsive thereto. 
 
     
     
       17. The change management system of  claim 16 , wherein the change management processor is further configured to:
 upon displaying the updated version available message, 
 determine that the user previously used the target feature with the target feature-state and subsequently reverted to using the target feature with the previously used feature-state; and 
 display a user prompt asking why the user reverted to the previously used feature-state. 
 
     
     
       18. The change management system of  claim 17 , wherein the change management processor is further configured to:
 determine when a new feature is available; and 
 display a new feature available message responsive thereto. 
 
     
     
       19. The change management system of  claim 15 , wherein the change management processor is further configured to:
 determine that the mismatch represents that the username identifier does not have authorization to use any of the service provider identifier, the previously used feature, or the target feature; and 
 display a failed authorization message responsive thereto. 
 
     
     
       20. The change management system of  claim 19 , wherein the service provider identifier is one of a plurality of service provider identifiers;
 the username identifier is one of a plurality of username identifiers; 
 each username identifier has an association with at least one service provider identifier of the plurality of service provider identifiers; and 
 the historical data store further has stored therein, for each association of each username identifier of the plurality of username identifiers, a respective user status that associates the username identifier and the service provider identifier of the plurality of service provider identifiers, the user status further associating with the service provider identifier, a respective previously used feature, feature-state, and use-timestamp.