Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you about the permissions of Apex classes and access modifiers. The article is rich in content and analyzed and described from a professional point of view. I hope you can get something after reading this article.

The definition of the Apex class is the same as Java and is identified by the class keyword.

1) every Top class must have a modifier, otherwise it cannot be compiled.

(Compile Error for Test.cls: Top-level type must have public or global visibility at line 1 column 7)

2) the inner class can not write modifiers (private).

3) optional virtual. Abstract indicates that the current class is abstract.

4) like Java, multiple interfaces can be implemented through the implements keyword, and the parent class can be inherited only through extends

5) the class name cannot be duplicated with the keywords of SF, such as standard object, etc. (a previous colleague encountered a class name with the same name as the standard object, so that the report field does not exist when using the standard object)

Class access modifier

1 private cannot be used in the Top class, can only be used in the inner class, and cannot be accessed externally

When new Test calls my (), it executes correctly, when the new Test.InnerClazz Times InnerClazz does not exist

Public class Test {private class InnerClazz {} public void my () {InnerClazz iclass = new InnerClazz (); System.debug (iclass);}}

2 public can be used in the current application or in the current namespace

3 global arbitrary access, webService must be global, if a method or inner class is global, then Top class must be global

4 with sharing/without sharing current class permission mode

Class definition form private | public | global [virtual | abstract | with sharing | without sharing] class ClassName [implements InterfaceNameList] [extends ClassName] {/ / The body of the class} member variable definition form [public | private | protected | global] [final] [static] data_type variable_name [= value]

Type and variable name is required, access modifier is optional, not written as private final and static modifier variable is constant the same as Java

Types: basic types and custom types

Apex attribute: get/set

Public Integer prop {get {return prop;} set {prop = value;}} / / when only get is written, the value public Integer prop {get; set;} cannot be given in this class as a member method [public | private | protected | global] [override] [static] data_type method_name (input parameters) {/ / The body of the method}

1) optionally, the access modifier is not written as private

2) override implements the abstract method of the parent class

3) static static methods, class methods, called by the class

4) value types (basic data types such as: Integer,String) and reference types

Permissions (1)

1) the current with sharing class follows SF's sharing model and finds only authorized data in the result set executed by the SQL statement.

2) without sharing executes according to SQL statement

Test 1: when the control class is without sharing object, all permissions are none, through the VF page, whether people without permission can create

After the actual test, it can be created, and the owner and creator are the current logins, but the current record cannot be viewed through the standard interface (the assignment is the value given by the program).

Test 2: when querying the background data is displayed on the VF page, when querying the log, the display obtains the data, and when the foreground passes through the loop, the blank is printed. Unable to view

When the object is checked, the results can be printed, but the fields whose field security is not visible are still not visible.

Test 3: delete a record and the results show that it can be deleted.

Test 4: modify a record and the results show that it can be deleted. (assignment is given by the program)

When using without sharing, objects can be created and the results can be queried, but they cannot be displayed on the VF page. When you have permission to view objects, you can see the standard fields. When the field visibility is not checked, it is still not visible.

Modification and deletion work properly. (there are also situations that need to be tested: permissions for inner classes, permissions when with sharing calls methods of without sharing class, when with sharing extends without sharing permissions, when without sharing extends with sharing)

With sharing,without sharing is usually used to solve special cases. For example, recently, when you create a registration under a marketing activity, the registration fee is updated to the marketing activity through the trigger summary, and the sales do not have the editing authority for the marketing activity, but the summary requires editing permission.

This is what the permissions of the Apex class and access modifier shared by the editor are. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.