Thursday, 25 May 2017

[#Blogged] Features Professional edition in Salesforce

Lighting Professional Edition in Salesforce
There are few features which are not available in the professional edition which needs to take care during implementation:
No Account Assignment Rules
No Territory Management
No Sales Teams (aka Opportunity Teams)
Configuration / Security / Administration
No Joined Reports
No Bucket Fields

No Cross Filters (e.g. Accounts without Opportunities)
No Dynamic Dashboards
No Scheduled Dashboards (you can schedule a Report)
50 Custom Report Types vs. 200 in Enterprise Edition
See our post on Enterprise Analytics for more details on these features
Marketing
250 emails sent in a single mass email blast vs. 500 in Enterprise Edition
Sales (Sales Cloud)
Limit of 20 Custom Fields on Activities vs. 100 in Enterprise Edition
Limit of 10 Custom Tabs vs. 25 in Enterprise Edition
Limit of 50 Custom Objects vs. 200 in Enterprise Edition
No Workflow / Approvals / Visual Workflow
No Person Accounts
No Ability to mass Grant Login Access to a System Administrator
No Data Export (Weekly Export Service to backup your Salesforce org)
Support (Service Cloud)
Limit of 20 Validation Rules per Object vs. 100 in Enterprise Edition
Limit of 100 Custom Fields per Object vs. 500 in Enterprise Edition
No Service Cloud Console
No Salesforce Knowledge (Note: Knowledge is available at an additional cost in Enterprise Edition, and included in Unlimited Edition)
No Live Agent (Note: Live Agent is available at an additional cost in Enterprise Edition, and included in Unlimited Edition)
Extending Salesforce / Community / Portals


No Partner or Customer Portal
No Websites (aka Site.com / Force.com Sites)
To use Chatter Plus (Chatter Only) licenses in Professional Edition, you’ll need to contact Salesforce support and have Profiles enabled
No Salesforce Communities (released Summer ’13)
Custom Development and Sandboxes
No Change Sets (which are needed to deploy custom code)

No API 
Limit of 10 Developer Sandboxes
Lightning Professional Edition Limits
5 Process Builder processes
2 Permissions Sets
2 Custom Profiles
3 Record Types
2 Page Layouts
10 Developer Sandboxes
A detailed difference between the features available and variations of these features in each of the editions is available on http://login.salesforce.com/help/doc/en/limits.htm.You can understand the pricing on http://www.salesforce.com/in/crm/editions-pricing.jsp.
Download the full edition comparison chart 

Monday, 22 May 2017

[#Blogged] Developer Edition "DE org"

Development and deployment on Force.com typically take place in an environment or org, which provides a number of features and accommodations for applications within that environment. An environment lets you instantly start developing, testing and deploying your app in the cloud. For an explication of the types of environments, optically discern An Exordium to Environments.
Follwing are the salesforce licenses : 
Salesforce Customer Portal
2 Salesforce CRM licenses
2 Salesforce Mobile licenses
3 Salesforce Platform licenses
5 Salesforce Partner licenses
10 Salesforce Customer Portal Manager licenses  

Other Limits for Developer Edition:
5.0 MB of Data Storage
20.0 MB of File Storage ( attachments)
5000 API requests per 24 hours
Any number of applications
A 500 MB bandwidth and 10 minute service request time limits (per rolling 24 hours) 

Developer Edition (often referred to as a "DE org") is a fully-featured development environment with limits on data and users. Developer Edition is used for:


Trailhead - Salesforce's free and fun online learning tool requires Developer Edition.

Development and Testing - If you don't have a sandbox (a copy of your Salesforce production organization), you can use Developer Edition to isolate development and testing.

ISVs - Independent Software Vendors use DE orgs to create managed packages, which may then be released as apps on the AppExchange.


Developer Previews - Sometimes we release new functionality to Developer Edition before other editions, so you can practice with it.


Fun - You can have more than one Developer Edition, so use one whenever you want to mess around and try something new.

How to signup for free developer edition in Salesforce?

1. Open "http://developer.force.com/".

2. Click "Sign Up" button.
3. Fill in the details. Click "Sign me up". 
4. Verify the account in email.
5. Use "https://login.salesforce.com" for login.


Thursday, 18 May 2017

[#Blogged] Different Types Of Sandboxes

Sandboxes :

sandbox is a replica of an engenderment environment utilized for a variety of purposes, commonly including testing and development. Here's how it works: When you engender or refresh (essentially effaces and reconstitutes a sandbox utilizing the same name) a sandbox, a facsimile of the engenderment environment at that point in time is made.


Different types of Sandboxes 


FullSandbox - Plenarily testing changes against authentic data afore promoting to engenderment.  This may include utilizer acceptance testing.  All changes must go through this sandbox.  If multiple admins/developers are working on overlapping areas, this is the place where changes get merged.  Force.com IDE can be habituated to compare changes by separate developers of the same apex code.
Full sandboxes have the same storage limit as your production organization.Once you refresh the Full Copy Sandbox then to refresh it one more time you have to wait for 29 Days.

 Partial Data Sandbox - This is an incipient sandbox type and I am not quite sure what the intention was.  Probably just a more frugal alternative to a full sandbox.  If you have a full sandbox, then partial data sandbox sounds like a good place for utilizer training for incipient features, incipient employees, etc.  Having authentic data can authentically avail with training.  Additionally, possibly a place to work on integration changes since it can hold quite remotely of authentic data.

Partial Data sandboxes have a 5 GB storage limit.
Once you refresh the Partial Data Sandbox then to refresh it one more time you have to wait for 5 Days.

Developer - A place to work through solutions to incipient requisites.  The main conception is to keep arbitrary experimentation out of the full sandbox.  It there are multiple admins/developers, each one should get their own so that they don't trample on each others work (until they deploy to the full sandbox).

Developer sandboxes have a 200 MB storage limit.


Once you refresh the Developer Sandbox then to refresh it one more time you have to wait for 1 Day.


Developer Pro - The main distinction between this and Developer is the amount of data that can be stored.  It additionally prehends some product data from engenderment.  If those two things are paramountutilize this one.  Otherwise, it's interchangeble with Developer.

Developer Pro sandboxes have a 1 GB storage limit.


Once you refresh the Developer Pro Sandbox then to refresh it one more time you have to wait for 1 Day.

Saturday, 13 May 2017

[#Blogged]Time To Upvote -Series (Part 1)

Here we have some idea's which need to be upvoted :

Idea 1 
Make the Manage External User button available in lightning

Currently the Manage External User button and the nested buttons it hosts are not available in the lightning user interface, as a result users have to switch between lightning and salesforce classic to access the functionality, another drawback to lightning as having to toggle back and forth between two different interfaces undermines the value of lightning.  Please make the manage external user button and the nested buttons it hosts available in lightning


Upvote 

Idea 2

Choose Who To Send Flow Fault emails and Process Builder Error Emails to
The notifications currently go to the user who built the flow or process builder.
I am currently in a situation where the original user who created the flows in Sandbox and deployed them is no longer active. I therefore must change his email in order to receive the error messages on existing flows.


Idea 3 
Increase the limit on the number of reports a user can subscribe to
The new report subscription feature is really nice, but only being able to subscribe to 5 reports is not helpful.  Most users who want to subscribe to reports want to do this for at least 10 - 15 reports.  I'm not sure why the limit is hard-coded to be 5 but having a higher limit (like 25?) would be much appreciated.

Upvote 

Idea 4 
Process Builder: Error messages
Process Builder works great, but when there is a validation error or any other error, it doesn't provide the much information to user and user will never know how to resolve that issue.
Admin gets an email for this exception with the proper message, but if we can improve the error messages for the end user also, that would be great.