shariq
IndividualForum Replies Created
-
Workflow tasks in salesforce are used to assigns a task to users. Using tasks we can specify the Subject, Status, Priority, and Due Date of the task. Tasks are workflow & approval actions that are triggered by workflow rules or approval processes.
-
Salesforce Workflow is a business logic that evaluates the records as they are created, updated in an object to apply automated process like Assigning Tasks, Emails, Field Update and outbound message sending.
-
Analytical Snapshot in Salesforce are used to create reports on historical data.
-
The user with permission “manage dashboard” - Users who have "Managed Dashboard" permission can access drag and drop dashboard.
-
No, we can not schedule dynamic dashboards for refresh. It must be done manually.
-
Dynamic dashboards in Salesforce displays set of metrics that we want across all levels of your organization. Enterprise Editions can use five dynamic dashboards and Unlimited edition can use ten dashboards.
-
Salesforce Dashboards are the graphical representation and Visual presentation of the data generated by a report (or multiple reports) at a certain point in time. So it’s a snapshot of data, to obtain the latest data you need to refresh them either manually or in a scheduled manner.
-
No, it is not possible to delete reports using data loaders.
-
Summary reports in salesforce are those where the data is displayed in the form of summary format. Sorting, sum-total of data can be available in this report.
-
Child records are not deleted.
-
When master Record is deleted, it’s detail records are also deleted.
-
Yes, It is possible to create Master-Detail Relationship on existing record. First we have to create Look-Up relationship to a record then convert it to master-Detail Relationship.
-
In salesforce, Junction Object are the part of the objects which joins one object to another. These are specially used to join many objects in Many to Many relationships.
-
We create Master-Detail Relationship using Junction Object in Salesforce.
Child record must have a associated parent.
Cascade record-level security.
Cascade record deletion.
Roll-up Summary fields can be established.
Standard objects can not be a detail object.
Standard Objects can be a Master object
Maximum 2 Master-Detail Relationships can be created to a Object.
Records can be re parented. -
No parent is required.
Relationship is optional.
No impact on Security.
Roll-Up summary fields cannot be available. -
No, we can create sharing rules for details objects because they don’t have owner field.
Sharing rules are used by administrators to automatically grant users within a given group or role access to records owned by a specific group of users. … All implicit sharing added by Force.com managed to share cannot be altered directly using the Salesforce user interface, SOAP API, or Apex.
-
No, sharing rules cannot restrict data access.
Sharing rules are used by administrators to automatically grant users within a given group or role access to records owned by a specific group of users. … All implicitsharing added by Force.com managed sharing cannot be altered directly using the Salesforce user interface, SOAP API, or Apex.
-
Yes, Role Hierarchy settings make the managers and subordinates to edit, and view the records. The users in the Hierarchy can be able to view, edit and report all the data shared.
To create roles in salesforce go to setup=>Administer=>Manage Users=> Roles.
-
Governor Limits in Salesforce.com are the run time limits enforced by the apex runtime engine to write scalable and efficient code.
Apex code runs as part of atomic transactions. Governor execution limits ensure the efficient use of resources on the Lightning Platform multitenant platform. Most of the governor limits are per transaction, and some aren’t, such as 24-hour limits. -
Salesforce uses role hierarchy to automatically to grant access to users by default. We can not edit Grant Access using Hierarchies for standard objects and can edit Grant Access using Hierarchies check box for Standard objects.
-
Login hours are set in an organization to restrict the user’s who tries to login before or after login hours.
To set login hours in an organization go to Setup=>Administration=>Manage users=>Profiles.IP ranges are used to restrict any login attempt is done from unknown IP addresses. Usually organizations maintain login IP ranges.
To set Login IP ranges in salesforce go to Setup=>Administration Setup=>Manage Users=> Profiles. -
No.
-
Lightning is the collection of tools and technologies behind a significant upgrade to the Salesforce platform. Lightning includes:
Experience: A set of modern user interfaces optimized for speed. This includes the Lightning Experience, Salesforce1 Mobile app and template-based communities.
Lightning Component Framework: A JavaScript framework and set of standard components that allow you to build reusable components to customize the Lightning Experience, Salesforce1 Mobile app and template-based communities and build your own standalone apps.
Visual Building Tools: Drag-and-drop technologies for fast and easy app building & customization’s. Use the Lightning App Builder to customize the Lightning Experience and Salesforce1 Mobile app. Use the Community Builder to customize template-based communities.
Lightning Exchange: A section of the AppExchange where you can find 70+ partner components to jump-start your development.
Lightning Design System: Style guides and modern enterprise UX best practices to build pixel perfect apps that match the look and feel of the Lightning Experience and Salesforce1 Mobile app. -
FlexiPage
Represents the metadata associated with a Lightning page. A Lightning page represents a customizable screen made up of regions containing Lightning components.
A Lightning page region can contain upto 25 components.Lightning pages are referred as FlexiPages in API and referred as Lightning pages elsewhere in SFDC documentation
-
The framework enables you to control access to your applications, attributes, components, events, interfaces, and methods via the access system attribute. The access system attribute indicates whether the resource can be used outside of its own namespace.
You can specify these values for the access system attribute.Private: Available within the component, app, interface, event, or method and can’t be referenced outside the resource. This value can only be used for or .Marking an attribute as private makes it easier to refactor the attribute in the future as the attribute can only be used within the resource.
Accessing a private attribute returns undefined unless you reference it from the component in which it’s declared. You can’t access a private attribute from a sub-component that extends the component containing the private attribute.Public: Available within your org only. This is the default access value.
Global: Available in all orgs.