Administrators and operations teams
Understand the common operating patterns used across Finger Manager, including navigation, search, filtering, creation, editing, saving, publishing, status changes, and permissions.
Understand the common operating patterns used across Finger Manager, including navigation, search, filtering, creation, editing, saving, publishing, status changes, and permissions.
يمكن تسليم الإشعارات التي يتم إعدادها في Finger Manager داخل Finger Trader App وفق القواعد والجمهور والجدولة.
This section explains common operating methods used in Finger Manager, including page navigation, search, filtering, creation, editing, saving, publishing, preview, status management, and permission control.
Although different modules correspond to different business functions, the overall interaction model remains consistent. After becoming familiar with these basic operations, users can work more efficiently across product management, customer management, trading management, content and notification, and system settings.
Finger Manager groups major functions by business module in the left navigation. Users can enter product overview, dashboard, market and product management, customer management, trading management, content and notification, organization and permissions, system settings, logs, troubleshooting, reports, and analytics.
Some main menus include multiple subfunctions. Users can expand or collapse a main menu to access second-level pages. The modules each user can finally access are determined by the current account's roles and permissions.
When a page contains many records, search can be used to quickly locate target data.
Search conditions vary by module and may include product name, Ticker, user name, User ID, customer number, order number, notification title, email, phone number, organization name, or other business fields.
After entering a keyword, the system displays matching results.
For pages with large record sets, filters can narrow the data range. Common filters include status, type, market, product, user, time range, organization, Desk, notification type, and publishing status.
For example, in the notification center, selecting Type: Push Notification and Status: Published will display only the notifications that match those conditions.
Filter conditions can be combined according to the business module.
When a page supports creating new data, it usually displays a New or + Create button.
Typical creation workflows include creating products, customers, notifications, user groups, roles, markets, and scheduled tasks.
After required fields are completed, the user can save the record or proceed to the next configuration step.
Existing records can usually be opened from a list or detail page and modified by authorized users.
Editable content may include names, status, parameters, display content, audience range, time settings, permissions, sorting, jump URLs, or other business configuration.
After changes are made, the user needs to click Save or Confirm for the new settings to take effect. Important operations may require additional confirmation.
Save and Publish are different concepts in Finger Manager.
Save usually means storing the current configuration, but it may not immediately take effect for end users. It is suitable for unfinished content, drafts, configurations that still need review, or pre-release preparation.
Publish means applying a completed configuration to the system or client, such as publishing announcements, popups, banners, marquees, or sending notifications.
Some modules therefore support saving first and publishing only after content is confirmed.
For functions that affect Finger Trader App display, Finger Manager can provide preview capability.
Preview is commonly used for Banner, popups, login popups, marquees, in-app notifications, and announcements.
Before publishing, users can confirm copy, images, display position, page effect, CTA, and jump logic.
Most business records in Finger Manager have status values. Status names vary by function.
Notifications may include Draft, Scheduled, Published, Expired, and Cancelled. Products may include Active, Inactive, Listed, and Delisted. Users may include Active, Disabled, and Pending.
Status helps users quickly determine whether a record is currently effective.
Some configurations can be enabled or disabled directly through a switch.
Examples include product listing status, user account status, notification status, system functions, API services, user roles, and certain client-side features.
After disabling, the configuration stops taking effect, but the original record is usually retained so it can be re-enabled later.
Authorized users can delete records that are no longer needed. Because deletion may affect system data or business configuration, important records may require second confirmation.
Before deleting, confirm whether the record is still in use, whether it has related data, whether disabling can replace deletion, and whether historical records must be retained.
For data that requires long-term auditability, the system may only allow disabling rather than permanent deletion.
Some pages support batch operations when multiple objects need to be processed.
Examples include selecting users in batches, adjusting product status in batches, sending notifications in batches, adding users to groups in batches, and exporting data in batches.
Actual batch capabilities depend on the specific business module.
Content that affects Finger Trader App display order can be sorted in Finger Manager.
Examples include product sorting, Banner sorting, market sorting, and homepage module sorting.
After the backend order is saved, Finger Trader App can display content according to the new order.
Some functions support start time, end time, publishing time, scheduled sending time, or validity period.
For example, an activity Banner can be configured to start at 09:00 and end at 18:00. The system will automatically control the content status within the specified time range.
For operations that may affect many users or important system settings, the system may require the user to confirm again.
Examples include publishing notifications, sending messages in batches, deleting data, changing permissions, listing or delisting products, and changing important system settings.
Before final confirmation, check the operation target, target users, current status, publishing time, and impact scope.
After an operation is completed, the system usually displays the result, such as saved successfully, published successfully, sent successfully, configuration updated, operation failed, or insufficient permission.
If an operation fails, users can check the system prompt, review configuration fields, or open logs and troubleshooting pages for more details.
All back-office operations in Finger Manager are controlled by roles and permissions. Different users may see different buttons and have different available actions.
For example, a user may be allowed to view products but not edit products. In that case, the user can still view related information but cannot modify it.
If a function is not visible or cannot be operated, first confirm whether the current account has the corresponding permission.
Finger Manager can record logs for important back-office operations.
Logs can show the operating user, operation time, module, target object, content, and result.
When configuration abnormalities, data changes, or other issues occur, operation logs can assist with troubleshooting.
A common operating flow is: enter Finger Manager, choose a business module, search or filter target data, open detail, create or edit configuration, confirm parameters, save, preview if applicable, publish or enable, let the system execute the operation, and then check the final result in Finger Trader App or the back-office page.
Different Finger Manager modules use a consistent back-office interaction model.
After users understand search, filtering, creation, editing, saving, publishing, status management, and permission control, they can quickly understand most functional modules.
For the specific fields, steps, and effects of each business function, refer to the detailed chapter for that module.
In short, basic operations provide the common interaction foundation for using Finger Manager. Business-specific details are explained in the corresponding chapters.
