refinement of the action "Distribute payments among processes based on expected payments" (distribution of payments among several processes while maintaining the original payment)
the action "Distribute payments among processes based on expected payments" needs to be improved in such a way that the action automatically distributes large payments to several processes and at the same time the main payment is saved
for this add to action:
- check the box "Automatically create subpayments in accordance with the expected if several expected payments were found according to the configured selection conditions"
- the "method" field, consisting of the options "pay off earlier (FIFO)" and "pay off later (LIFO) first"
when this checkbox is enabled
must happen
1. the actual payment that is being processed is marked as virtual
2. If in the "method" field "repay the earliest (FIFO)" is selected, then sort the expected by creation date in ascending order, otherwise, if "repay the later (LIFO) first", then sort "Descending"
3. as many subpayments are created as the amount of the original
Original question is available on version: ru
for this add to action:
- check the box "Automatically create subpayments in accordance with the expected if several expected payments were found according to the configured selection conditions"
- the "method" field, consisting of the options "pay off earlier (FIFO)" and "pay off later (LIFO) first"
when this checkbox is enabled
must happen
1. the actual payment that is being processed is marked as virtual
2. If in the "method" field "repay the earliest (FIFO)" is selected, then sort the expected by creation date in ascending order, otherwise, if "repay the later (LIFO) first", then sort "Descending"
3. as many subpayments are created as the amount of the original
Answers:
Pereginyak Alexander wrote:
layout https://www.figma.com/file/8rgRpCkKzcagoBkYO5biUU/Untitled?node-id=1%3A9
There is too much extra on your layout that is not described in the task - why is this layout in the description? If there should be more settings according to the layout, please describe them.
28.12.2020, 10:39
Original comment available on version: ru
Tyndyk Maxim Vadimovich wrote:
There is too much extra on your layout that is not described in the task - why is this layout in the description? If there should be more settings according to the layout, please describe them.
I see that you initially detailed a large TK into tasks in order to get free answers on the forum - tricky)
Here https://crm-onebox.com/ru/support/finances/5071-dorabotat-deystvie-quotraspredel... answered on multi-setting
Question for this issue:
Pereginyak Alexander wrote:
1. the actual payment that is being processed is marked as virtual
3. as many subpayments are created as the amount of the original payment is enough to cover the existing pending payments (take into account the sorting from paragraph 2.)
What if the amount of expected payments is less than the actual payment? if we make it virtual with incomplete separation, we will get the actual shortage of the payment amount in OneBox than in reality
Pereginyak Alexander wrote:
- the "method" field, consisting of the options "pay off earlier (FIFO)" and "pay off later (LIFO) first"
+1 hour to previous estimates, subject to the implementation of the clause on the creation of subpayments
28.12.2020, 10:49
Original comment available on version: ru
Tyndyk Maxim Vadimovich
Administrator wrote:
There is too much extra on your layout that is not described in the task - why is this layout in the description? If there should be more settings according to the layout, please describe them.
this is the layout of the final result, which is described in the complex TOR (link)
28.12.2020, 11:06
Original comment available on version: ru
Tyndyk Maxim Vadimovich
Administrator wrote:
I see that you initially detailed a large TK into tasks in order to get free answers on the forum - tricky)
sorry, you are wrong. I initially delivered a complex technical specification, with which Ustimenko sent me to the integrator)))))
28.12.2020, 11:06
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
