1. System Preset Fields
Each business object in ShareCRM has system preset fields, these fields cannot be deleted, but some of them can be modified and hidden. For example: fields such as account status and highseas under the account object.
- Field Name: cannot be modified.
- Required: that is, whether the current field is required when creating a new business record.
- Hide: If hidden, this field will not be visible when creating a new business record.
- Option Settings: In case of a selection type field, you can modify the option value. For example, in the "Reason of Lost Order" in the business opportunity, you can configure the reason for loss of order suitable for your company, such as "order lost by competitors", "customer demand not met", etc.
2. Custom Fields
The system preset fields cannot fully meet the business needs of the enterprise, and you can add custom fields for each business object.
2.1 Supported Field Types
Currently supports 32 field types and 3 business components. The applicable conditions for each type of field or business component are as follows:
| Preset Basic Fields: responsible person, belonging department, responsible department, creator, creation time, last modification person, last modification time, life status, deletion mark |
| Preset Interconnection Fields: external personnel, external related teams, external enterprise accounts |
| Supports 35 field types |
| Single-line Text: support scan code to add, manual input |
| Multiline Text |
| Rich Text: support graphic and text mixed arrangement |
| Single-select: support field dependencies |
| Multi-select |
| Number: support default value |
| Amount: support default value , mask |
| Date |
| Time |
| Date & Time |
| Mobile: support default value, send verification code (only customer object) |
| Image: 20 image fields can be set for an object, and watermark is supported |
| Attachment: One object can set 50 attachment fields |
| Large Attachment: One object can set 1 large attachment field |
| Mailbox: support default value, mask |
| Website: support default |
| Boolean: yes, no, editable option name, can be used in calculation formulas |
| Percentage: supports the default value |
| Location: optional range |
| Personnel: optional range |
| Personnel (Multi-select): optional range |
| External Personnel |
| Department: optional range |
| Department (Multi-select): optional range |
| Reference Field: An object can set 20 reference fields. Fields on the lookup associated object, master object can be referenced. Filtering is not supported when referencing global variables (current date, current time) or fields under the person object. |
| Find Associations: up to 20 objects, resource packs can be purchased, support default value data Optional range: manual setting, custom function setting complex rules |
| Find Associations (Multi-select) |
| Main-sub Field: It is used in the scenario where the master and sub-detail data are created at the same time. The function authority and data authority of the slave object follow the master object, and the slave object does not have separate invalidation, restoration, locking, and unlocking functions. Only objects without historical data can set the master-slave field. An object can only create one master-detail field. A master object can have up to 5 slave objects. the |
| Auto-increment Number: automatically generated when saving data, and the new page is not displayed. Prefix and suffix support inserting year, month, day variables and radio fields under this object & person object. You can set recalculation rules by year, year, month, year, month, and day. Support custom coding rules with custom functions (710) |
| Calculation Fields: 20 calculated fields can be set for an object, and filtering is not supported when global variables (current date, current time) or fields under the person object are referenced. All historical data will be automatically recalculated after the value of the referenced field changes |
| Statistics Fields: 20 statistical fields can be set for an object, supporting statistical range |
| Signature Fields: a field that supports entering the signature information of the person |
| Payment Component: You can complete business collection by defining this field, and collect money to the specified account. , an object can set 1 payment component |
| Sign-in Component: users can perform sign-in/sign-out, and the background can set whether to enable sign-out according to requirements, and one object can be set with 1 sign-in component |
| Region Location: used to create positioning information, which can display location information on the map. One object can be set with one regional positioning field, which can trigger UI events |
Notes:
- After the preset object field is deleted, all generated data will also be deleted and cannot be restored;
- After the preset object field is modified, the second natural day will be synchronized to the report.
3. Dependency
3.1 Add Dependency
Dependency refers to the front and back dependencies between fields in the same business object. The optional value of a subfield depends on the value of the parent field, which is similar to the cascading relationship of "country, province, city", but the difference is that in the dependency relationship, A certain option value of the subfield can be linked with multiple options in the parent field, which is mostly used for multi-level classification. For example, if the parent field has "account classification", the options include "corporate account" and "personal account", and the subfield is "account level", and the options include "VIP account", "important account" and "general account". When setting dependencies, you can assign three sub-values to "corporate account": "VIP account", "important account" and "general account", and two sub-values "VIP account" and "general account" to "personal account". item. When using, you can only select "Account Type" before selecting "Account Level". When selecting "corporate account", there are three options for account type; when selecting "personal account", there are only two options for account type.
You can also create multiple dependencies through dependencies to form multi-level dependencies, that is, when creating a second dependency, the parent field selects the child field of a dependency, and so on, up to 10 levels of dependencies can be formed.
- Business restrictions: the parent field can only be a single-choice field, and the child field can be a single-choice field or a multi-choice field. Up to 10 levels of dependencies can be set
- The parent field can only be a single-choice field, and the child field can be a single-choice field and a multi-choice field.
- Up to 10 levels of dependencies can be set
3.2 Remove Dependency
That is, the dependency relationship is lifted, and the two radio fields are no longer dependent on each other, and can be selected and used independently.