US 11,720,953 B2
Methods and systems for performing change management at login
Eric Schultz, San Francisco, CA (US)
Assigned to salesforce.com, inc.
Filed by salesforce.com, inc., San Francisco, CA (US)
Filed on Sep. 23, 2021, as Appl. No. 17/448,696.
Application 17/448,696 is a continuation of application No. 16/773,277, filed on Jan. 27, 2020, granted, now 11,151,638.
Prior Publication US 2022/0012797 A1, Jan. 13, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/00 (2019.01); G06Q 30/0601 (2023.01); G06F 16/21 (2019.01); G06F 16/23 (2019.01); G06F 16/248 (2019.01); G06F 16/25 (2019.01); G06F 8/65 (2018.01); G06F 21/31 (2013.01); H04L 9/40 (2022.01); G06F 8/71 (2018.01); H04W 4/60 (2018.01); G06N 5/022 (2023.01); G06F 16/835 (2019.01)
CPC G06Q 30/0635 (2013.01) [G06F 8/65 (2013.01); G06F 8/71 (2013.01); G06F 16/219 (2019.01); G06F 16/2379 (2019.01); G06F 16/248 (2019.01); G06F 16/252 (2019.01); G06F 21/31 (2013.01); H04L 63/08 (2013.01); H04W 4/60 (2018.02); G06F 16/8358 (2019.01); G06N 5/022 (2013.01)] 20 Claims
OG exemplary drawing
 
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.