#how to design for flow in sfdc

[sfdcpanther]

How to develop Lightning DataTable for Salesforce flows

How to develop Lightning DataTable for Salesforce flows

Hello #Trailblazers, Welcome back to SFDCPanther and wish you a very happy new year 2022. In this blog post, we will learn how to develop a lightning datatable for Salesforce Lightning Flow Builder. We know that we can not directly develop the Lightning DataTable for Salesforce flow. So I have developed a lightning web component that can be used inside a flow and will work dynamically for any…

[yadavti]

Getting started with Salesforce Visualforce Workflow

How a flow is created? Flows can be created from Setup, enter Flows in the Quick Find box, then select Flows, and then click New Flow.

There are 3 main “building blocks” of the flow:

Elements represent actions that are executed in the flow

Connectors define which path the flow takes

Resources are the values that can be referenced anywhere in the flow

Visualforce flow

It allows to automate business process by building application, knows as flows that collect, edit, update and create salesforce information.

Flow can execute logic, interact with salesforce database.

Flow designer tool is used for creating flows, configure screen, and define branching logic without writing any code.

What is visualforce flow? When I first heard about Salesforce Flow also called Visual Flows, Visual Workflows. Want to streamline your opportunity creation process without the need to code? The use cases for Flows are endless. Flow is a powerful business automation tool that can manipulate data in Salesforce in a variety of ways. The ease of creating flows makes it the number one go-to tool when it comes to complex business requirements.  The Salesforce platform’s object relationships and overall how Salesforce runs. You have got to have at least mid-level of understanding of SFDC and its features in order properly use flows.

Difference between Salesforce dot com Flow and Workflow

Salesforce Flow or Visual Workflow is often confused with a feature named Workflow in Salesforce. They may be similar in certain fashion such as assisting in automating a business process, but in essence they both are different.

Salesforce dot com Flow

Visual Workflow is more of a front-end based tool. It is mainly used when you have to display or collect information through screens making it more visible to the users.

Visual Workflows are triggered by user actions. However in Visual Workflows, you can also Auto launch Flows i.e. start a Flow without user interaction. Since they are triggered without user interactions you cannot include steps, choices, screens or dynamic choices in your Auto launch Flow.

Workflow

Workflow on the other hand execute per-defined rules behind the scenes. They are used to process information rather than collecting it.  While Workflows are mainly triggered by events

Workflows can fetch, delete, update or even create records on multiple objects but Workflows are defined to affect only a single specified object. The exception to this is the case of Workflows having to update fields on specified object’s related master records.

[tinygardenphilosopher]

Getting started with Salesforce Visualforce Workflow

How a flow is created? Flows can be created from Setup, enter Flows in the Quick Find box, then select Flows, and then click New Flow.

There are 3 main “building blocks” of the flow:

Elements represent actions that are executed in the flow

Connectors define which path the flow takes

Resources are the values that can be referenced anywhere in the flow

Visualforce flow

It allows to  automate business process by building application, knows as flows that  collect, edit, update and create salesforce information.

Flow can execute logic, interact with salesforce database.

Flow designer tool is used for creating flows, configure screen, and define branching logic without writing any code.

What is visualforce flow? When I first heard about Salesforce Flow also called Visual Flows,  Visual Workflows. Want to streamline your opportunity creation process  without the need to code? The use cases for Flows are endless. Flow is a   powerful business automation tool that can manipulate data in   Salesforce in a variety of ways. The ease of creating flows makes it the  number one go-to tool when it comes to complex business requirements.  The Salesforce platform’s object relationships and overall how   Salesforce runs. You have got to have at least mid-level of   understanding of SFDC and its features in order properly use flows.

Difference between Salesforce dot com Flow and Workflow

Salesforce  Flow or Visual Workflow is often confused with a feature named Workflow  in Salesforce. They may be similar in certain fashion such as assisting  in automating a business process, but in essence they both are  different.

Salesforce dot com Flow

Visual  Workflow is more of a front-end based tool. It is mainly used when you  have to display or collect information through screens making it more visible to the users.

Visual Workflows are triggered by user actions. However in Visual Workflows,  you can also Auto launch Flows i.e. start a Flow without user   interaction. Since they are triggered without user interactions you   cannot include steps, choices, screens or dynamic choices in your  Auto launch Flow.

Workflow

Workflow on the other hand  execute per-defined rules behind the scenes. They are used to process  information rather than collecting it.  While Workflows are mainly  triggered by events

Workflows can fetch, delete, update or even create records on  multiple objects but Workflows are defined to affect only a single  specified object. The exception to this is the case of Workflows having  to update fields on specified object’s related master records.

[hireindianpvtltd]

Fwd: Urgent requirements of below positions

New Post has been published on https://www.hireindian.in/fwd-urgent-requirements-of-below-positions-45/

Fwd: Urgent requirements of below positions

Please find the Job description below, if you are available and interested, please send us your word copy of your resume with following detail to vendor@vinsysinfo.com or please call me on 703-594-5490 to discuss more about this position.

  We are planning for a weekend drive on 2nd Feb and 3rd Feb and hence need your extended support for that. Will be expecting an active participation from each of you.

  Position

Location

Salesforce Developer

Columbus / Indianapolis, IN

SFDC Business Analyst

Peoria, IL

CPQ/Apttus Consultant

Minneapolis, MN

SFDC Developer

Austin, TX

Salesforce Sales Cloud + APTTUS CLM (Senior Developer) OR Cloud Craze

Houston, TX

SFDC Community Cloud developer

San Francisco, CA

Sr. Developer Lightning Community

Trevose, PA

    Job Description

Job Title: Salesforce Developer

Location: Columbus or Indianapolis, IN

Duration: Contract

Work Authorization: USC/GC ONLY      

Mandatory Skills: SFDC Lightning, Apex, Visual Force  Looking for Field Service Experience Field Service implementation (Siebel, ServiceMax etc..)

Desired Skills: HTML, CSS, Ajax, JavaScript, J Query

Experience: 10+ Years is mandatory

Job Description:

5+ years of SFDC (Salesforce) experience.

Must have Hands on Customization APEX, Lightning, Visual Force, Triggers, Batch, Schedule Apex, VF Components, Test Class etc. and Good experience in SFDC configuration and mapping features to the business requirements.

Good Experience in Data Migration using SFDC import and export utilities.

Experience in implementing integration solutions between CRM, ERP and Financial systems

Strong RDBMS knowledge and building SQL queries. Experience in working with HTML, CSS, Ajax, JavaScript, JQuery will be a plus.

Look for candidates with Salesforce Developer Certification.- Experience developing customer-facing user interface

Able to read, modify and debug complex code.

Job itle:  SFDC Business Analyst

Location: Peoria, IL

Duration: Contract

Mandatory Skills: Business Analyst, Salesforce.com, Sales Cloud, Apex

Job Description:       

Over 10 years of IT experience with about 5 years of experience in the Salesforce platform as a Business Analyst

Experienced working with Salesforce.com Sales cloud, Service Cloud, Communities

Experience in interacting with business stake holders and capturing business requirements

Good knowledge on Apex development in creating Objects, Triggers, Apex Classes, Standard Controllers, Custom Controllers and Controller Extensions

Experienced in building Custom Applications that includes administration configuration implementing and support experience with Salesforce.com platform

Proficiency in administrative tasks like Creating Roles Profiles Users Email Services Page Layouts Workflow Alerts Actions Reports and Approval Processes

Implemented security and sharing rules at object field and record level for different users at different levels of organization. Also created various profiles and configured the permissions based on the organizational hierarchy

Experienced working with salesforce.com sandbox and production environments also with Eclipse IDE Force.com Plug-in environments

Technology savvy with aptitude and experience in adopting modern methodologies and innovative techniques to boost work efficiency

Detail-oriented energetic team player motivated with multi-tasking capabilities problem solver and hands-on leader with exceptional presentation and client/customer relation skills

Strong communication and inter-personal skills with ability to work well in a dynamic team environment.

Certified Salesforce Developer or Administrator would be preferred.

  Position:              CPQ/Apttus Consultant

Location:             Minneapolis, MN

Contract:             Longterm

  Required Qualification

At least 1 year or 2 projects experience in Angular JS.

At least 1 year or 2 projects experience in CPQ development such as Apttus callbacks.

At least 1 year or 2 projects experience in Apttus CPQ (Configure/price and quote) with good understanding on how Apttus CPQ works. Don’t need experience in Apttus CLM or other module.

4-5 years of solid SFDC development experience. No compromise here since there should be enough people with this level experience.

SFDC Integration using SOAP/REST API’s must

Knowledge of Continuous Integration (Deployment) using SVN tools (JENKINS/GIT) must.

  Responsibilities

Manage day to day development activities on the salesforce.com platform and Apttus tool using Apex and Visual Force

Support the creation of customizations and integrations required to solution delivery

Configure the Salesforce.com application based on the business requirements

Develop custom applications using Apex, Visualforce, JavaScript, AJAX, HTML, CSS

Apply best practices and experience to build Salesforce.com applications.

Develop estimates for projects

Work closely with other developers in the team, business analyst, QA analyst and project managers.

Research Salesforce.com and Apttus CPQ capabilities as needed to suit business requirements, and provide gap analysis

        Position: SFDC Developer

Location:  Austin, TX

Duration: Contract

  Job Description:

Responsibilities:

•             Work with stakeholders and existing engineering teams to gather requirements and translate them into efficient salesforce                           solutions.

•             Develop, maintain and test new Salesforce processes using Salesforce techniques such as custom objects, APEX triggers,                                 workflow rules, validation rules and Lightning.

•             Design and implement for API endpoints for internal integrations.

•             Carry out system maintenance, configuration, development and testing.

•             Documenting designs and implementation

•             Creating training materials for users.

•             Ensuring that migration to new platform is successful. 

Minimum qualifications:

•          3+ Salesforce Development Experience including hands-on experience in Apex Code, SOQL queries, Triggers, Validation Rules, workflows, flows/process builder and migration of code,  Visualforce, backup of sandbox/ repository.

•             Experience implementing Web Service SOAP, REST API and bulk APIs

•             Flexible engineer, with strong communication and team working skills

•             Experience with complete lifecycle of software development, from design to product ionization.

•             Experience with working with distributed teams and a great team player

•             Good writtenand verbal communication skills.

•             Degree in Computer Science, Engineering or related areas.

Preferred qualifications:

•             Salesforce Certified Administrator           

•             Experience with Salesforce Security Models

•             Experience with C++ development

Position: Salesforce Sales Cloud + APTTUS CLM (Senior Developer) OR Cloud Craze

Location:  Houston, TX

Duration: Contract

Mandatory Skills: Salesforce Sales Cloud and Apttus CLM, HTML, CSS, JavaScript

Experience: 8+ Years

  Job Description:

The Salesforce Developer will perform hands-on technical implementation, with a focus on delivering functional solutions on the Salesforce.com platform.

Salesforce Developer will take a lead role in the design, implementation, deployment, and documentation of projects that leverage the Salesforce.com tool set. This is an Apttus CLM environment on Force.com (Salesforce) platform.

Required Technical and Professional Expertise

5+ years Salesforce development experience

Hands-on experience in Apttus CLM

2+ years’ experience HTML, CSS, JavaScript, Ajax, JQuery

Design, develop implement and support custom business solutions for a variety of industries

Effectively translate business requirements into systems solutions using Visual force and Apex

Drive projects from concept and design to testing, and implementation

Strong SOQL experience

SFDC architecture experience

Excellent, highly professional written and oral communication skills required

Strong analytical and problem-solving skills

Ability to work effectively both independently and as part of a team

Experience with project automation technology: Jenkins, automated unit testing, Ant etc. is preferable

Preferred Tech and Prof Experience

Bachelor's degree or Master’s Degree in Computer Science or related field is preferred

Job Title: SFDC Community Cloud developer

Location: San Francisco, CA

Duration: 6-8 months

  Mandatory skills: Experience with Community Cloud development.(MUST)

  Job description:

Proficiency in SFDC Administrative tasks like creating profiles, roles & users, manipulating page layouts and record types, setting up email services, configuring approvals, designing workflows, creating reports & dashboards, working in both the Classic UI and Lightning

Hands-on design and architect of custom solutions on the force.com platform including significant work in Apex, Visual Force, SOQL, and application integration patterns.

Solid understanding of Salesforce Connect to call external API.

Experience in developing client-specific solutions on the force.com platform using Apex, Visual force, Lightning.

Experience in SFDC development using Apex classes, batch scripts and triggers, Visual force pages and components (in both Classic UI and lightning), Force.com IDE, SOQL, SOSL, REST & Web Services APIs, Flow Designer.

Experience with Community Cloud development.(MUST)

Configure and maintain Salesforce Community portals. Understanding of community user permissions, design of components for use in Community Builder, editing community styles and templates.

Create Web Services APIs, Flow Designer.

Configure APIs and Web Services between Salesforce and other systems.

Proficiency in object oriented software design methodologies, data modeling, data extraction & transformation, data loading, scheduling, monitoring, and reporting in a multi-tenant, cloud computing environment

Job Title: Sr. Developer Lightning Community

Location: Trevose, PA

Duration: Contract

Experience: 8+ years

Work Authorization: USC/GC/H1b

Mandatory skills: Salesforce- Sales Cloud, Lightning community, Apex, Visual Force

  Job Description:

Deep understanding of Salesforce – Sales Cloud, Service Cloud, Communities / Portals and Force.com.

Salesforce Configuration and Design of Partner & Customer Communities. This would leverage the Lightning Community Builder, Lightning Components – standard and custom, and also Visualforce and other tools where needed.

Previous experience working with Salesforce Communities is a must. Experience leveraging both the Visualforce / tabs and Lightning Template approaches is must.

Operational experience in how a community is used – for Customers, is required. Candidate must have an understanding of how users leverage Communities in multiple use cases: Self Service, Public Discussion / Collaboration, and Partner.

Communities Consultant, Sales Consultant or Service Consultant certification is preferred.

Strong ability to problem solve and understand how a business process can be enhanced and improved using Salesforce, coupled with the knowledge of choosing the most effective option for a customer.

Ability to document requirements for developers a must. Must be hands on with an understanding of what can be done with Lightning/Apex/Visualforce/Web Services is a must.

Ability to work in a self-sufficient manner, but also with a team.

Translating the Customer’s requirements and using best practices, crafting a solution with Salesforce that will support their processes, with standard and custom development.

Develop technical requirements for internal developers to build solutions where needed.

Provide End User Training and Documentation during roll-out

  Thanks, Steve Hunt Talent Acquisition Team – North America Vinsys Information Technology Inc SBA 8(a) Certified, MBE/DBE/EDGE Certified Virginia Department of Minority Business Enterprise(SWAM) 703-594-5490 www.vinsysinfo.com

    To unsubscribe from future emails or to update your email preferences click here .

[cstesttaken]

THE HACKIES: A CMO's guide to integrating marketing technologies

Is your marketing team having challenges in seamlessly planning and executing campaigns with the tools they use? Does data automatically flow from one system to another, or does your team move data by manually exporting and importing spreadsheets?

In supporting your company’s business objectives, you may realize that your existing martech stack doesn’t meet your current marketing needs due to one or more systems:

Not having the required capabilities

Having some but not all required capabilities

Having the capabilities but are difficult to implement and/or manage

Not being sufficiently integrated with each other

Whether you need to modify your existing toolset, acquire new technologies or a combination of both, you need to ensure all the platforms are integrated optimally to maximize the effectiveness of your martech stack. While you don’t need to know how to design or build the integrations, you should understand some basics to ensure that you have a cohesive infrastructure rather than a house of cards or a set of application siloes.

Out-of-the-box integration: caveat emptor

Many martec vendors promote that they have built-in integrations to one or more systems. Be sure you understand the use cases that these integrations support.

Do they meet a robust set of use cases or only a few? Do these use cases align with yours, or do you have unique scenarios that may not be possible or negatively impacted with the native integration as-is? Can their built-in integration be customized to support your needs? Will it be able to move all your required data to and from the target system and perform necessary functions?

I recently reviewed the integration capabilities of an online survey platform to an MAP. While the vendor was listed as a partner on the MAP vendor’s web site and claimed having native integration support, I quickly realized that the integration was limited to simply passing a link to a survey for a specific set of recipients so that an email with that link can be sent to them. The integration didn’t support the ability to pass the response data from a completed survey to the MAP, which could provide much more value to marketing.

Another important factor to consider is the extent to which your system has been customized. We have consulted with clients that use Salesforce.com (SFDC) for their CRM, and we were tasked with integrating their newly-purchased marketing automation platform (MAP) with it.

Some clients had lead and opportunity management processes that required them to customize the data models and functionality in their CRMs. This created difficulty in using the MAP’s native SFDC integration as-is.

For some clients, the native integration was customized (e.g., via Marketo sync filter or Eloqua program) to meet their requirements. Others made changes to their processes to align with the use cases supported by the native integration. There also were clients where the native integration simply wouldn’t work due to its adaptability or their limitations in business process changes, and they had to use an integration platform.

Important integration terminology and concepts

Before getting into more integration specifics, let’s cover some terminology and concepts at a high level. There are plenty of articles and discussions on the Internet on these, so if you want more details, just google for them.

Manual versus automated integration

Your team may already be performing manual integration by exporting a list of attendees from your event management platform and uploading them into your MAP. They may be doing the same task between the MAP and CRM.

Automated integration replaces the human factor, enabling the ability to schedule data syncs. Automated integrations can also store field mappings, transform data and allow the transfer of data at scale, eliminating the risk of human error.

Flat-file and web services integration

Flat-file integration involves using flat files (in CSV or text format) to transfer data. Some systems have built-in functions to automatically export flat files to a server, and some can also import files. Note that this approach only supports the transfer of data, nothing more. All business logic is handled within the source and target systems.

Web services integration leverages functionality exposed by a system to the Internet for other systems to interact with it. In addition to transferring data, web services can trigger actions within the system, such as enabling another system to instruct a MAP to run a batch email campaign, without someone having to log into the MAP and performing that task. Web services can open many possibilities for interactions between systems. However, customers are limited to the capabilities offered by each vendor.

With either approach, each system must already have the capability built-in. You can’t add the function directly into the platform.

These are how one system communicates with another over the Internet for its web services. Without getting into the details or the arguments of which is better (again, just google for more information), let’s just say that REST is newer than SOAP, and the trend favors using REST over SOAP. For this reason, most vendors are expanding their REST web services and planning to deprecate their SOAP web services (if they already had one, of course).

Two other terms that go together with these are JSON (for REST) and XML (for SOAP). These are the data formats used in communicating with these web services.

Lack of integration standards

There are no standards for a minimum set of operations that are exposed by a system, even for well-established categories such as marketing automation. Each system’s API is often unique in almost every way.

If you were to compare the API documentation between Marketo and Eloqua (and I have, extensively and repeatedly), you would see that they differ significantly. Although they offer some similar operations (such as retrieving person data), even those functions differ in structure and technique.

While both Eloqua and Marketo have REST web services, that’s where the similarities end. A CRM integration to Marketo looks very different than a CRM integration to Eloqua due to the differences and capabilities of their APIs.

Going custom: key considerations and options

Let’s assume that a native integration doesn’t exist or can’t be customized to meet your needs. Before diving in and building a custom integration, your team needs to consider several factors. Integration design is a balancing act that accounts for the following:

Timeliness and volume of the data sync

System capabilities often dictate how much data can flow between systems and how often. You need to understand the data availability requirements and anticipated record volumes. This will help determine the best method for integration, whether data flows need to be transactional, periodic or a mix.

For example, an online form submission where the respondent indicated that they want to be contacted about a product should be captured by the MAP then immediately passed to the CRM for follow-up by the appropriate salesperson. On the other hand, a digest of daily activity might be compiled and transferred as part of a nightly scheduled integration.

To handle volume, you must estimate how much data needs to be transferred at any given point in time. Account for scenarios such as a dramatic spike in form submissions due to a new product or service launch or an event list with a significant number of attendees that needs to be passed to the CRM for immediate follow-up. Sending one record at a time (as is the case with a transactional data sync) may not be as efficient as sending in a batch (periodic data sync) to ensure a timely action by the system receiving the data.

Think of transactional versus periodic data sync as analogous to a triggered versus scheduled email campaign. You want certain emails to be sent to the recipients immediately, such as a thank you email when someone submits an online form. Other emails, such as newsletters, can go out en masse at a scheduled day and time. Similarly, certain data should get to another system as soon as possible while other data can be passed at regular intervals.

Technical readiness for integration

In addition to understanding how much data can flow and how often, you will need to determine system capabilities to meet your needs. Flat-file integration functionality can enable you to achieve an automated data transfer with a minimum of time and effort. Web services could provide more options for the integration, but your team will need to determine if the REST or SOAP API is robust enough to meet your use cases, now and into the future.

For example, one MAP system supports flat-file data transfers while another has no built-in capabilities at all. Some offer webhook capabilities, meaning they can send data transactionally to other systems without the need for an integration middleware.

However, just because a system has a feature doesn’t necessarily mean it will meet your requirements. For example, one MAP’s file-transfer functionality is limited to one-hour intervals, meaning it can’t transfer more than 24 files of a given dataset in a day. Most web services APIs limit the number of calls per day (without paying additional fees) as well as the number of records within each call. Some have data insertion and extraction limitations that may require a different integration process than another system, even though it may be in the same functional category such as MAP.

Team readiness: skills and knowledge

In addition to having the technical tools, your company needs to have people with the skills and experience in designing, building and maintaining integrations between disparate marketing systems. Integrations often involve more than mapping data and consuming APIs. They require architected data flows, and they should be able to easily recover from system downtime or errors.

Your team should be able to understand marketing objectives and define business use cases, then design interfaces that meet marketing and technical requirements. They should also have knowledge of data integration platforms and techniques. They should be able to build integrations that can be rapidly reconfigured to meet shifting business requirements.

If you find deficiencies with your resources, you have options. Depending on your budget and timeline, you may train current employees and/or acquire new talent. You can also engage MarTech integration consultants for design advice or to build the integration for you.

Budget is a significant factor to the integration design and implementation. You must account for costs other than the integration technology itself, such as training or acquiring new personnel. You may need to do some process re-engineering to better align with system functionality.

An important cost that is often overlooked is data cleanse and normalization. Before any integration can go-live, an initial data load must be performed to ensure the integrated systems start off with the same sets of data. As part of this exercise, the existing data should be cleansed and normalized before the initial data load has taken place. To ensure high data quality is maintained, a data management strategy should be defined and implemented across systems.

Stakeholders may be clamoring to get data flowing sooner than later to ensure they can meet their performance deadlines. If time to value is critical, you should consider hiring outside consultants, as they can quickly implement higher quality integrations given their experiences on a variety of platforms for a broad range of business cases. This may save both time and money compared to a trial-and-error approach.

Integrating in a cloud-based world

Homegrown solutions (“dark integrations” using programming or scripting languages such as Java, C#, PHP or Perl) are things of the past, especially in integrating Software-as-a-Service (SaaS) systems. Unless you’re an integration software vendor, it’s not your core competency; it’s an opportunity cost you can’t afford. Without a significant investment of time and effort, homegrown integrations won’t have the bells and whistles of a vendor solution, such as:

Operational functions of monitoring, alerting and retries

Implementation functions of development, test, deployment and maintenance (including monitoring and rollback)

User interface for managing field mappings or system configurations

Use a commercial integration platform, especially an integration-Platform-as-a-Service (iPaaS), whenever possible. Many provide built-in connectors that abstract away the complexities of interacting with the API of the target system, such as maintaining active communication sessions and making multiple calls to retrieve all relevant data due to API volume restrictions.

Some important considerations in selecting an integration platform:

Look for point-and-click configuration versus code development for commonly-used functions such as data transformations and field mapping.

Find out what you can do with the connectors for your platforms. Don’t rely solely on what the vendors tell you what you can do.

There likely will be gaps between the platform API methods and those made available with the connectors.

Not all connectors are built alike; some vendors support more API methods than others for a given platform.

Be wary of vendors that tell you they can build a missing connector right away — this can end up taking more time and effort than you had planned.

Avoid the Enterprise Service Bus (ESB) mentality. Its time has passed, and it’s not relevant in a SaaS world. (See Maneesh Joshi’s article, , for a detailed discussion on the topic.)

Getting help

The exponential growth of marketing tools in the past few years has brought on challenges in connecting them together, especially considering the lack of integration standards. Unless your team is intimately familiar with the integration techniques of martec systems (and, specifically, SaaS-based applications), you may want to consider an experienced partner to assist and guide you in this process.

What did you think of this article as an entry in essay contest for the upcoming ? If you liked it, you can register your vote in the contest by sharing it on LinkedIn, Facebook, and Twitter.

Source

http://chiefmartec.com/2017/04/hackies-cmos-guide-integrating-marketing-technologies/

[tinygardenphilosopher]

Hands-on guide on Visualforce flows

What is visualforce flow? When I first heard about Salesforce Flow also called Visual Flows, Visual Workflows. Want to streamline your opportunity creation process without the need to code? The use cases for Flows are endless. Flow is a powerful business automation tool that can manipulate data in Salesforce in a variety of ways. The ease of creating flows makes it the number one go-to tool when it comes to complex business requirements.  The Salesforce platform’s object relationships and overall how Salesforce runs. You have got to have at least mid-level of understanding of SFDC and its features in order properly use flows.

How a flow is created? Flows can be created from Setup, enter Flows in the Quick Find box, then select Flows, and then click New Flow.

There are 3 main “building blocks” of the flow: Elements represent actions that are executed in the flow Connectors define which path the flow takes Resources are the values that can be referenced anywhere in the flow

Visualforce flow -It allows to automate business process by building application, knows as flows that collect, edit, update and create salesforce information. - Flow can execute logic, interact with salesforce database. - Flow designer tool is used for creating flows, configure screen, and define branching logic without writing any code.

Thanks for reading..............