Changes

Jump to: navigation, search

Payment Scheduler

2,907 bytes added, 20:20, 10 December 2015
no edit summary
|[[Image:How.png|50px|link=]]
|This article will explain '''how''' you can implement this feature for use on your SmartSimple system.
|}
|}==Overview==New page for generating multiple payments in batch to make payment scheduling easier. Need the ability to schedule L2 payments from L1 based on a set of criteria (total amount, start date, end date, duration). People should be able to set mappings of these criteria to L1 fields and with settings to enable the scheduler on certain L1 types. Mappings for L2 fields are also required (L2 type, L2 status, payment amount, payment date, payment number, etc.)
==How to implement it==
===Enable Payment Scheduler=== - Located at UTA settings >> L1 type. An option "Enable Payment Scheduler" is added.===The field mapping page=== - Located at UTA settings >> L2 >> Payment Schedule Mapping - You will have to map the criteria L1 fields (total amount, start date, end date), and the pre-populated L2 fields (L2 type/status, payment amount, payment date). These fields are mandatory. - You can add additional optional fields (general L2 field or fields under mapped L2 type) to the scheduler. Currently only following field types are allowed: single line text field, multi line text field, select one combo box, and auto number.===Payment Scheduler page=== - Once the Payment Scheduler is enabled and a valid mapping is created, the Payment Scheduler link will appear in edit/view L1 page. - If the L1 doesn't have any payment L2 underneath, the L1 criteria fields with pre-populated values from mapping will appear. All criteria can be modified except for the total amount. - Once criteria is set, click on the Preview button and the system will generate a list of payments. Please note this is created through javascript and just for preview purpose, no actual records created in the system. - For each record: the date is generated according to the criteria date period and frequency; the amount is divided evenly according to total amount and number of payments (except for last record which might contain a remainder); the type and status will be populated according to mapping; all additional fields will be displayed and can be modified, but will not be pre-populated. - The displayed records can be deleted or you can add new ones before submission. - You can re-generate records by modify the criteria and click on Preview button again. - Once everything looks good you can click on the Create Payment button. This will generate actual L2 records in the system and trigger workflow, template formula/status trigger etc. - If the L1 has existing payment L2 underneath, the L1 criteria div will not be displayed. Only total amount is visible. - You can edit the fields for existing L2 payments, delete existing L2 payments or add new ones on this page. Click on Create Payment button to update/add payments.
==Overview==
==Navigating to the feature==
==How to implement it?==
==Illustrated==
==Examples==
==Notes - What are the limitations/restrictions if any?==* If an existing L2 payment is in a locked status, the row will be read only.* There is a validation that the sum of amounts on page should not exceeds total amount.* Allowed field types: single line text field, multi line text field, select one combo box, and auto number. 
==Also See==
 
 
2,004
edits

Navigation menu