Home Salesforce Meetup#4 in Belarus: Keynotes

Salesforce Meetup#4 in Belarus: Keynotes

About Us

Published by admin

08 October 2018

52

On October 4, the fourth meetup of the Salesforce Professionals Belarus community took place in Event Space.

Salesforce meetup gathered experts to discuss the latest news from the world of Salesforce.

Alexey Ezhkov, Salesforce developer at iTech Art, delivered a report about “Best Practices for Developing Lightning Components”. As a part of his report, Alexey told and showed on real cases how the Lightning Data Service, Storable Actions and Custom Cache work.

Eugene Rusalev, technical architect at JET BI, prepared a report “Dreamforce 2018. Overview" about the largest IT-conference in the world and the latest updates from Salesforce. In his report, he spoke about Mule Soft Anypoint Platform, partnership between Apple and Salesforce, latests platform updates and new product releases.

We learned from Eugene that during Dreamforce 2018 Einstein Voice and Salesforce Customer 360 were announced.

Einstein Voice is Salesforce CRM voice assistant. Now it will be possible to make appointments, check the schedule and set tasks in CRM system using only one voice.

Salesforce Customer 360 is a system to connect Salesforce apps and deliver unified cross-channel customer experiences.

Thanks to everyone who was with JET BI at Salesforce Meetup # 4! Follow us on social networks and do not miss the next meeting of Salesforce Professionals Belarus.

Get the latest Salesforce news from JET BI team!

Gallery

Salesforce Meetup#4

Salesforce Meetup#4

Salesforce Meetup#4

Salesforce Meetup#4

Salesforce Meetup#4

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.