4 Replies Latest reply on Feb 28, 2011 5:14 AM by gmkumar2005

    Maker-Checker Support Envers

    gmkumar2005

      Hi,

      Can any one help me how to solve these use cases for maker-checker functionality

       

      1) Maker creates a request to create an entity (eg department)

                -- Data should not be inserted to entity tables . It has to be recorded in audit tables

      2) Checker retrives list of entities for authorization

                -- Data should be queried from audit table

      3) Checker views the pending request

                     -- Display original record along with changes

      4) Checker authorizes the request

                -- Data is moved/overwrite from audit table to enity table. 

      5) Maker requests to modify an entity

                  -- Entity tables will not be modified. The changes are recorded in audit tables. Changes will move the entity tables only upon authorization.

      The solution is expected to address following constraints

       

      1) Master-Detail ie, Dept contains Employees

      2) Bulk authorization , ie, When there are say 10,000 employees in a department the authorization process should have reasonable performance. The final use case has to execute  data validations + authorization  rules + moving data from audit tables to entity tables.

      3) All above use cases apply to Master-Detail.

       

      I like to know from envers experts is it feasible to implement all above usecases using envers ?

      What changes will be needed in Envers ?

       

      Thanks in advance

      --Kiran.Kumar

        • 1. Maker-Checker Support Envers
          adamw

          I think that you are rather looking for a workflow solution, not an auditing one.

          So I would look at workflow frameworks

           

          Adam

          • 2. Maker-Checker Support Envers
            gmkumar2005

            Adam thanks for the reply.

            The use-cases I mentioned should be modelled as actions with in a workflow.

            Workflow will be used to handle issues like What should happen after a request is created? --> should go for authorization --> who is the authorizer --> apply some rule based on say amount/org structure, find authorizer --> authorizers take an action (auth/reject).

             

            I am looking for a solution which can simlify the action.

            Can we have a design  where I define an entity and i get all the above use cases (ignore the UI) . Workflow part could be developed using drools or some other custom code.

             

            --Kiran.Kumar

            • 3. Maker-Checker Support Envers
              adamw

              Well for workflows I would recommend jbpm/drools (flow) or similar. Envers is really only for auditing

               

              Adam

              1 of 1 people found this helpful
              • 4. Maker-Checker Support Envers
                gmkumar2005

                Thanks a lot adam. My requirements actually maps to master data management. You are right, my expectations are misplaced. I will continue my discussions with drools experts.

                --Kiran.Kumar