Shopify Integration with Salesforce
Apr10

Shopify Integration with Salesforce

I have worked in Salesforce space for the past ten years and is the proud founder of the Salesforce Consulting company named Cloud Analogy. I have worked with our global clients to render Salesforce Consulting services in data migration, data integration and customized Salesforce solutions. Today, I am here to share my experiences about our client who wanted us to integrate Shopify with Salesforce. First, let us understand “What is Shopify?”. What is Shopify? Shopify is an e-commerce platform that comes with varied e-commerce and Point of sale features. These are what lets you start, manage and grow your business. This is one place where we can build our online store to manage our users. There is a Shopify online store builder that enables to customize the look and feel of an online store builder. Now, let us delve into the best CASE STUDY we have so far.   CASE STUDY-Requirements The requirements from the client were two of the following tasks: In the Shopify Store for the client, the user fills a registration form and submits the same form. A request is sent to the Salesforce and the system checks the same details inside the Contact object. If it exists, then only a corresponding client is created inside Shopify with details such as First name, last name, email address, and password.   In the situation, when the same details are not found in the Contact details of Salesforce, then an alert message is displayed as in the below figure.     The below figure shows how contact is created in Salesforce.     The second task was to integrate Shopify with Salesforce to add a tag in the customer profile. The already existing tag for the above customer profile in the above screen was that of participation tag. It was basically a picklist dependent Salesforce field and the client wanted us to reflect to the customer profile of Shopify. Let us now come to the solution that was provided by us. The Solution In the Salesforce Membership object, there is a picklist field.   On selecting a specific record in Salesforce, we arrive at the membership details page. This is where we can change the membership level say platinum, from a picklist field as shown in the below diagram.     After a change in the picklist value, the same value will be reflected in the Shopify page, after refreshing the page. The tag is changed to reflect the change in the picklist value. This we had done by implementation of a trigger that passes the change to the picklist value and sets it to put a request...

Read More
Client Security and Company Culture at Cloud Analogy
Mar25

Client Security and Company Culture at Cloud Analogy

Let me start with a weird security incident from today’s Facebook messenger chat. I received this email from a lady from a certain company and as we at Cloud Analogy do lots of email marketing campaigns, we thought this could be a reply from a prospective Salesforce services client. I immediately took this to my Sales team and did a quick data mining about the lady who emailed me and her company details. It looked a bit suspicious as the website of email Id was not found but a bigger firm with a similar name and details were found. Before my Sales Team could plan to do anything in reply, I got another message from her.     This Lady contacted me from her company email to my company mail and asked me to fix a code for her – sharing requirements. Initially I thought she was a contractor and wanted to hire us[Cloud Analogy]. Then soon this girl found me out on Facebook and asked for my help directly on messenger! I thought that this will be a quick question kind of freelancer test and I tried suggesting some solutions for the Salesforce trigger code she was referring to. Eventually, I found out that she was actually trying to take help from me to get her code done. It was merely some kind of test she was about to submit to her company or end client for that matter. I went ahead and warned her as this is a serious security breach and if her company finds out she will be in a bad mess. I am sure the conversation itself will be good enough to explain the entire story but I would still like to make a few more points for both new joiners to Software Industry or in fact to any Industry. Companies should conduct proper security training and HR team and Legal team must be able to explain an experienced or fresh talent joining the company about company policies and Security steps. We at Cloud Analogy tend to follow best practices in the industry and ensure data and client information integrity at all cost. Companies must regularly check/inspect the security breaches by various means and processes. We at Cloud analogy have hi-tech devices in our premise to protect and prevent any security breach. Some of these are: FingerPrint Scanner and ID cards for access to the workplace.  Security Camera at all workplaces   Google security to prevent any unwanted file and data sharing outside the company. Regular Notifications and alerts to Team leads. On-Premise Software copy check tool and Background verification of each individual. Legal Team...

Read More
Salesforce™ Android Attendance Management App
Mar12

Salesforce™ Android Attendance Management App

We are Salesforce™ Experts and we channelize our energy by documenting all the industry-specific technical problems we solve in Salesforce™ CRM world. Here I am going to explain Salesforce™ Android Attendance Management App. I was closely involved as a Salesforce™ Developer. And we have done it successfully. This is an Attendance management app integrated with Salesforce™ Rest API and Google Map API. We have developed this app for update the daily Attendance In-time and Out-Time of the employees. Username and Password required for login into the application. Once the user clicks on Attendance In Button a record will be created in Salesforce™ object and while leaving office to click on Attendance out Button same record will be updated with Time outfield. User can’t log in and log out from 100 meters away from the company. If the user forgot to log out while leaving office, So in next day as he will open the app the last record will update and total hours will be count as 5 hours means the half day will be count. We are using Username and Password flow for directly start the app, It will not ask any org credential .  Client Requirements A client wants an attendance app to manage attendance for employees. They want an Android app which will be managed by Salesforce. Client requirement is an employee will able to log in and log out only single condition when they are nearby (100 meters) of their office area. The user can see the office location and distance with the best path from their current location. A separate credential for every employee like Username and Password. A client doesn’t want to log in every time when they open the app on their respective devices. Once the user logged-in, they can’t log out. The user can put attendance only once i.e between 8 AM to 11:59 PM. All the record will be stored in Salesforce database. For every user total hours will be count every day. Our Solution We have developed an android app for attendance management. All the record will be stored and managed in salesforce™ DB. We have integrated Google Map and salesforce Rest API in this application. Using this app, the user can see the distance between office and their current location with the best path. We had provided login feature to all app users with their separate login credentials. We haven’t developed any logout button as per the client requirement. Once user logged-in then, they can’t exit the app until they uninstall it. We have created login credentials like Username and Password FLOW to start the app right away,...

Read More
Introduction to Salesforce DX
Mar07

Introduction to Salesforce DX

Developers are always source-driven people. Salesforce DX (developer experience) enables the developer to work with any externalized source – even incorporating version control. “What is Salesforce DX ? It is an open standard developer experience, letting you build with the tools you love including Git, Selenium, Eclipse, Sublime, and more. Salesforce DX includes an updated Eclipse integrated development environment (IDE) that significantly expands the value of the toolset to developers. However, the development process is source-driven. Moreover DX not only allows them to collaborate with other members of team. Moreover, the environment for a developer never works in perpetuity – something that the developer can simply dispose of, on project completion. It is this combination of the environment and the source code that leads to faster development of mobile apps -something that is a yearned by a developer always. Finally, it is a packaging model that is used to aid in the distribution of changes – across environments.The below figure shows some of the core principles around which modern software delivery is centred around. Let us now find out more on the advantages of Salesforce DX: Advantages of Salesforce DX The advantages of Salesforce DX are: Salesforce DX has a source-driven development process, This allows to test the features with agility and confidence. Salesforce DX helps developers build together in teams. In many ways, it brings together the best of the Force.com and Heroku developer experiences. It’s a new approach that supports team collaboration with a focus on quality, predictability, and an open and standardized development lifecycle on Salesforce. The advantage for this is that it enhances productivity and a faster development – thereby decreasing the time to market the product or service. A core theme of Salesforce DX is letting developers choose the tools they want. For example, we’re investing in making the Force.com IDE a best-in-class solution, but with Salesforce DX and our new command-line interface, you can use the text editor or IDE of your choice, along with the CLI, to develop your app. It’s up to you. When it is time to  test your development work, then a Salesforce DX uses a scratch org and pushes the metadata. This scratch org, otherwise known as developer server.- serves only the purpose of testing and validation. There must be automated test runs for each of the change sets for your application. This is named as continuous integration(CI). This is for ensuring quality before any corrupt changes makes it way into the source repository. Following are some of benefits of the scratch org: It is easy to integrate scratch org into a CI process. The scratch orgs are...

Read More
Salesforce Requirements Gathering Techniques for Small and Mid Size Projects
Feb26

Salesforce Requirements Gathering Techniques for Small and Mid Size Projects

Sunday Morning, I finally got some time to be back to my fav work of sharing knowledge via blogs. This week I was able to get involved into a rapid-fire requirement gathering session of straight 2.5 hrs and was able to get to the requirements, pain points/ top 5 show stoppers and immediate solution as well. My specialty is suggesting solutions and approach within the process of understanding the problem with my past experience of solving similar problems or NEW features being launched by SalesforceTM every Release cycle. How Do I Gather Requirements? A project in a software development company starts with the Requirements Gathering phase. I have created a unique requirement gathering question and answers fill in the blanks I always take down with me in a meeting.  The requirements are gathered by the Business Analyst which is most of the time me and my team, employing a set of techniques. Sometimes there is a diverse set of techniques to be applied. All this is to accurately comprehend the requirements from the client or the other stakeholders in the organization. There is a need to choose the right technique and this changes from one stakeholder to another. In this post, I will narrate the various methods that our team at Cloud Analogy employs – to understand the client needs in a precise manner. Let me share with you about my experience with a client named Eric Wilson, for gathering requirements. I will highlight the various approaches, I resorted to. But before we go into further details, let me tell you something about Cloud Analogy. About Cloud Analogy Cloud Analogy is a Salesforce Consulting Company with a team of Salesforce certified experts – architects, developers, designers in handling various projects. It has worked in various domains – finance, healthcare, real estate and has shown an unprecedented level of growth in the last few years of its operations. The team comprise of talented Salesforce professionals who have developed world-class applications in Salesforce technology, as well as mobile app development. It has maintained its winning spree by handling some of the complex projects, from clients all over the world. Let us now delve, right into these approaches of requirements gathering – resorted by Cloud Analogy. What are the Approaches Adopted? The approaches adopted by us are: 1. Fixing a Facilitated Session a. Client Requirements b. Solution Provided 2. Scope of Training 3. Request for Proposals (RFPs)1. Fixing a Facilitated Session The clients come to know about our profiles from Upwork or some other sources say our websites, social media posts etc. They fix up an appointment with us through Calendly. We...

Read More