Andrii Muzychuk

A software company with several Salesforce components that are manually created and configured in their client's organizations. I made unmanaged and managed packages that were installed with minimal configurations from the client's side.

I created a series of Visualforce pages to ease project and invoice setup and management. Initially the process was processed manually by setting up everything manually by a user (like create a bunch of records for each week to bill a customer). Now you can customize it—by settings dates, by the number of invoices for a project, and some other details. It has a manager setup project and invoices, and accountant set billed hours/sums (after this an invoice is sent to an external billing application).

It has various capabilities for fields modifications, record types, workflow/validation rules, layout changes, installation/removing applications, and adding/modifying/removing users.

I built a series of custom Apex REST API web services to manage data from desktop WPF and mobile iOS applications.

I built a WinForms application to manage test cases. I created the test cases, ran them, and saved the test results. Data was stored in an MS SQL database and shown in a tree view on the application.

This is a case management system with specific company rules. It has Visualforce pages with minimal JavaScript and CSS. The back-end logic is in the controller/extension, it has PDF generation, and saves as an attachment (implemented via a Visualforce page rendered as a PDF) plus external web services.

This is an opportunity management system with specific company rules. It has Visualforce pages with minimal JavaScript and CSS, back-end logic in the controller/extension, and external web services. I recently did an organization restructuring. That included modifying fields and their values with new organization structure model, code (including external web services), workflow rules modifications, and documenting all the changes.

I created a project management system that was initially written in PHP. I then added Flex forms to it instead of HTML forms. The challenge was to replicate PHP-generated HTML/CSS/JS with Flex and connect it with the PHP back end.

A company decided to use Salesforce for managing communications with customers. I was hired to integrate Salesforce into the company's software for managing communications with customers; an integration was needed with company's software. I tackled this problem by beginning to investigate how an integration could be made between the two systems for the specific Salesforce functionality. I also provided documentation of how to make the needed features work.

I automated deposit invoice generation based on sales orders. I created new Aura dialogs to streamline the user interface, built a Visualforce page to render invoices as PDFs, and added fields to capture extra details. I also set up triggers to recalculate values dynamically using the new fields.

An external service returns a complex payload. The payload is parsed with Apex code. Bi-directional integration.
Scheduled class makes a callout to retrieve records. They are parsed and inserted as Salesforce objects. To push changes to external service a complex system was implemented. Once a record is changed in Salesforce and the changed field is in a list of fields to be pushed to the service, a post request object is created with all the information for the POST request from the modified record. The creation is done via Flow. Once the flow is finished a queueable class is executed to process all unprocessed post requests. Queueable composes and executes a POST request. The queueable then saves the result in the post-request object. If the POST request returns an error, the request will be executed a few more times till it finally stops re-trying.
A report with failed requests is sent daily. An admin checks the errors, addresses them, and then executes re-try on all failed records using the list view button (which executes the same queueable that processes all unprocessed post-request records).
Logging is implemented on all stages, and once an error occurs, an email with a number of details is sent to all admins.