SShortSingh.
Back to feed

Salesforce Workflow Rules Migration to Flow: A Safe Checklist

0
·3 views

Salesforce is retiring Workflow Rules and Process Builder in favor of Flow, making migration necessary for orgs still relying on the older tools. The article recommends inventorying every existing rule and process, then using the Flow Migration Tool as a starting point while manually reviewing time-based and complex rules. Each rule type should map to the appropriate Flow type, such as before-save, after-save, or scheduled, and rebuilt logic should be checked for outdated criteria. Changes should be built and tested in a sandbox, with old rules deactivated only after new Flows are verified, ideally running in parallel for a period. Finally, obsolete or duplicate rules should be removed and the changes documented.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Kill switches let engineers disable features in seconds without a deploy

A kill switch is a long-lived feature flag that turns off a feature or dependency at runtime, letting engineers stop damage during an incident without waiting for a rollback, which can take 10 to 30 minutes. It is well suited to shedding slow third-party services, expensive work, risky new code paths, flood-prone background jobs, and non-essential UI. Effective switches default to the feature running, use a boring fallback path, evaluate locally so they keep working during network trouble, and sit close to the costly operation. Teams should pick one switch per dependency or feature rather than one coarse maintenance switch, and test both the on and off paths regularly.

0
ProgrammingDEV Community ·

Test shows which automated visitors reach analytics and which stay invisible

A developer tested how common automated clients appear in web analytics by sending ten types of bot to a one-page test site on November 20, 2026. Each client visited three times, and the results were compared between server logs and a JavaScript analytics beacon. Clients that only downloaded HTML, including replayed AI crawler user agents and plain curl, generated server log entries but never triggered the beacon because no script ran. Browser-driven clients such as headless Chrome and Playwright did run the script and sent beacons, and headless mode was identifiable through its user agent string. The author notes that some crawlers do render JavaScript, so bots do not always stay hidden from analytics.

0
ProgrammingDEV Community ·

How Wi-Fi Calling works without cellular signal: the phone, ePDG and IMS call path

A farmhouse with home broadband but no cellular signal can still complete a Wi-Fi call, which relies on the operator's core network rather than on radio coverage. The phone connects to the core over Wi-Fi, using the 3GPP architecture for non-3GPP access, with credentials held on the SIM and authenticated through EAP-AKA. The operator's AAA server checks the subscription to confirm authorization, and the phone then sets up an IPsec tunnel to an ePDG, which links to the PDN gateway and IMS services. The phone selects its ePDG by determining its country and building a DNS name from its home network's PLMN ID, following the 3GPP numbering pattern. The GSMA IR.51 profile governs voice, video and SMS over untrusted Wi-Fi access.

0
ProgrammingDEV Community ·

Backup automático do n8n com cron, cópia criptografada e restauração testada

Um guia explica como transformar o backup manual do n8n em uma rotina diária automatizada. O script faz o dump do PostgreSQL, guarda a pasta .n8n e o arquivo .env com a chave de criptografia, e envia tudo cifrado para um bucket S3 fora da VPS, removendo cópias antigas. O procedimento parte de uma instalação do n8n com Docker Compose e exige um bucket compatível com S3 separado da máquina. A configuração usa o rclone, instalado pelo pacote oficial, com credenciais protegidas e uma camada de criptografia sobre o bucket. Ao final, o leitor deve restaurar o backup em um projeto separado para confirmar que workflows e credenciais continuam acessíveis.