Home Registration Closed! - Salesforce Developers Group Meetup

Registration Closed! - Salesforce Developers Group Meetup

About Us

Published by admin

09 November 2018

34

On 5 December takes place the meetup of Belarusian Salesforce Developers Group. Experienced Developers and Salesforce Admins share their knowledge and exchange opinions on the latest technologies and approaches to application development. JET BI supported by the Belarusian High-Tech Park organizes this event to gather both skilled developers and solution architects as well as beginners who only start their way in the world of Salesforce, CRM system #1.

JET BI Solution Architect, Eugeny Rusalev, will make a report on the following topic 'Salesforce DX: Build Apps Faster'. The next topic to be delivered will be presented by JET BI Co-founder, Andrey Bosak. He will share the latest news from San Francisco, where the biggest IT-conference, Dreamforce, took place in the early November.

A big amount of new information, an overview of cutting-edge Salesforce technologies, as well as the exciting quiz and networking with speakers and guest are planned for the meetup.

Participation is absolutely free of charge! You only have to fill in the registration form to dive in the world of the latest technologies. The event will be held in Russian. Any questions to the speakers can be formulated in English.

Question to the expert

Salesforce Event Salesforce

We have available resources to start working on your project within 5 business days

1 UX Designer

1 Admin

2 QA engineers

1 Consultant

Related Articles

All articles

Is Salesforce Winning the Public Sector Race?

An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.

Why Your Salesforce Flows Are Agentforce's Biggest Problem

This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.

How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything

This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.