Step by step guide to setup Git Server using Bitvise SSH Server
Recently for one of client, I was in need to setup Git on their intranet. Being healthcare industry and compliance issue, source code could not leave company network and therefore needed in-house solution for Source Code Management (SCM) and automate builds.
In this blog post, I will explain how did we setup Git server that is accessible from anywhere in company network.
We need below two software installed on system which will act as a Git Server.
Navigate the Salesforce Advantage – New learning module and project added to Trailhead
Its not too long when Trailhead was announced in Dreamforce, who have though that it would be integral part of learning for Salesforce developers, admin, business analyst and even customers ?
Trailhead recently released new trail Navigate the Salesforce Advantage for readers, who want to know about Salesforce, its culture and what makes it outstanding and different from other technology companies.
Tutorial to create custom Task in ANT with complete source code
ANT is very powerful and one of the most used tool in Java and other platforms like Salesforce. In Salesforce, ANT is officially used to deploy changes on instances using Metadata API. It is also integral part of Continuous Integration. Even though, there are hundreds of libraries and ANT Tasks are available to use, however there are many scenarios where we need to create our own custom Task.
I am using many custom ANT tasks in my projects and its very easy to create. For example, I have created automated data load process with custom ANT task, which is almost as powerful as of any paid ETL tool.
In this blog post, We will go through creation of very simple ANT plugin. We will create a custom ANT Task with nested tags , attributes and then print it on console. It shows that, we can read attribute passed in build.xml. if we can read attribute, then writing any custom logic is not a big deal. Continue reading “Creating custom ANT plugin or Task in Java”
This blog post explains simple use case of Nested Lightning Component. It goes through example on how to interact and combine nested components to be used in parent Lightning component.
This is a first blog post of a series, to develop advance lightning components and understand various features offered by Salesforce Lightning Platform. This post will explain why do we need nested components and how do they communicate.
At first, nested components looks like displaying something in child component and wrapped in parent component. However, to make most of nested components and designing efficient Lightning components, we should use nested component only to define set of rules. Unlike components in Visualforce, where we render some reusable output on page, Nested components in Lightning defines set of attributes to be used by parent component.
Why Renderer is important in Lightning Components. Best practices to follow and use case example of using Renderer methods in lightning components.
Chances are very high that most of you already know why do we need controller, helper, style and component resources in Lightning component. Renderer is one of the overlooked and very powerful resource (feature) while developing Lightning components.
We can use renderer functions to dynamically change components look and feel and tweak its behavior as well. You might not need this Renderer resource at all until, you are working on some advance component or run into problem as discussed in this post.
Basically, Renderer consists of following four methods:
This method returns html element from DOM hierarchy.
This method executes when html element (DOM node) is rendered in browser.
This method executes when component is changed. for example, if any attribute is changed on component then this method gets executed.
Whenever component is destroyed from browser’s DOM hierarchy, this method gets executed.
In previous blog post, we discussed best practices of writing Test classes in Apex. In old school way, if we wanted to create records for test methods, helper or utility classes were favorite option for developers.
However this approach has few disadvantages
Multiple Test classes could depend on these utility methods
It creates tight coupling between classes
Deployment could be slow if unnecessary test record being created for test methods
If class to create test record is not marked with @isTest then it will count against allowed apex code in instance
Test classes needs to explicitly call method to create test records
Using Salesforce Spell checker in custom Visualforce pages
Standard email functionality in Salesforce supports spell checker out of the box. These days, all modern browsers already has spell checker and customer may agree to use it. However there are some customer, who wants standard look and feel of application include spell checking.
Designing application to store passwords or secrets in Salesforce using Manage packages
Salesforce supports Encrypted Field out of the box on standard or custom objects. However, users with appropriate profile or permission set can easily view content of those fields. If we want to store secure information like passwords (of external systems), then there is no direct way to achieve this. If we think about passwords, no one should be able to view it. If we forget password, then instead of system sending old password, it forces us to reset it.
We will create same behaviour in Salesforce where stored password cannot be viewed by anyone.