Skip to main content

Salesforce Meetup#3 in Belarus: Keynotes

About Us
Published by admin
25 July 2018
64

We have great news - JET BI has become an official partner of Event Space! This means that all the Meetups of the Salesforce Professionals Belarus community are going to be organized with engagement and initiative of JET BI team.

Now get to the point. On July 18, the third Salesforce Meetup took place in Minsk. The event was gathered more than 150 like-minded people who have discussed the latest news and features from the Salesforce world, as well as share their experience with newcomers.

Sergey Kochanovsky delivered a report about "External JS Libraries and Lightning". He pointed out possibilities of using external JS libraries while developing the Lightning Component, turned attention to the pros and cons of this approach, as well as told about nuances that require attention at the very beginning of development. Moreover, Sergey demonstrated examples of the real usage of JS libraries for drawing charts and maps in Lightning Components.

Andrey Dedovets forcefully demonstrated and proved that Salesforce DX CLI, nowadays, is an indispensable tool for solving everyday tasks and allows developers to save the most valuable IT resource - time.

If you missed the event but want to know more about introduced presentations -  go to this link and find the video record of the Salesforce Meetup # 3 in Belarus.

Many thanks to everyone who was with JET BI during Salesforce Meetup # 3! Follow us on the social media and do not miss the next meeting of Salesforce Professionals Belarus. Dreamforce 2018 Keynotes will be on the agenda next time! The JET BI team are going to present and discuss the most exciting news that will be brought right from San Francisco.

See you on October 4!


image
Question to the expert
image

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

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
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.
28 August 2026
image
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.
23 July 2026
image
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.
08 July 2026