Hi Binny,
It's good to enhance the configuration table by modifying "value" column to
VARCHAR which can be used for various purposes in the application.
If we are introducing "Trapdoor Configurations" then apart from
restrictions we need to have predefined enum values for these
configurations.
regards
Ashok
On Wed, Sep 24, 2014 at 8:37 AM, Binny Gopinath Sreevas <
[email protected]> wrote:
> All,
>
>
>
> Does it make sense to introduce “Trapdoor Configurations” in Mifos X? This
> will work similar to some of the configurations that were available in
> Mifos 2.x. These configurations can be changed initially during setup, but
> once some processing has happened, then cannot be changed again.
>
>
>
> For example: “Post interest at end of current period” Or “Date of
> Financial year beginning” – which once configured and interest is posted
> based on these configurations – we should not allow a user to change this
> value again. Till the time interest is posted for the first time, an
> administrator may change these configurations, but not after that. My
> thought is that it is better to introduce some restrictions on changing
> these configurations rather than ensuring that Mifos platform will handle
> all possible scenarios caused by changing these values.
>
>
>
> Rough thought on implementation:
>
>
>
> Introduce two more columns in the c_configuration
> table:
>
>
>
>
> *CREATE* *TABLE* `c_configuration` (
>
> `id` *BIGINT*(20) *NOT* *NULL* *AUTO_INCREMENT*,
>
> `name` *VARCHAR*(50) *NULL* *DEFAULT* *NULL*,
>
> `value` *VARCHAR*(256) *NULL* *DEFAULT* *NULL*, à This column is
> currently decimal. May need to be changed to varchar for future needs.
> Needs more thought.
>
> `enabled` *TINYINT*(1) *NOT* *NULL* *DEFAULT* '0',
>
> `is_trapdoor_setting` *TINYINT*(1) *NOT* *NULL* *DEFAULT* '0', à New
> column to be introduced, default “No”
>
> `trapdoor_setting_open` *TINYINT*(1) *NOT* *NULL* *DEFAULT* '1', à New
> column to be introduced, default “Yes” – to be used only if
> is_trapdoor_setting is set to “Yes”. If set to “No”, then this
> configuration may no longer be modified
>
> *PRIMARY* *KEY* (`id`)
>
> )
>
>
>
> If is_trapdoor_setting is “No”, then current behaviour continues.
>
> If is_trapdoor_setting is “Yes” trapdoor_setting_open is “Yes”, then this
> configuration value may be changed.
>
> If is_trapdoor_setting is “Yes” trapdoor_setting_open is “No”, then this
> configuration value may NOT be changed any more.
>
> If is_trapdoor_setting is “Yes”, then one of the Mifos X components (like
> the batch job which does interest posting) will set the
> trapdoor_setting_open from “Yes” to “No” when it does any interest
> posting for the first time.
>
>
>
> Let me know your comments on this.
>
>
>
> Thanks
> Binny
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> Mifos-developer mailing list
> [email protected]
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users
