"Everything must be made as simple as possible. But not simpler"
- Albert Einstein
We do not produce lines of code just for the sake of proving that we can code and justify numbers on our invoices. Every team member's main objective is to build practical, maintainable and scalable solutions. The architecture we apply makes it possible for anyone else to easily read, understand and modify the code we wrote. We do not just offer you coding hours — we look for solutions to business challenges.
But it is not just about the code but our people behind the development console. Countries like Poland, Czech Republic or Slovakia are constantly occupying the highest spots in various rankings of the best software developers. We are based in the EU and culturally closer to Western Europe, Scandinavia and the United States hence the clear communication and high knowledge of English language are the standards.
Back-end is the backbone of your business logic and we know how to write quality code on multiple Salesforce clouds.
Apex enables execution of flows and transaction control statements. Using syntax that looks like Java and acts like database stored procedures, Apex enables developers to add business logic to most system events, including button clicks, related record updates, and Visualforce pages. Apex code can be initiated by Web service requests and from triggers on objects.
Apex can be stored on the platform in two different forms:
A class is a kind of a sample from which Apex objects are created. Classes consist of other classes, user-defined methods, variables, exception types, and static initialization code.
A trigger is Apex code that executes before or after specific data manipulation language (DML) events occur, such as before object records are inserted into the database, or after records have been deleted. Triggers are stored as metadata in Salesforce. A list of all triggers in your organization is located on the Apex Triggers page in Setup. See Manage Apex Triggers.
Front-end is responsible for how your application looks like so all buttons, windows, fonts and anything else you see on the screen.
Still using Salesforce Classic? Don’t worry, we will not leave you behind. We have expertise in Visualforce markup and we can support you with on-going org development.
Integrations (REST, SOAP, BULK, METADATA)
We live in times when every customer is connected. Integrations are what are powering these custom-connected experiences. Using them you can bring together disparate systems — data that lives in external ERP, Supply Chain, HR, or on-premises software like SAP, Oracle, and Microsoft — to build a unified 360-degree overview of your customer.
APEX REST API
An excellent choice for use with mobile applications and web projects
REST API provides a powerful, convenient, and simple REST-based web services interface for interacting with Salesforce
Uses REST, HTTP, JSON
APEX SOAP API
Can be used to integrate Salesforce with your org’s ERP and finance systems
You can use SOAP API to create, retrieve, update, or delete records.
Handles medium data volumes
Uses WSDL, SOAP, and XML
The Bulk API is a RESTful API that is optimal for loading or deleting large sets of data. You can use it to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches that Salesforce processes in the background.
Bulk API is designed to make it simple to process data from a few thousand to millions of records.
Allows access to the organization’s data model, business logic, and user interface
SOAP, WSDL, and XML
The most common use is to migrate changes between .org (for example between sandbox and your production environment)
Relevant case study
German luxury furniture retailer improves order management and purchasing process with Salesforce
Organization-wide data access from one place provided by connecting Sales Cloud, Service Cloud and E-shop solutions on one Salesforce. com platform.