[
http://mifosforge.jira.com/browse/MIFOS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67483#comment-67483
]
Adam Monsen commented on MIFOS-4:
---------------------------------
Fix Version should actually be a previous release, right? Whenever question
groups were introduced?
> KYC capability: Enable "custom fields" to collect structured data
> -----------------------------------------------------------------
>
> Key: MIFOS-4
> URL: http://mifosforge.jira.com/browse/MIFOS-4
> Project: mifos
> Issue Type: New Feature
> Components: Configuration
> Affects Versions: Release 1.0
> Environment: Platform: All, OS: All
> Reporter: sonyabarry
> Assignee: pmqueue
> Priority: Major
> Fix For: Release 2.1.1
>
>
> original reporter and date: emilytucker 2006/03/23
> emilytucker
> 2006-03-23 10:57:32
> Custom fields are described in 6.3.7 from the M1 spec located here:
> MIFOSCVS\Documents\FunctionalSpecification\Mifos Functional specifications.doc
> See below for text. These fields can be used by MFIs to collect additional
> info
> on clients, groups, centers, accounts, etc that aren't being collected by
> Mifos.
> However, these fields are simply open-text fields (although you can specify if
> they should be numeric, date, or text)-- so it will be very difficult for MFIs
> to use these fields to collect structured data that can be queried against.
> For
> example, if an MFI wants to use a custom field to specify clients as
> "non-poor/poor/very poor"-- and then run reports against these various
> segment--they would have to rely on the user to enter the data in consistent
> way. We would like the user to be able to define look-up options for these
> fields. Ideally (perhaps a later enhancement)-- to define certain fields as
> have
> single- select, multi-select, checkbox options, etc. Here is the FS background
> for custom fields as they will currently be built: In addition to the
> pre-defined fields, there will be 10 custom fields to define user data. These
> can be either personal or MFI related fields. • These can be text, date, or
> numeric fields. • The label is provided and content of these fields is defined
> by the MFI at installation level and any change thereon should be notified to
> all the branches • MFI will also specify, which of these fields are mandatory
> and which are not. • If chosen, these fields will be included and positioned
> at
> the bottom of the UI. • The 10 custom fields will be of following types: 2
> date
> formats, 3 integer, 5 text fields.
> emilytucker
> 2006-03-23 10:57:59
> changed to unscheduled.
> emilytucker
> 2006-03-23 10:57:59
> target_milestone
> Target milestone
> Iteration 1
> Unscheduled
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
