Pre-deployment steps
To be done before deployment
|
Check configuration changes and apply them in the application.yaml if the default configuration has been overridden there
|
Check if the release contains migrations. Migrations can affect deployment and downtime.
|
Use GET /i18n/export/{fileName} to download files with current i18n properties. Check if the downloaded file is correct.
|
Post-deployment steps
To be done after deployment
|
Verify permission changes and assign or remove required permissions if they have been overridden
|
Add new properties from the I18n properties changes to the downloaded i18n properties file and add translation for them if needed.
Use POST /i18n/import to upload and apply previously downloaded i18n file with added new properties.
|
Release migrations
–
Changes to notice
–
New functionality
We’ve introduced a new Merchant Portal offering merchants the ability to create invoices, request and receive payments, make withdrawals, view balances and transactions, and manage their points of sale.
Feature
|
Description
|
Benefits
|
Ability to set different commissions which will be deducted from the merchant for merchant payment, depending on how the merchant payment is paid:
|
Commission for paying by wallet will be set in the Contracts, in commissions for System vendor by choosing operation merchant payment and will consist from only one commission total commission which will be deducted from merchant.
Commission for paying by card will be set:
-
in the Vendors for Vendor which is used for payment, with operation type Gate merchant payment
-
in Contracts for Vendor which is used for payment, with operation type Gate merchant payment. This commission will be total commission deducted from merchant.
|
Flexible commission settings let merchants reduce costs for in-system wallet payments compared to card payments
|
Improvements
Feature
|
Description
|
Separated permissions to view client and system transactions and instead of TRANSACTIONS_VIEWER permission implement the following:
|
Back-end changes:
-
if the user has permission SYSTEM_TRANSACTION_VIEWER , APIs return only system business processes
-
if the user has permission CLIENT_TRANSACTION_VIEWER , APIs returns only client business processes
-
if the user has both permissions, APIs returns all transactions
Front-end changes:
-
Show menu System account → View transactions button according to the permission SYSTEM_TRANSACTION_VIEWER
-
Show menu Clients → View profile → Last transactions according to the permission CLIENT_TRANSACTION_VIEWER
-
Show menu Transactions according to the permission CLIENT_TRANSACTION_VIEWER
|
The calculated next fee date when another contract is scheduled is not deleted until new contract is linked.
|
When scheduling a new contract for a user, preserve the already calculated nextFeeDate instead of deleting it immediately.
The existing nextFeeDate remains intact until the new contract is formally linked to the user.
During timer execution, once it’s confirmed that an old contract is inactive, the corresponding nextFeeDate entry in org_prof_monthly_fee_billing_cycle_def will be removed.
|
Added ability to top up the user’s wallet for the service role with appropriate permission
|
Button Requests → Create top-up via bank available for users with permission BANK_TOP_UP_EXECUTOR
|
Fixes
–
API changes
Updated
|
API GET /api/v1/operation-flows can be called with permission CONTRACT_VIEWER
|
API GET /api/v1/commission-profile/{profileId}/limit-rule can be called with permission LIMIT_RILE_VIEWER
|
Added processStatus to POST /invoices/{identifier}/pay response
|
Added processStatus to the POST /merchant-payments/{identifier}/execute response
|
API GET /api/v1/i18n/locales can be called with permission I18N_RECORD_VIEWER
|
The new field createdAt was added to the following API operations:
-
GET /reports
-
GET /reports/{reportId}
|
GET /reports
|
API POST /management/cash-desks/view can be called with CASH_DESK_MANAGER permission
|
Added
|
POST /v1/tasks
|
PATCH /v1/tasks/{taskId}
|
DELETE /v1/tasks/{taskId}
|
GET /v1/tasks/{taskId}
|
GET /v1/tasks
|
POST /v1/schedules
|
PATCH /v1/schedules/{scheduleId}
|
DELETE /v1/schedules/{scheduleId}
|
GET /v1/schedules/{scheduleId}
|
GET /v1/schedules
|
Deprecated/Deleted
|
–
|
I18n properties changes
Added
|
Added two default locales 'es', 'fr' and languages Spanish, French
i18n:
locales: ['en', 'uk', 'ar', 'es', 'fr']
|
Configuration changes
–
Permission changes
Added permission MEDIA_FILE_VIEWER to the following roles by default
- Customer Success specialist
-
KYC specialist
-
AML specialist
|
Removed permission USER_ACTION_VIEWER from the following roles:
-
KYC specialist
-
AML specialist
-
Antifraud specialist
-
Financial specialist
-
CFO
-
Accountant
|
-
Removed permission TRANSACTIONS_VIEWER from existing roles and removed the ability to assign this permission (permission is removed from the system)
-
Added permissions SYSTEM_TRANSACTION_VIEWER and CLIENT_TRANSACTION_VIEWER to the following roles:
-
Added permission CLIENT_TRANSACTION_VIEWER to the following roles:
-
Added permission SYSTEM_TRANSACTION_VIEWER to the following roles:
-
CFO
-
Financial specialist
-
Accountant
|
|
The following permission changes were made for the Revenue analyst role:
-
Removed permission COMMISSION_MANAGER
-
Removed permission LIMIT_RULE_MANAGER
-
Added permission CURRENCY_VIEWER
-
Added permission CONTRACT_VIEWER
|
New permission added LIMIT_RILE_VIEWER
|
Permission LIMIT_RILE_VIEWER added to the role Revenue analyst
Permission LIMIT_RULE_MANAGER removed from the role Revenue analyst
|
New permission added I18N_RECORD_VIEWER
|
Added permission I18N_RECORD_VIEWER to the following roles by default:
-
CRO
-
Revenue specialist
-
Revenue analyst
-
Financial specialist
-
Antifraud specialist
|
Removed permission I18N_RECORD_MANAGER from the following roles:
-
Financial specialist
-
Antifraud specialist
|
Added permissions I18N_RECORD_MANAGER, BANK_TOP_UP_EXECUTOR to the following roles:
|
Added permission USER_INITIATOR to the Customer success specialist
|