Method allowing validation in a production database of new entered data prior to their release
First Claim
1. A computer-implemented method of ensuring an integrity of a plurality of updates brought in real-time to a production database concurrently used by one or more software applications, the production database including a plurality of products participating to a definition of objects, the method comprising steps of:
- requesting an issuance of a unique filing number associated to a draft state version of the plurality of updates keeping invisible to end-users of the production database, the plurality of updates;
in the production database, creating or copying from the production database, a set of product items identified as a whole by the unique filing number and gathered under a form of a meta-product on which the plurality of updates is applied;
in the production database, updating the meta-product on which the plurality of updates has been applied;
when updating of the meta-product is complete, in the production database, successively setting into a customizable flow of one or more validation states the meta-product in order to perform a cross-validation of the plurality of updates, wherein the customizable flow of one or more validation states allows returning the meta-product to the draft state when cross-validation of the plurality of updates fail, each validation state qualifying actions are performed on the meta-product identified by the filing number, the validation state is a field stored in association with the filing number in a specific table;
when validation of the meta-product is complete, setting into a production state the uniquely identified meta-product which becomes immediately visible and useable by the end-users of the one or more software applications;
wherein said creating or copying step, said updating step, said validation step, and said setting step are each perform while the production database is concurrently accessed by the end-users; and
wherein said meta-product cannot be accessed by the end-users during said creating or copying step, said updating step, and said validation step.
1 Assignment
0 Petitions
Accused Products
Abstract
A method of insuring the integrity of a plurality of updates brought in real-time to a production database concurrently used by one or more software applications is described. The production database includes a plurality of products participating to the definition of objects. The method first includes requesting the issuance of a unique filing number associated to a draft state version of the plurality of updates while keeping them invisible to the end-users of the production database. Then, a set of product items identified as a whole by the unique filing number are created or copied from the production database and gathered under the form of a meta-product on which the plurality of updates is applied. After updating, the meta-product is successively set into a customizable flow of one or more validation states in order to perform a cross-validation of the plurality of updates. After validation, the meta-product is set into a production state where the uniquely identified meta-product becomes immediately visible and useable by the end-users.
-
Citations
15 Claims
-
1. A computer-implemented method of ensuring an integrity of a plurality of updates brought in real-time to a production database concurrently used by one or more software applications, the production database including a plurality of products participating to a definition of objects, the method comprising steps of:
-
requesting an issuance of a unique filing number associated to a draft state version of the plurality of updates keeping invisible to end-users of the production database, the plurality of updates; in the production database, creating or copying from the production database, a set of product items identified as a whole by the unique filing number and gathered under a form of a meta-product on which the plurality of updates is applied; in the production database, updating the meta-product on which the plurality of updates has been applied; when updating of the meta-product is complete, in the production database, successively setting into a customizable flow of one or more validation states the meta-product in order to perform a cross-validation of the plurality of updates, wherein the customizable flow of one or more validation states allows returning the meta-product to the draft state when cross-validation of the plurality of updates fail, each validation state qualifying actions are performed on the meta-product identified by the filing number, the validation state is a field stored in association with the filing number in a specific table; when validation of the meta-product is complete, setting into a production state the uniquely identified meta-product which becomes immediately visible and useable by the end-users of the one or more software applications; wherein said creating or copying step, said updating step, said validation step, and said setting step are each perform while the production database is concurrently accessed by the end-users; and wherein said meta-product cannot be accessed by the end-users during said creating or copying step, said updating step, and said validation step. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 14, 15)
-
-
12. A computer program product stored on a non-transitory computer readable storage medium, comprising computer readable code means for causing at least one computer to operate instructions comprising:
-
requesting an issuance of a unique filing number associated to a draft state version of the plurality of updates keeping invisible to end-users of the production database, the plurality of updates; in the production database, creating or copying from the production database, a set of product items identified as a whole by the unique filing number and gathered under a form of a meta-product on which the plurality of updates is applied; in the production database, updating the meta-product on which the plurality of updates has been applied; when updating of the meta-product is complete, in the production database, successively setting into a customizable flow of one or more validation states the meta-product in order to perform a cross-validation of the plurality of updates, wherein the customizable flow of one or more validation states allows returning the meta-product to the draft state when cross-validation of the plurality of updates fail, each validation state qualifying actions are performed on the meta-product identified by the filing number, the validation state is a field stored in association with the filing number in a specific table; when validation of the meta-product is complete, setting into a production state the uniquely identified meta-product which becomes immediately visible and useable by the end-users of the one or more software applications; wherein said creating or copying step, said updating step, said validation step, and said setting step are each perform while the production database is concurrently accessed by the end-users; and wherein said meta-product cannot be accessed by the end-users during said creating or copying step, said updating step, and said validation step.
-
-
13. A server side or a client side of a computer program product stored on a non-transitory computer readable storage medium, comprising computer code means for causing at least one computer to operate instructions comprising:
-
requesting an issuance of a unique filing number associated to a draft state version of the plurality of updates keeping invisible to end-users of the production database, the plurality of updates; in the production database, creating or copying from the production database, a set of product items identified as a whole by the unique filing number and gathered under a form of a meta-product on which the plurality of updates is applied; in the production database, updating the meta-product on which the plurality of updates has been applied; when updating of the meta-product is complete, in the production database, successively setting into a customizable flow of one or more validation states the meta-product in order to perform a cross-validation of the plurality of updates, wherein the customizable flow of one or more validation states allows returning the meta-product to the draft state when cross-validation of the plurality of updates fail, each validation state qualifying actions are performed on the meta-product identified by the filing number, the validation state is a field stored in association with the filing number in a specific table; when validation of the meta-product is complete, setting into a production state the uniquely identified meta-product which becomes immediately visible and useable by the end-users of the one or more software applications; wherein said creating or copying step, said updating step, said validation step, and said setting step are each perform while the production database is concurrently accessed by the end-users; and wherein said meta-product cannot be accessed by the end-users during said creating or copying step, said updating step, and said validation step.
-
Specification