Commit | Line | Data |
---|---|---|
6a488035 TO |
1 | {* |
2 | +--------------------------------------------------------------------+ | |
2c4c49ca | 3 | | CiviCRM version 4.7 | |
6a488035 | 4 | +--------------------------------------------------------------------+ |
e7112fa7 | 5 | | Copyright CiviCRM LLC (c) 2004-2015 | |
6a488035 TO |
6 | +--------------------------------------------------------------------+ |
7 | | This file is a part of CiviCRM. | | |
8 | | | | |
9 | | CiviCRM is free software; you can copy, modify, and distribute it | | |
10 | | under the terms of the GNU Affero General Public License | | |
11 | | Version 3, 19 November 2007 and the CiviCRM Licensing Exception. | | |
12 | | | | |
13 | | CiviCRM is distributed in the hope that it will be useful, but | | |
14 | | WITHOUT ANY WARRANTY; without even the implied warranty of | | |
15 | | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | | |
16 | | See the GNU Affero General Public License for more details. | | |
17 | | | | |
18 | | You should have received a copy of the GNU Affero General Public | | |
19 | | License and the CiviCRM Licensing Exception along | | |
20 | | with this program; if not, contact CiviCRM LLC | | |
21 | | at info[AT]civicrm[DOT]org. If you have questions about the | | |
22 | | GNU Affero General Public License or the licensing of CiviCRM, | | |
23 | | see the CiviCRM license FAQ at http://civicrm.org/licensing | | |
24 | +--------------------------------------------------------------------+ | |
25 | *} | |
26 | {htxt id="id-group_intro-title"} | |
27 | {ts}Custom Fields{/ts} | |
28 | {/htxt} | |
29 | {htxt id="id-group_intro"} | |
30 | {ts}Use this form to set the title, the type of record the fields will be used for, and set-level help. You will then be able to add any number of fields to the set.{/ts} {docURL page="user/organising-your-data/custom-fields"} | |
31 | {/htxt} | |
32 | ||
33 | {htxt id="id-title-title"} | |
34 | {ts}Title{/ts} | |
35 | {/htxt} | |
36 | {htxt id="id-title"} | |
37 | {ts}For 'inline' display custom sets, this title will appear as the fieldset legend. If you choose the 'tab' display style (which is available for Contact record custom fields), the title will be used for the navigation tab.{/ts} | |
38 | {/htxt} | |
39 | ||
40 | {htxt id="id-display_style-title"} | |
41 | {ts}Display Style{/ts} | |
42 | {/htxt} | |
43 | {htxt id="id-display_style"} | |
b05a0fb6 | 44 | {ts}Select 'Inline' to include this set of fields in the main contact Add/Edit form and Contact Summary screens. Select 'Tab' or 'Tab with Table' to create a separate navigation tab for display and editing these values (generally for less frequently accessed and/or larger sets of fields). 'Tab with Table' is recommended for customs data sets which allow multiple records.{/ts} |
6a488035 TO |
45 | <p class="font-italic">{ts}NOTE: This setting applies only to custom sets used for Contact records (e.g. Individuals, Households, Organizations, or ALL contact types).{/ts}</p> |
46 | {/htxt} | |
47 | ||
48 | {htxt id="id-extends-title"} | |
49 | {ts}Entity Type{/ts} | |
50 | {/htxt} | |
51 | {htxt id="id-extends"} | |
52 | {ts}Select the type of record that this set of custom fields is applicable for. You can configure custom data for a specific type of contact (e.g. Individuals but NOT Organizations), ANY type of contact, or other record types such as activities, contributions, memberships and event participants.{/ts} | |
53 | <p>{ts}EXAMPLE: If you are using CiviEvent, and you want to collect information from people registering for your events, select "Participants". If the information is specific to one type of participant (e.g. event volunteers), select "Participants (role)" and then select the role (e.g. 'Volunteer').{/ts}</p> | |
54 | <p>{ts}If your site uses Contact Subtypes, you can assign this set of custom fields to a specific subtype (e.g. 'Student'), OR you can select '- Any -' which makes the fields available to contacts of the parent type (e.g. 'Individual') as well as to any subtypes.{/ts}</p> | |
55 | {/htxt} | |
56 | ||
61dcf61b | 57 | {capture assign=importMultipleURL}{crmURL p="civicrm/import/custom" q="reset=1"}{/capture} |
6a488035 | 58 | {htxt id=id-is_multiple-title"} |
e26f4e37 | 59 | {ts}Allow Multiple Records{/ts} |
6a488035 TO |
60 | {/htxt} |
61 | {htxt id=id-is_multiple"} | |
62 | <p>{ts}Checking this box allows you to enter multiple sets of values for a given contact.{/ts}</p> | |
63 | <p>{ts}<strong>EXAMPLE:</strong> When creating a set of custom fields used to collect <strong>Employment History</strong> - you might have fields for Job Title, Start Date, End Date, and Reason for Leaving. Checking the "multiple records" box allows you to collect information for multiple jobs.{/ts}</p> | |
64 | <p>{ts}You can also set the maximum number of records which can be recorded per contact. Using the previous example, you might only want data for the three most recent jobs.{/ts}</p> | |
61dcf61b | 65 | <p>{ts 1=$importMultipleURL}Use the <a href="%1">Multi-value Custom Data Import tool</a> to import data into multiple record custom fields (contact records must already exist).{/ts}</p> |
6a488035 TO |
66 | <p> |
67 | {ts}CAUTION: The following features are NOT available for custom fields in 'multiple record' custom set:{/ts} | |
61dcf61b DG |
68 | <ul> |
69 | <li>{ts}They can not be Exported{/ts}</li> | |
70 | <li>{ts}If they are included in a report as a display column, only the first set of values are shown.{/ts}</li> | |
71 | </ul> | |
72 | </p> | |
6a488035 TO |
73 | {/htxt} |
74 | ||
75 | {htxt id=id-max_multiple-title"} | |
76 | {ts}Maximum Records{/ts} | |
77 | {/htxt} | |
78 | {htxt id=id-max_multiple"} | |
79 | {ts}If you want to set a specific limit on the maximum number of records, enter that number. Otherwise leave this field blank.{/ts} | |
80 | {/htxt} | |
81 | ||
82 | {htxt id="id-weight-title"} | |
83 | {ts}Weight{/ts} | |
84 | {/htxt} | |
85 | {htxt id="id-weight"} | |
86 | {ts}Weight controls the order in which custom field sets are presented when there are more than one. Enter a positive or negative integer - lower numbers are displayed ahead of higher numbers.{/ts} | |
87 | {/htxt} | |
88 | ||
89 | {htxt id="id-collapse-title"} | |
90 | {ts}Collapsed on Page{/ts} | |
91 | {/htxt} | |
92 | {htxt id="id-collapse"} | |
93 | {ts}Check this box if you want only the title for this fieldset to be displayed when the page is initially loaded (fields are hidden).{/ts} | |
94 | {/htxt} | |
95 | ||
96 | {htxt id="id-collapse-adv-title"} | |
97 | {ts}Collapsed on Search{/ts} | |
98 | {/htxt} | |
99 | {htxt id="id-collapse-adv"} | |
100 | {ts}Check this box if you want only the title for this fieldset to be displayed when the page is initially loaded (fields are hidden) on advanced search.{/ts} | |
101 | {/htxt} | |
102 | ||
103 | {htxt id="id-help_pre-title"} | |
104 | {ts}Pre Help{/ts} | |
105 | {/htxt} | |
106 | {htxt id="id-help_pre"} | |
107 | {ts}Explanatory text displayed at the beginning of this sets of fields.{/ts} | |
108 | {/htxt} | |
109 | ||
110 | {htxt id="id-help_post-title"} | |
111 | {ts}Post Help{/ts} | |
112 | {/htxt} | |
113 | {htxt id="id-help_post"} | |
114 | {ts}Explanatory text displayed below this set of fields.{/ts} | |
115 | {/htxt} |