Implementing a change control sytem

Idea created by jrenfrew on Oct 4, 2017
    Active
    Score4
    • jrenfrew
    • sgripman
    • jbante
    • User26081

    Change control

    >> Change control within quality management systems (QMS) and information technology (IT) systems is a formal process used to ensure that changes to a product or system are introduced in a controlled and co-ordinated manner

     

    Change control is often applied to the sofware build phase, what if this applies to the data?

     

    One of the major benefits of FileMaker is that record changes are immediately saved, and updated everywhere.

    There are some well established techniques for making this a transactional event so that all required changes are applied or none.

     

    What if the business rule is that NO changes may be made after initial entry unless approved?

    What if only some of the fields in a table have this rule applied to them?

    How do you lock a record from further editing, or signal that there is a 'change control' in play, and what if the same record has more than one of these?

     

    How to re-use components so the requirement can be easily appplied across the whole system.

    Can card windows help with the interaction?

    What if a change is not approved?

    How to work out what other records in the app are affected, and lock them if they are in a dependant chain

    What does FileMaker have natively that helps with the task?

     

    What are the benefits? What is the technical debt? How much extra work is involved?

    Can you test it?