MAF CLOUD - NEW RELEASE + FIX UPDATES DEC 2023
29 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
20231218 采销预配
| Enhancement |
| |
yearly settlement follow-up how to test
then do yrly settlement in 2023. see if psl, stock date and remark update correctly. | Enhancement |
| |
Procurement and Sales Planning
need to do calculation for 未配对数量. coz when user insert p and s contract, FE needs to keep update 未配对数量 to follow mapping logic. those 未配对数量 in main table. = 0 rows, should not be shown in the insert table. | Enhancement |
| |
PSP mapping issue unmatchedQty = 可卖库存-已配对数量 e.g., phy_trade_id = 103235 可卖库存 = 合同数量(有实际数量用实际数量,无实际数量用合同数量)-对应的已出库数量 which should be 200 已配对数量: there is no mapped in psp table for trade 103235, so 已配对数量 should be 0
unmatchedQty = 200 - 0 = 200, not 0
| Enhancement |
| |
move bal_qty of stock_mgmt into database level. currently we calcualte bal_qty in BE code lvl, which is not easy to maintain. we will create a new column called match_bal_qty in stock_mgmt. Orm layer will update match_bal_qty whenever insert, update or delete. orm layer done. we are able to get stock_bal_qty directly from database (noted that old data stock_bal_qty may be be correct, but could be update if any update with match_id row)
please remove bal_qty in code level and get bal_qty (stock_bal_qty ) from database directly including in PSP table. testing, you can randomly put stock in / stock out and swap in/out with match id, see if the bal qty is correct.
| Enhancement |
| |
STOCK APPLICATION the correct flow should be application
approval
| Enhancement |
| |
business mode and strategy mapping issue | Enhancement |
| |
new business mode request from HT | Enhancement |
|
14 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
231212 组别盈亏曲线 enable edit group in settings | Enhancement |
| |
231212 归档 Add Archive icon user select phy trades, press ARCHIVE button to archive them.
| Enhancement |
|
12 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
231212 取消合同筛选 | Enhancement |
|
11 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
231207 列定位 在打乱默认格式的前提下使用向左定位,系统会把打乱的列排序恢复成默认排序,视频已发送给CC, 例如,默认列排序是1,2,3,4,5,6, 打乱成1,3,2,5,4,6以后,在3列选择向左定位,应该是1,3列固定不动,后面为2,5,4,6可以拖动;但是现在会恢复成1,2,3列固定不动,后面4,5,6可以拖动 | Enhancement |
|
07 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
phy yearly settlement API changes
| Enhancement |
|
06 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
Procurement and Sales Planning | Enhancement |
| |
Download trade file bug in windows when download file in trade sftp list, have issue in windows. | Enhancement |
| |
add additional header in token to different api_token and login_token | Enhancement |
| |
VaR app add end date auto update tick box | Enhancement |
| |
20231205 结算价 to show maf_group_id (group name) and user_id (user_name), non editable in settlement tab and updated settlement tab
| Enhancement |
|
04 Dec 2023 -VERSION 3.1.7.1
Issue/Request | Type | User Guide | Jira Ticket |
---|---|---|---|
231130 取消的合同 已经取消的合同,如果款项总额是0,在采销资金的下拉框里,就不用显示这笔合同,不然容易认错款; 例如以下已取消的合同,因为款项总额为0,所以这笔合同不会再有款项,因此不用显示在采销资金列表里 只有曾经有过收付款的合同,在合同取消以后,需要进行退款才需要在采销资金列表里显示,待退款完成后,即款项总额累计为0以后,也不用显在采销资金的合同列表里了 point 1: (both conditions met then filter out)
point 2: (both conditions met then fitler out)
| Enhancement |
|