Cloud CRM & Platform — New Capabilities
1. Cloud CRM on existing instances
Cloud CRM is enabled as an additional service for existing companies. The legacy CRM remains active, allowing teams to gradually switch to the new interface without interrupting operations.
Benefits
Smooth transition with no operational risk.
Ability to test Cloud CRM on live data.
Parallel support of the old and new CRM.
2. Web card “Reclamation”
A full Reclamation card is now available in the web version of CRM, with logic, validations and business rules aligned with the mobile app. Users can create, view and edit reclamations directly from the web.
Benefits
Single reclamation process across web and mobile.
Accurate reporting and compliance with regulatory requirements.
Automatic data sync between web and mobile.
3. Web card “Vigilance”
The Vigilance (pharmacovigilance) card is added to the web CRM. The structure, logic and business rules fully match the mobile implementation.
Benefits
Full pharmacovigilance process on both web and mobile.
Unified drug safety control across the ecosystem.
Fewer manual workarounds for quality and safety teams.
4. Web “Finance” section (travel/expense reports)
The Finance (“Accounting”) section is implemented in the web CRM. Users can create, edit and review travel and financial reports with all card and field business settings preserved.
Benefits
Same financial data logic in both web and mobile.
Convenient reporting from laptop/desktop.
Data is synchronized between web and mobile.
5. Custom fields for new object types
Custom field support is extended for these objects:
Calls (visits / calls)
Tasks
Gas Report
Accounting
Reclamation
Tickets
Expenses
Expense details
Administrators can manage these custom fields in Platform Admin.
Benefits
Flexible adaptation to specific business processes without development.
Unified custom field model for key CRM objects.
Users can see and fill these fields in web, and access them from mobile via web cards.
6. Universal deep-link endpoint for cards
A new endpoint accepts card parameters (type, mode, ID) and opens the corresponding card in view or edit mode (visits, tasks, expenses, gas reports, tickets, reclamations, etc.).
Benefits
Direct links from emails, dashboards and third-party systems.
Easy navigation setup between modules and integrations.
Fewer clicks and faster access to the right data.
7. Order Management: orders in HCO card
The HCO (institution) card now has an Orders tab:
full order history sorted from newest to oldest;
order header: visit date/time, status, amount, items count, order number, last update time;
filters by status and period (month, quarter, year);
line-level details: product, quantity, price with discount, amount, status, supplier.
Benefits
Complete order history directly in the HCO card.
Fast status control for field teams.
Consolidated view of distribution, orders and reporting.
8. KPI report on tablet HomePage
A new table info_usersaleinfo is synchronized to tablets and used to build a custom KPI report on the HomePage. Data is filled via external import.
Benefits
Key KPIs available right on the start screen.
Flexible configuration through import without code changes.
Unified metric view for the whole team.
9. Improved data export in the new AdminTool
In the new AdminTool:
the 500-row export limit is removed;
export respects all filters applied to the table.
Benefits
Bulk updates (e.g. client–segment links) without data loss.
Less manual work and fewer errors.
Easier administration of large data volumes.
10. Unique links and tokens in OCM/SCE
OCM can optionally add a unique token parameter to client links.
For SCE campaigns, service tables now store identifiers that link messages and replies to a specific campaign and contact.
Benefits
Tracking on external sites at individual contact level.
Unified analytics logic for standard and SCE campaigns.
More accurate click and engagement reports.
11. Stable custom reports in Consent Manager
Custom report logic is now preserved during updates.
A public function is added to build reports based on the existing agreements function.
When saving a consent image, the file name is generated in a proper format (e.g. consent-<id>.jpg).
Benefits
Custom reporting logic isn’t broken by updates.
Transparent, controllable reporting mechanism for consents.
Convenient file download without manual renaming.
12. Optimized access-token validation in Cloud CRM
Access-token validation is now performed directly on the Cloud CRM backend without extra external calls.
Benefits
Faster API responses.
Lower UI latency.
Controlled token lifetime via configuration.
Bug Fixes (Cloud CRM, OCM, AdminTool)
Visits, schedule, agreements
Visits copied from previous months now pull brands and presentations according to the current plan.
Editing own visits works without access errors.
Only a single gas report card is created per report.
Subordinate visits and planner visits open without “access denied” errors.
Schedule no longer appears empty due to loading errors.
New visits are created automatically based on “Next visit date”.
Agreement data is saved correctly.
Client, HCO, contact, ticket cards
HCO cards open correctly, including the “Additional responsibility” tab.
Stable URL navigation for tickets, All tasks and creating HCO/client/contact from visit.
Direct links no longer open the HCO creation form if the user has no permission; an access message is shown instead.
Order history / Order details / Additional responsibility tabs work without errors.
The “HCO ID” column is displayed in the clients list.
Client and HCO are prefilled when creating a visit from a client card, even if “last visit date” is shown.
Surveys, custom fields, visibility rules
Visits and tasks with the “Survey” field no longer block saving; survey and card are saved correctly.
Additional fields (single/multi-select, text) store their values without errors.
Field order in cards matches AdminTool configuration in both view and edit modes.
Visibility rules work as expected: hidden fields appear when conditions are met; empty groups are not shown in preview.
PDK table is visible when creating a visit even if HCO was not selected beforehand.
Agreement cards now show the client’s full name.
Photos and photo layouts
Photos added to a visit are saved with tags; the field status changes to “Filled”, and previous photos are visible when reopened.
Photo–tag links in photo layouts are restored; users see proper tag info instead of only filenames.
Photo-related buttons on Android tablets are fully visible and no longer cropped.
OCM, SCE, WhatsApp, Telegram
Child campaigns in OCM are displayed under parent campaigns with full attributes (name, date, content preview, audience).
For SCE campaigns, identifiers are stored to link messages and replies to campaign and contact.
Errors when saving content with the extra Brand field are fixed.
Personalization in WhatsApp buttons works correctly; links do not contain raw placeholder text.
Telegram welcome messages show the doctor’s full name instead of placeholder text.
Reports, dashboards, filters
Double-visit report shows table data even when only date filters are applied.
Percentage icons are displayed correctly in tables.
Filter button works after reopening the report.
System multislect filters now use correct dictionaries (users instead of clients).
Access, authorization, blocking
Users are no longer logged out or “blocked” due to single API errors.
The Active account toggle correctly changes user status to inactive.
SSO login works reliably; the “No internet connection” error is no longer shown incorrectly.
GeoForce 2.0 — New Capabilities
1. Map version management interface
New tools for managing map coloring versions:
create new versions;
set active period (“from date” / “to date”);
mark versions as default, archived, API or CRM.
Benefits
Full control over which map versions are used in dashboards and analytics.
Support for multiple visualization scenarios.
Campaign planning with clear date ranges.
2. FTE Calculator
An FTE calculator helps estimate required headcount to cover the target audience. Users can:
select a period with working/non-working days;
set number of visits by type (HCP, HCO, pharmacy);
select region, city or isochrone;
choose specialties, organization types, coverage share and visit frequency;
see calculated covered organizations, specialists and FTE.
Benefits
Data-driven team and coverage planning.
Fast “what-if” scenarios for different regions.
Transparent arguments for budgeting and headcount decisions.
3. Geodata upload via datasets
Users with dataset permissions can upload custom geographic objects (bricks) in WKT format. Perimeter and area are calculated automatically on the DB level.
Benefits
Support for customer-specific geo models.
No complex manual imports.
Geodata is immediately ready for analysis and visualization.
4. Datasets ETMS → GeoForce 2.0
Implemented dataset loading from ETMS into GeoForce 2.0 without extra integration work.
Benefits
Single source of truth for data across modules.
Faster GeoForce 2.0 rollout.
Fewer manual setup steps.
5. GeoForce 2.0 permissions in AdminTool
AdminTool now includes a dedicated permission block for GeoForce 2.0, including dashboard access.
Benefits
Fine-grained control over what different roles can see.
Ability to restrict dashboard access for specific groups.
Centralized permission management.
6. Navigation between “unpainted” bricks
When “Highlight unpainted” is enabled, a switcher appears:
next/previous arrows to move between unpainted bricks;
counter of remaining unpainted objects;
automatic centering on the selected brick with optimal zoom.
Benefits
Fast detection of uncovered areas.
Less manual scanning of the map.
Comfortable work with large geodata sets.
7. UX improvements in Manage Map Version
After any change to map version settings, the Save button becomes active.
It is no longer possible to open multiple “new version” dialogs before saving the current one.
Benefits
Fewer chances to lose changes.
No duplicates when creating versions.
Predictable UI behavior.
Bug Fixes
Role and permission settings for GeoForce 2.0 now load correctly; map and menus open without errors.
GeoForce 2.0 API no longer returns internal errors; users see the auth form and valid responses.
In drawing mode, already painted bricks correctly change color when a new color is selected.
The Map button is hidden if the role has no dashboard access.
Map and dashboard labels are translated according to the UI language.