Another Salesforce blog!!!

Salesforce, Apex

SALESFORCE

What is a Salesforce DX “Project”?

In general, a Salesforce DX Project is a new local file structure that collects your org’s metadata (code and config), org templates, sample data, and tests. The project root is often the repository root of a version control system (VCS) as well. Specifically, an SFDX Project exists when you have a local directory that contains […]

available security features in salesforce!

Salesforce provides security controls to manage the accessibility of functionalities i your application and also the visibility of the individual records it creates. Functional security Data security Functional security: Security that applies to application objects and some code entry points (providing APIs) and also Visualforce pages that deliver the features of the application is referred […]

ROLLUP SUMMARIES AND LIMITS

When it comes to performing calculations on your data, the Salesforce platform provides a number of options, API, Apex Triggers, Visualforce and Rollup summaries. The Rollup summary provides a code-free solution with the ability to apply some condition filtering. Rollup summary fields can be referenced and combined with other features such as formula fields and […]

custom field features – default field values

Adding default values to your fields improves the usability of your appliation and can reduce the number of fields needed on the screen. Default values defined on custom fields apply in the native user interface and VF UI’s Example: Create a Year text custom field in the object and in the default value provide the […]

publication and licensing of your application

The following are other organization types that you will eventually eed in order ot manage the publication and licensing of your application. Production/CRM Org: the purpose of this organization for managing contacts, leads, opportunities, cases and other CRM objects. AppExchange Publishing Org (APO) This org is used to manage your use of AppExchange. This org is actually […]

package in one of two states

Packages can be uploaded in one of two states Release: Release packages can be installed into subscriber production orgs and can also provide an upgrade path from previous releases. The downside is that you cannot delete the previously released components, or change certain things, such as a field’s type. Changes to the components that are […]

package namespace

Important decision when creating a managed package is the namespace this is a prefix applied to all your components (custom objects, visualforce pages, lightning components etc…) The namespace prefix is an important part of the branding of the application since it is implicitly attached to any Apex code or other components that you include in your […]

PACKAGE TYPES AND BENEFITS

A package is a container that holds your application components, such as Custom Objects, Apex code, Apex triggers, Visualforce pages, Lightning Components, and so on. This makes up your application. While there are other ways to move components between Salesforce orgs, a package provides a container that you can use for your entire application or […]

How the Salesforce Platform Enforces Authorization

In most cases the platform automatically enforces admin-configured authorization settings, so your job is easy. However, because the platform is flexible, there are certain cases where developers can bypass authorization settings. To understand why and where this happens, you need to understand the two execution contexts that a Force.com app runs in: user and system. […]

Authorization in Salesforce

Access to online data is generally restricted to only those who are identified, authenticated, and authorized. There are three main ways: –> Create, read, update, and delete (CRUD) settings ——–> Determine which objects a user can create, read, update, and delete –> Field level security (FLS) settings ——-> Determine which fields a user can read […]

Previous Posts Next posts