Develon using Next2U based on Salesforce Plus Lightning to register maintenance by dealers. The process starts automatically when a task in Frontu reaches the "Approved" status.
Machine Identification & Limitations
To ensure data is recorded against the correct machine, the integration uses the VIN number stored in the Serial Number field in Frontu. This is matched with the manufacturer's serial number in the Develon system.
Important Limitation: Develon only began using this specific tracking parameter for machines registered from January 1, 2023.
Newer Machines (2023+): Synchronization works automatically.
Older Machines (Pre-2023): Synchronization is not possible because the identifier does not exist in Develon. Data for these machines must be uploaded manually by Intrac representatives.
Data Collected and Sent
When a sync occurs, the system sends standard details such as the Visit Date, Serial Number, Operation Hours and other. List of all data shared with Develon is visible below:
Reference ID
Operation Hours_c
Record Type ID
Serial No
Manufacturer Serial Number
Visit Date
Operation Hours Interval
Customer Opinion
Service Interval Logic
How the service interval is reported depends on the type of task performed:
1. Standard Maintenance.
For standard technical inspections, the system uses the "Warranty Indicator" field.
Note on Mapping: Frontu uses a custom mapping system. For example, if a machine has 1000, 3000, or 5000 hours in Frontu, the integration automatically converts this to the standard "1,000 Hours / 6 Months" service interval required by Develon.
2. Stock Maintenance. Type: Develon mėnesinė patikra.
For monthly checks, the value is taken from the custom field "Develon Stock Intervalai".
Selections: This field allows specific selections required for web users (not visible in the app): 30 Days, 90 Days, 180 Days, 270 Days, or 1 Year.
File Transfer
Once the data is successfully sent (without errors), the system automatically uploads the "Act of Acceptance" file from Frontu to Develon.
Error Handling and Troubleshooting
If an error occurs during synchronization:
Notification: The system applies a tag "Not synced_Develon" to the task in Frontu.
Alert: An email is automatically sent to the administrator with details of the error.
How to Manually Retry
If a synchronization was unsuccessful and the "Not synced_Develon" tag appears, a user can attempt to re-send the data manually:
Open the detailed view of the Work Order.
Click the button "Send data to external system".
Select the option "Work order approved".
Frequently Asked Questions (FAQ)
Q: Why didn't the data sync for a specific machine even though the task is approved?
A: Check the machine's registration date. Develon only supports automatic synchronization for machines registered on or after January 1, 2023. If the machine is older, you must upload the data manually.
Q: I see the tag "Not synced_Develon" on a task. What should I do?
A: You can manually trigger the sync. Open the work order, click "Send data to external system", and select "Work order approved".
Q: Which task status triggers the data transfer?
A: The integration is triggered only when the task status is changed to "Approved".
Q: Why are the operation hours in Develon different from what I see in Frontu?
A: This is expected behavior. Frontu uses custom mapping to match Develon's standards. For example, Frontu hours like 1000, 3000, or 5000 will all map to the standard "1,000 Hours / 6 Months" interval in Develon.
Q: Where does the system find the interval for Monthly Check?
A: For monthly checks, the system looks at the "Develon Stock Intervalai" custom field (e.g., 30 Days, 90 Days). Note that these options are visible to web users but not in the mobile app.
Q: Is the "Act of Acceptance" file sent if the data sync fails?
A: No. The file is only uploaded to Develon if the initial data transmission is successful and error-free.