Tuesday, October 6, 2015

View Setup Audit Trail in Salesforce

View Setup Audit Trail

Salesforce.com keeps an Audit Trail of configuration changes made in the Setup section. This Audit Trail is available for administrators to track recent setup changes. This becomes especially helpful if there are multiple administrators for your organization. Let's start with an example where Appiuss has many system administrators and they want to track who changed the configuration. Only the system administrator or a user with View Setup and configuration permission can use this feature. You can see the last 20 entries under Setup Audit Trail and are able to download data of the last six months for your organization.
To access the Audit Trail, follow these steps:

1.   Navigate to Setup | Administer | Security Controls | View Setup Audit Trail



2. The preceding screenshot shows the last 20 most recent configuration changes for your organization.

The description of the various fields is as follows:

Field
Description

Date
The Audit Trail shows the date/time for every change.

User
This field shows the information about the user who made the change, in this case, the username.

Action
This field shows the action taken by the user. Examples include changing the workflow rule name and object name, field creation, and password change.

Section
This shows which section was impacted by the change, for example, customize accounts, workflow, manage users, reports, groups, and so on.

Delegate User
This shows the name of the delegated user who made the changes. This will have value only if changes made by the delegated user are on behalf of another user.

Audit Trail key concepts
You can check Audit Trail for the mentioned section/type of changes:
Administration: This will track various administration changes such as changes in the company information, multiple currencies, users, e-mail address changes, profile changes, roles, record types, creating e-mail footers, and domain name changes.

Customization: These changes are related to the interface changes, forecasts, contracts, ideas, field tracking in feeds, support-related settings, process setups, and changes to groups.

Security and sharing: These are related to security settings and sharing, such as password policy changes, session setting changes, changes in SAML settings, and so on.

Data management: These changes are related to the mass deletion of records, data export requests, the mass transfer of records and import wizard usage, and changes in analytic snapshots.

Development: This change is related to Apex classes, triggers, and Visualforce. Changes can include modifications to triggers, classes or Visualforce; remote site access setup; and Force.com site setup.

Various setups: These include various setup changes such as the creation of an API, usage metering notifications, territories usage, workflow and approvals settings, and AppExchange package installation/uninstallation, and creation and deletion of workflow actions are also tracked.

Using the application: These changes are related to the changes in the account team and opportunity team selling settings, Google App services, and the enabling and disabling of partner and customer portal users.


The View Setup Audit Trail page only shows the 20 most recent entries in the list. To download the full audit history for the last 180 days, click on the download link. 



Thanks for reading....... 

Monday, October 5, 2015

The Dreamforce '15 Ultimate Content Guide

The Dreamforce '15 Ultimate Content Guide

Here is a breakdown of where you can find the best videos, pictures, announcements, sessions and more from Dreamforce ‘15:









Limitations of the workflow in salesforce

Limitations of the workflow

The workflow feature is only available in Enterprise, Unlimited, Performance, and Developer editions. For the Professional Edition, you can enable this feature after paying an extra amount. As Salesforce is based on a multitenant architecture, it imposes a few limitations on the workflow:

• For each workflow rule, you can have the following:
  • 10 time triggers
  • 40 immediate actions
  • 40 time-dependent actions per time trigger


• For both immediate and time-dependent actions in one workflow rule,
there can be no more than:

  • 10 email alerts
  • 10 tasks
  • 10 field updates
  • 10 outbound messages

• The workflow time trigger per hour limit for different editions are as follows:
  • Professional Edition: 250
  • Enterprise Edition: 500
  • Developer Edition: 50
  • Unlimited and Professional Edition: 1,000

• The workflow e-mail limit per day is as follows:

  • 1,000 per Salesforce standard license
  • 200,000 per organization


Note: Once an organization's daily e-mail limit of 200,000 exceeds, Salesforce will send a warning e-mail to the default workflow user and discard all the e-mails. Salesforce does not try to resend them later.




Thanks for reading.....

Language settings and its importance in Salesforce.

Language settings and its importance in Salesforce

As Salesforce is being used across the globe and we all use different languages to communicate, Salesforce supports multiple languages. The Salesforce web user interface, Salesforce for Outlook, Connect for Outlook, Connect Offline, and Connect for Office are all available in various languages.

The Salesforce web user interface supports two language settings.
Personal settings
Let's start with an example. Tom is a new hire from Russia. The default organization language is set to English, which means all the text and online help are displayed to all the new users in English. Tom would like to change his complete user interface to Russian.
Users can change the default language to their local language to display the Salesforce text, images, buttons, and online help.
To change to your personal language, follow these steps:
1. Navigate to Name | My Setting | Personal | Language & Time zone.
2. Then, select the language from the Language drop-down list:




You can find more information about the language Salesforce supports as the standard language in the information box.

Note: If you are not able to find your preferred language, then contact your system administrator to enable it. In the preceding example, the system administrator enabled the English, Deutsch, Español, François, and Italiano languages for the organization so that users can get these options under the Language drop-down list.

Organization's default language settings
A system administrator can enable multiple languages for your Salesforce organization. This means users have the option to select their preferred language from the available list.
Salesforce offers three levels of language support, as follows:
  1. Fully supported languages
  2. End user languages
  3. Platform-only languages

Fully supported languages
Fully supported languages, such as Thai, Russian, English, or Danish, are the ones where the user functionality and help pages in the application are completely translated into these languages.

Note: The fully-supported languages list includes Chinese (simplified), Chinese (traditional), Danish, Dutch, English, Finnish, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Spanish, Swedish, and Thai. Even though the Salesforce interface is completely translated to Thai, the help page remains in English

End user languages

End user languages are useful when you are working in a multilingual organization where you speak a language that is different than your headquarters. End user languages are used by users who would like to access the app in that language, but do not want to access the Setup menu.
Let's start with an example. A company has its headquarters in a French-speaking country, but that company has non-admin employees in other countries that would prefer to use the app in a language supported as an EUL. As they do not want to access the Setup menu and help pages, the EUL settings provide sufficient translations out of the box to suit their needs.

Note: The end user languages list includes Arabic, Bulgarian, Czech, English (U.K.), Greek, Spanish (Mexico), Hebrew, Hungarian, Indonesian, Norwegian, Polish, Romanian, Turkish, Ukrainian, and Vietnamese
Enabling an end user language
To enable an end user language for your organization, follow these steps:
1. Navigate to Setup | Administer | Company Profile | Language Settings.
2. From the Language Preferences section, select the Enable End User Languages checkbox to enable it:


 3. Then, it will add all the end user languages to the available language multi-select picklist.
 4. Click on Save.
Platform-only languages
Platform-only languages are used to localize the custom functionality (apps) built on the Salesforce Platform. The platform-only languages allow organizations to provide their own translations via the translation workbench for languages that Salesforce doesn't provide any translations for.

Note: The platform-only languages list includes Albanian, Armenian, Basque, Bosnian, Croatian, English (Australia), English (Canada), English (India), English (Malaysia), English (Philippines), Estonian, French (Canada), Georgian, Hindi, Icelandic, Irish, Latvian, Lithuanian, Luxembourgish, Macedonian, Malay, Maltese, Moldovan, Montenegrin, Portuguese (European), Romansh, Serbian (Cyrillic), Serbian (Latin), Slovak, Slovenian, Tagalog, Urdu, and Welsh.

Enabling the platform-only languages
To enable the platform-only languages for your organization, follow these steps: 
1. Navigate to Setup | Administer | Company Profile | Language Settings.
2. From Language Preferences, select Enable Platform Only Languages:


3. This will add all the end user languages to the available language multi-select picklist.
4. Click on Save.

Once you enable the platform-only language, Salesforce will enable the end user language automatically.

Note: What happens when the system administrator changes the organization's default language from English to Russian if the user's personal language preference is already set as Russian?.The user will still see Salesforce in Russian. If a personal preference is not set, then Salesforce will automatically change everything from English to Russian 



Thanks for reading.....

Saturday, October 3, 2015

Two-factor authentication in Salesforce

Two-factor authentication in Salesforce

Two-factor authentication in Salesforce is a two-step login process. You can enable it if your users need more security rather than the ordinary login process. In this process, once the user logs in using their username and password, a token or passcode is sent to their device, which they need to enter in order to finally log in.

Time-based tokens can now be used as a substitute to SMS-based (not available for non-English organizations) and e-mail-based login verification to activate a computer:

1. Download the supported Authenticator app for your mobile devices.

2. Create one permission set with the name Two Factor Authentication.         
To do this, navigate to Name | Setup | Manage Users | Permission sets | New and enter the data as shown in the following screenshot:


3. Add the Two-Factor Authentication for User Interface Logins system permission in the newly-created permission sets. 


4. Now, navigate to the user's record for which you want to enable Two Factor Authentication.
  
5. Add this permission set to the user's record by clicking on the Edit Assignments button in the list related to Permission Sets Assignments on the user's record. 

6. Now, log out from Salesforce and log in using your credentials; you will come across the following page:



7. Open Google Authenticator App on your mobile and scan the QR code, and it will look like the following screenshot: 

8. Enter this code in the login screen and access your organization.

Removing Time-Based Token/Two-Factor Authentication


It's very easy to do this; just navigate to the user's record and click on the Remove link beside Time-Based Token:



More about Two-factor authentication in Salesforce








Thanks for reading......


Friday, October 2, 2015

Holiday settings in salesforce.

Holiday settings in salesforce.

Let's start with an example. Srinivas is working as a support agent in a company. He is resolving an ample amount of cases per day, and the response time for every case is 3 hours. Now, he is worried because April 18 is a holiday for Good Friday and if cases come in on that day, they will be escalated to the manager.
Holiday settings define that your organization is not working on that day. If some cases are raised on that day and waiting for a service agent response, Salesforce will not count that day as a working day and the case will not be escalated.
Setting up the holiday settings
To set up the holiday settings for your organization, follow these steps:
1.  Navigate to Setup | Administer | Company Profile | Holidays.

2.  Click on the New button.


3. Enter data in the Holiday Name, Description, Date, and Time fields. You can set recurring holidays as well. To do that, select the Recurring Holiday checkbox and fill in the Frequency, Start Date, and End Date fields:
4. Click on Save

Associating holidays with business hours

You can associate holidays with business hours so that Salesforce can suspend any escalation rules associated with it. There are two ways to associate business hours and holidays.
Method 1 – associate business hours with holidays
To associate business hours with holidays, follow these steps:
1.  Navigate to Setup | Administer | Company Profile | Holidays.
2.  Click on the holiday from the Holidays list


3. It will open the Holidays detail page.
4. Click on Add/Remove from the Business Hours list.
5. In addition, add any Business Hours as per your needs. 




It will associate one holiday with multiple business hours.

Method 2 – associate holidays with business hours
Another way to associate holidays with business hours is from the business hours instead. To associate holidays with business hours, follow these steps:
1.  Navigate to Setup | Administer | Company Profile | Business hours.
2.  Click on the Business Hours option from the available list:



3.  It will open Business Hours detail page.
4.  From the Holidays list, click on the Add/Remove button.
5.  It will redirect you to the next screen where you can associate the current business hours with multiple holidays:




This will associate multiple holidays with one business hour.



Thanks for reading.......







Thursday, October 1, 2015

Single sign-on settings in salesforce.

Single sign-on settings in salesforce

Single sign-on allows users to log in via external environments. To configure the single sign-on setting for your organization, follow these steps:
1. Navigate to Setup | Security Controls | Single Sign-On Settings.
2. Click on the Edit button and select the SAML Enabled checkbox:





1. Click on Save.
2. You will be redirected back to the Single Sign-On page.
3. Under SAML Single Sign-On Settings, click on New


4. It will redirect you to the SAML Single Sign-On Setting page where you have to provide various details:


The descriptions of the various fields are found in the following table:

Field
Description

Name
Enter the full name.

SAML Version
Select the appropriate SAML version.

Issuer
Enter the identity provider's name.

Identify Provider Certificate
Click on the Browse button to upload the authentication certificate issued by your identity provider.

Custom Error URL
Enter the URL that users should be redirected to, in case any errors occur during SAML login.

SAML Identity Type
Specify what the SAML identity type will be. You can select either using the Salesforce.com users or the Federated ID.

SAML Identity Location
Specify the location of the SAML identity.




Authentication providers

These days, we are using various login credentials to access multiple websites such as Facebook and Janrain. To access these websites, you have to remember multiple login credentials, and if you are using Salesforce, that is one more credential to remember. Once you enable this feature, users can log in to Salesforce from an external service provider such as Facebook or Janrain, and there is no need to remember one more credential to log in to Salesforce. You can use your favorite account to log in to Salesforce.

To configure an authentication provider successfully for single sign-on, you need to perform the following activities:
1. Configure the login service provider website.
2. Use Apex to create a registration login handler.
3. Define the authentication provider in your Salesforce.com organization.
4. Once you set up the authentication provider, the steps that a user has to perform will be described as follows.
5. Users will try to log in to Salesforce.com using third-party identity credentials.
6. The login request will be redirected to an authentication provider for the service provider.
7. The third-party service provider authenticates the login credentials and redirects the user to Salesforce.com with the credentials.
8.  Finally, the user gets access to Salesforce.com.

To configure the authentication provider in Salesforce.com, you have to follow these steps:
1. Navigate to Setup | Administer | Security Controls | Auth. Providers.
2. Click on New, as shown in the following screenshot:



3. It will redirect you to a new page, where you have to select the authentication provider 
4. The following is a screenshot for Facebook as the authentication provider:


5. Here, you have to specify information for the mandatory fields (the fields that feature a red mark). The fields shown depend on the authentication provider. The description of various fields is as follows:

Field
Description
Name
This specifies the name of the authentication provider.
URL Suffix
This specifies the suffix to be used in client configuration URLs.
Consumer Key & Secret
The authentication provider provides this information. In this scenario, Facebook will provide the information when you create an application in Facebook.
Custom Error URL
This is an optional field where you can specify the URL to be used by the provider to report any errors.
Registration Handler
This is the Apex class used for registration handling.
Portal
If the SSO needs to be extended to portal users, select an appropriate portal for this.






Fiscal year and its customization in Salesforce.

Fiscal year and its customization in Salesforce.

A fiscal year or financial year is a period of time used to calculate annual (yearly) financial statements in businesses and other organizations. The system administrator can set the fiscal year for your organization. The fiscal year settings are used to report on the fiscal year timeline.

Salesforce supports two types of fiscal years:
  1.  Standard fiscal year
  2.  Custom fiscal year

 Standard fiscal year
Salesforce provides the Gregorian calendar as the standard fiscal year calendar by default. But this is not the same for every organization as some organizations use different calendars and need to change the fiscal year start month, for example, for the fiscal year starting in April, the standard fiscal year is used. Standard fiscal years can start on the first day of any month. Additionally, it can be defined whether the fiscal year is based on the start or end of the selected month.
To set up a standard fiscal year for your organization, follow these steps:
1. Navigate to Setup | Administer | Company Profile | Fiscal Year.
2. Select the option of Standard Fiscal Year.
3. Select the start month for the fiscal year.
4. Choose whether the fiscal year is defined based on the end or start of the month as shown in the following screenshot:
  




5. Optionally, you can select Apply to all Forecasts and Quotas if you want to apply the new fiscal year settings to your existing forecasts and quotas. This option may or may not be available depending on your forecast settings.
6. Click on Save

Custom fiscal year
The custom fiscal year option is used when the standard fiscal year does not meet the organization's requirements. To use the custom fiscal year, the system administrator has to enable it. Complex fiscal year structures can be achieved using the custom fiscal year option. Enabling custom fiscal years does not automatically define them. You must define all of your company's custom fiscal years so that they fit your company's calendar.
To set up a custom fiscal year for your organization, follow these steps:
1. Navigate to Setup | Administer | Company Profile | Fiscal Year.
2. Select the option of Custom Fiscal Year.
3. Select the checkbox next to the statement Yes, I understand the implications the custom fiscal year feature has on my organization and I want to enable it.
4.  Click on Enable Custom Fiscal Years.
5.  Click on OK.

Note: Enabling custom fiscal years is not reversible. After enabling custom fiscal years, you cannot revert to standard fiscal years . Before enabling the custom fiscal years, make sure that you have exported any data related to the fiscal periods. 

Defining a new custom fiscal year
To define a new custom fiscal year for your organization, follow these steps:
1. Navigate to Setup | Administer | Company Profile | Fiscal Year.
2. Click on New. It will open a Custom Fiscal Year Template window to set up a new custom fiscal year:


3. In the template window, you can choose a template type based on your needs. Click on Continue and you are done.
4. The next step is to set the fiscal year start date. For this, enter the fiscal year name and choose the start day of the week. Here, you can reset the fiscal year structure as well.
5. Click on Save



Thanks for reading......





 
| ,