Akinon Release Notes (04.01.2024)
Last updated
Was this helpful?
Last updated
Was this helpful?
Fixed the Synchronization Problem on Data Sources
Updates to supplier codes in the data sources now synchronize correctly with Commerce.
Whippy Ware and Dynamic Price SSO Integration
With this development, it has been ensured that login can be performed with the providers added to Omnitron for Dynamic Price and Whippy Ware. To enable the usage of OAuth providers, these providers must be defined in the OAUTH_PROVIDERS dynamic setting of the relevant applications.
Adding Filtering Options on Localizable Attributes
Localizable attributes can now be filtered for Price List, Stock List, and Category Items.
UI Protocol - Added Visible Type to Application Config
During application creation, the visible_type attribute must now be included, indicating whether the application is a fullpage or a plugin. By default, it will be set to fullpage.
Enhanced Filtering Options for Price List Detail Page
Users can now filter data using CSV and XLS formats on the Price List Detail Page, accessible through Sales Channels > Sales Channel Settings > Marketplace Operations > Price Update.
Order Detail Comment Feature
A comments section has been added to the Orders page, allowing users to take notes related to specific order numbers. Access this feature through Orders > Order No.
Single Sign-On Feature
A new feature has been implemented allowing users to enable Single Sign-On (SSO) functionality. Users can access this feature through Settings > SSO Settings, where they can fill out the necessary fields for providers and enable the SSO function.
UX/UI Improvement
The Store Management category has been added to the Sales Channels, enhancing navigation and making store-related pages more accessible and relatable for users.
System improvements have been made to improve the "Remove All Products" action on the Category Product List.
Oney Payment Package Enhancement
As part of the Oney payment package development, a hash structure has been added to ensure a more secure communication. Now, when the sessionId parameter is passed from the view to the extension, it is included as a parameter and a SHA512(salt|sessionId|hash_key) is generated, then added to the form sent to the extension.
Improved Feed Processing with Multipart Upload
To address issues encountered with Google feed functionality in brands boasting extensive product catalogs, a multipart upload feature has been introduced. This enhancement enables the fragmentation of large data sets into smaller parts and subsequently merges them.
Store Condition in Campaigns
A new feature has been introduced to enhance campaign customization: the "Store" condition. This addition allows users to specify specific stores as conditions within their campaigns.
Python 2 to Python 3 Alignment
The system has been upgraded to align with Python 3, ensuring compatibility with the latest technologies and standards.
Improved Sorting in Distribution and Transfer Scenario Lists
The page no longer refreshes after sorting on the Scenario Listing page. Style enhancements have been made to clearly indicate where a dragged row will be placed during drag-and-drop interactions between rows. Drag-and-drop functionality has been disabled when any filter is applied on scenario listing pages to ensure clearer sorting.
Consistent Design for Info Icons
Info icons added to the page have been changed to white to maintain consistency with the overall design of OMS. Additionally, their sizes have been adjusted accordingly. Users can access these info icons through Stock Locations > Create Stock Location.
Update Feature Added to Related Location Addition Form
The ability to update sub-stock locations has been added to the addition form. Clicking on a sub-location item in the related locations list now directs users to the update form. Users can access this feature through Locations > Related Locations.
Integration of OMS and Seller Center
The integration of OMS and Seller Center processes has been successfully completed. This allows packaging processes from Seller Center to be managed within OMS, streamlining operations and providing centralized control.
Delivery Type Filtering
Users can now filter packaging orders based on delivery type, enabling separate control of packages for each delivery method. Access this feature through Packaging Orders > Delivery Type filter.
Enhanced Packaging Document Security
Packaging document data accessed in package details can now be displayed based on the id_encrypted field, ensuring more secure storage of all packaging document information.
Simplified Delivery Address Selection
Unnecessary parentheses in the courier company text have been removed during the selection of delivery addresses in the address and shipping information step. This enhances clarity and improves the user experience.
Dynamic Homepage Menu Names
Homepage menu names are now dynamically adjusted based on the data received from the backend, ensuring consistency and flexibility in menu naming.
Visual Enhancement Modal Adjustments for Right-to-Left Support
Modal adjustments have been made to enhance visuals, accommodating right-to-left support.
Versions Improvement
During the project creation process, the Versions table is now automatically generated. This enhancement ensures that all steps of the flows, including their initial creation details, are stored in the version table.
Version ID search functionality has been added to the Version table.
Character validation has been implemented for the Version Message content.
Logging Improvement
The logging QueryRecord operation has been optimized for improved performance. This enhancement allows log queries to occur more quickly and efficiently, enhancing the overall logging system's responsiveness.
Alarms Improvement
Auto Resolved feature has been developed in the Alarm Service. This feature automatically marks alarms as resolved when their status is no longer active, even if not manually marked by the user.
Pagination functionality has been added to the Alarm Detail Popup, allowing users to navigate through alarm details more efficiently, especially when dealing with a large number of alarms.
Flows Improvement
The name of the Testing Tab has been changed to Flow Trigger, providing users with clearer understanding that the triggers are live and not solely for testing purposes.
Security Improvement
In addition to token validation, user authorization checks have been implemented for Backend (BE) requests.
Successful Completion of PCI DSS Level-1 Audit and Renewal of Certification
We are pleased to announce the successful completion of the PCI DSS (Payment Card Industry Data Security Standard) audit, ensuring continued compliance with industry standards for secure payment processing.
Additionally, Akifast certification has been renewed for another year, demonstrating Akifast commitment to maintaining the highest standards of data security and protecting sensitive customer information.
Admin Dashboard - Integration of User Deletion Button
An integration has been implemented in the Admin Dashboard, allowing administrators to delete users directly from the Akifast User List.
Garanti Reconciliation Flow - Void Transactions
Void transactions have been added to the Garanti Reconciliation Flow. Previously, automatically voided transactions were included in reconciliation reports. With this enhancement, the reconciliation process now ensures synchronization between the status of transactions in Garanti and Akifast.
Merchant Back Office - Payment Sessions
Two new pages have been added to the Merchant Dashboard, allowing users to view payment sessions that are in a "Failed" or "Expired" state.
Additionally, new data related to payment sessions has been added, providing users with enhanced visibility and control over payment session details.
Transition to Hash V3 for Nestpay Integration
In response to Nestpay's announcement regarding the discontinuation of Hash V1 support effective March 31, 2024, the transition to Hash V3 has been successfully completed. This update ensures compatibility with Nestpay's latest security protocols and safeguards the integrity of payment transactions processed through the integration.
Mobile​
Resolved an issue where the application would close itself when navigating from the Product Search screen to the Barcode Scanner.
Fixed an issue in the Android environment from Env 3.4 onwards where products on the Basket Page failed to follow finger movements when swiped to the right.
Mobile​
Unit Tests for Core Elements
Enhancements have been made to the framework functionalities with the addition of new unit tests for core elements.
Scrollable Content in Bottomsheet Component
The Bottomsheet Component now supports simultaneous scrolling with scrollable content, providing a smoother user experience.
Credentials Screen Instead of Pop-Up View
The Projects>Credential Page has been redesigned as a separate page instead of a Pop-Up View, providing a more intuitive and user-friendly experience.
Editing Credential Pop-Up
Pop-Up views for editing credentials in the Projects > Credentials > Edit Credential page have been redesigned with a dark theme to align with the overall design, enhancing visual consistency.
Platform
Filter for Environment and Store Version
Adding Environment and Store Version on Project Card
Live build information, including store and tag versions, is now displayed on project cards in the Projects page, providing quick access to essential information.
Netopia Bitcoin Payment Extension
Mokka Payment Extension
The documentation for the has been updated to provide users with comprehensive information and guidelines.
Platform
A new filter has been added on the Projects > Builds page, allowing users to filter by ENV and Store versions by typing them exactly in the input field.
The development of the Netopia Bitcoin Payment Extension has been completed. This integration is available for any brand and can be used with Netopia in currencies and countries provided by the 3rd Party. After deploying the Netopia Bitcoin extension, users should configure the Sales Channels > Payment Management > Pos Integration and Sales Channels > Payment Management > Payment Option pages according to the Installation document. Reference: ()
The development of the Mokka Payment Extension has been completed. This integration is available for any brand and can be used with Mokka in currencies and countries provided by the 3rd Party. After deploying the Mokka extension, users should configure the Sales Channels > Payment Management > Pos Integration and Sales Channels > Payment Management > Payment Option pages according to the Installation document. Reference: ()
