fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Raymundi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FINERACT-209) Maker-Checker principle for Document management
Date Fri, 12 Aug 2016 19:57:20 GMT

    [ https://issues.apache.org/jira/browse/FINERACT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419362#comment-15419362
] 

Lionel Raymundi commented on FINERACT-209:
------------------------------------------

As we discussed in the dev mailing list, document upload is not a simple command which modifies
the database, but also creates files, the suggestion is to leave the document creation command
untouched and add a flag to the document to determine whether it has been verified or not.
Finally, there should be a different command to mark it as verified. This new command is the
one which should be under maker-checker workflow.

> Maker-Checker principle for Document management
> -----------------------------------------------
>
>                 Key: FINERACT-209
>                 URL: https://issues.apache.org/jira/browse/FINERACT-209
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Lionel Raymundi
>            Assignee: Markus Geiss
>
> For some scenarios, it is useful to validate that a document linked to a client or loan
is valid. For example if customer uploads his own documentation (company balances, person
identification, etc.) it would be needed that someone verifies that the documents are correct.
> It would be interesting if any fineract user with a role which has check capabilities,
could see the pending verification task under the maker-checker tray.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message