Fallback engine for updating selectors of an automation
A method executed by a fallback engine is provided. The fallback engine is implemented as a computer program within a computing system. The method includes tracking information for versions for a selector stored in a selector repository. The information includes a proof of work defining an amount of use per version of the versions. The method includes determining a current state of an original selector version of the selector utilized by an automation and automatically implementing a fallback operation that updates a target of the selector of the automation from the original selector version to a different selector version based the proof of work for the different selector version in the selector repository.
1 . A method executed by a fallback engine of a non-transitory computer readable medium within a computing system to improve processing capabilities of the computing system by comparing last-updated information, the method comprising:
tracking, by the fallback engine, information for one or more versions for a selector stored in a selector repository, wherein the information comprises a proof of work defining an amount of use per version of the one or more versions and changes in the one or more versions of the selector, last-usage of the one or more versions, and last-updated of the one or more versions;
determining, by the fallback engine, a current state of an original selector version of the selector utilized by an automation by analyzing the information for the one or more versions of the selector to determine a different selector version; and
automatically implementing, by the fallback engine, a fallback operation that updates a target of the selector of the automation from the original selector version to the different selector version based the proof of work for the different selector version in the selector repository,
wherein the fallback engine compares an automation failure time with last-updated information to find a newest version.
2 . The method of claim 1 , wherein the fallback engine comprises an object browser configured to browse through the selector repository.
3 . The method of claim 1 , wherein the selector repository receives the selector and the one or more versions as contributions from one or more user devices and stores the selector and the one or more versions.
4 . The method of claim 1 , wherein the proof of work comprises a hit count that defines the amount of use via an incrementing numerical value.
5 . The method of claim 1 , wherein the current state comprises operable, inoperable, out-of-date, and out-of-use, or pointer error.
6 . The method of claim 1 , wherein the fallback engine determines the current state of the selector of the automation based on an alert issued when the automation fails by a user device executing the automation.
7 . The method of claim 1 , wherein the different selector version is a next best selector version comprising a highest value for a proof of work from the one or more versions in a selector repository.
8 . The method of claim 1 , wherein the automation comprises a test automation or a robotic process automation.
9 . The method of claim 1 , wherein the fallback engine analyzes hit counts for all versions and selects a highest hit count version with a last-updated information after an automation failure time.
10 . A computer system comprising a non-transitory computer readable medium storing computer program code and at least one processor executing the computer program code for a fallback engine system to improve processing capabilities of the computing system by comparing last-updated information and to cause the computer system to perform operations comprising:
tracking, by the fallback engine, information for one or more versions for a selector stored in a selector repository, wherein the information comprises a proof of work defining an amount of use per version of the one or more versions and changes in the one or more versions of the selector, last-usage of the one or more versions, and last-updated of the one or more versions;
determining, by the fallback engine, a current state of an original selector version of the selector utilized by an automation by analyzing the information for the one or more versions of the selector to determine a different selector version; and
automatically implementing, by the fallback engine, a fallback operation that updates a target of the selector of the automation from the original selector version to the different selector version based the proof of work for the different selector version in the selector repository,
wherein the fallback engine compares an automation failure time with last-updated information to find a newest version.
11 . The computer system of claim 10 , wherein the fallback engine comprises an object browser configured to browse through the selector repository.
12 . The computer system of claim 10 , wherein the selector repository receives the selector and the one or more versions as contributions from one or more user devices and stores the selector and the one or more versions.
13 . The computer system of claim 10 , wherein the proof of work comprises a hit count that defines the amount of use via an incrementing numerical value.
14 . The computer system of claim 10 , wherein the current state comprises operable, inoperable, out-of-date, and out-of-use, or pointer error.
15 . The computer system of claim 10 , wherein the fallback engine determines the current state of the selector of the automation based on an alert issued when the automation fails by a user device executing the automation.
16 . The computer system of claim 10 , wherein the different selector version is a next best selector version comprising a highest value for a proof of work from the one or more versions in a selector repository.
17 . The computer system of claim 10 , wherein the automation comprises a test automation or a robotic process automation.