




Dimasi Software is an Italian ERP and asset-management suite provider (“Logica e Sistemi”) offering customisable modules for facility management, maintenance, assets and field operations.
Have any questions? We’re here to help You
Yes, Makini supports both cloud-based and on-premises systems. For on-premises installations, connections require double the connection credits compared to cloud systems. The connection process typically requires opening specific ports and whitelisting Makini's IP addresses in your firewall configuration. For some on-premises systems, VPN tunnels may be necessary. We provide detailed technical requirements during implementation planning. In cases where security policies prohibit external connections, we offer self-hosted deployment options where Makini runs entirely within your infrastructure, eliminating the need for external network access to on-premises systems.
Makini provides webhook testing tools in the dashboard where you can trigger test webhook deliveries to verify your endpoint configuration. Test webhooks use sample payloads matching actual event structures. Verify your endpoint receives the webhook, validates the signature correctly, and responds with a 200 status code within 10 seconds. Test webhook retries by having your endpoint return error codes or timeout, then verify Makini retries as expected. Test duplicate handling by processing the same webhook multiple times. For local development, use tools like ngrok to expose your local endpoint for webhook testing. The webhook logs in the Makini dashboard show delivery attempts, response codes, and timing, helping debug delivery issues.
Yes, Makini supports write operations including creating, updating, and in some cases deleting records in connected systems. Common write operations include creating purchase orders, updating work order status, modifying inventory levels, and creating vendor records. Write support varies by system and entity type—core entities like purchase orders have comprehensive write support across major systems, while more specialized entities may have limited write support in some systems. Write operations use the same unified API, so the code to create a purchase order in SAP is identical to creating one in NetSuite. Validate write requirements during implementation to ensure your target systems support needed operations.
When a system becomes unavailable, Makini detects the connectivity failure and marks the connection status accordingly. Scheduled syncs will fail with connectivity errors. API requests to the connection will return error responses indicating the system is unreachable. Makini continues attempting scheduled syncs using exponential backoff—initial retries happen frequently, then progressively less often to avoid overwhelming the system when it comes back online. Webhooks notify you of the connection status change. When the system comes back online, normal operations resume automatically. For temporary outages, no action is required. For extended outages, you may want to notify the customer. Connection credits remain consumed during outages since the connection configuration persists.
