Title: Message Title
|
|
|
|
|
|
|
eg. A user should not be able to approve a client when the business details API endpoint has not been filled out for that client eg. A Loan cannot be approved when no site visit survey is filled out. eg. A client cannot be closed before the Client Exit Survey is completed. The way to do this would be to extend the current datatables API endpoint and hook it up to a entity_status endpoint. This endpoint would store data such as: Datatable_ID Entitiy_Type Entity_Status (or possibly even the call to which this needs to be applied? Requirement (Warning / Force) This would allow us to setup the workflows flexibly in the DB, and allow a user to reconfigure. We will then use that info to put in the datatables API template which ones are mandatory (so we can enforce in UI/tablet). At the same time we will also write abstract code that allows checking these with a simple method call when handling the request. We can blend this in and will then allow users to do basic customisation of workflows.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues