![]() After all, five years is considered an eternity in software design and architecture. Since it has been five years, I thought it would be appropriate to see how Salesforce has changed. In fact, the project was considered the most-successful software implementation for my employer – which was delivered without any delays or compromise in functionality. Our implementation went live in November 2015. inability to end-to-end (E2E) test Salesforce customer solutions.inefficient request/response pattern for client/server communication.inability to work in a git-based workflow.non-standard options for client customization.When talking about the project, at the time, my biggest hesitations with the Salesforce solution were the following: This is in contrast to an open platform, wherein consumers generally have unrestricted access to applications and content. Walled Garden: a software system wherein the carrier or service provider has control over applications, content, and media, and restricts convenient access to non-approved applicants or content. As one might expect, getting to know Salesforce in the pre-lightning era seemed like it might be a step back because we all felt like we were working on an assignment that lived within a closed-source proprietary system, or what is often referred to as a "walled garden". Prior to this assignment, our project sprints had been focused on using leading-edge, open-source frameworks and technologies. The six-person team consisted of four full-stack developers and two quality assurance team members. convert an existing CRM solution to Salesforce.get the team up to speed with the Salesforce ecosystem. ![]() The goal of the 2015 initiative was two-fold: ![]() However, I did receive a pretty nice T-shirt for attending the session. Other than an introductory session from Salesforce during the 2008 Gartner Application Architecture and Design conference, I really had no depth of knowledge for a CRM product which promised a "No Software" implementation. I know that sounds extreme, but that was the reality for the six core members of our team who were required to adopt the platform as a part of a corporate objective. The year was 2015 and my feature team was forced to learn Salesforce.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |