Lines 228-234
If an input record has more than one attribute, the fields should either be ente
Link Here
|
228 |
<ul><li>Example 3: "STARTDATE:January 1, 2010","TRACK:Day"</li></ul> |
228 |
<ul><li>Example 3: "STARTDATE:January 1, 2010","TRACK:Day"</li></ul> |
229 |
The second syntax would be required if the data might have a comma in it, like a date string.</li> |
229 |
The second syntax would be required if the data might have a comma in it, like a date string.</li> |
230 |
[% END %] |
230 |
[% END %] |
231 |
<li><b>Required fields: </b>The fields 'branchcode' and 'categorycode' are required and must match valid entries in your database.</li> |
231 |
<li><b>Required fields: </b>The fields 'cardnumber', 'surname', 'branchcode', and 'categorycode' are required. Branchcode and categorycode must match valid entries in your database.</li> |
232 |
<li><b>Password: </b>Values for the field 'password' should be stored in plaintext, and will be converted to a Bcrypt hash (if your passwords are already encrypted, talk to your system administrator about options).</li> |
232 |
<li><b>Password: </b>Values for the field 'password' should be stored in plaintext, and will be converted to a Bcrypt hash (if your passwords are already encrypted, talk to your system administrator about options).</li> |
233 |
<li><b>Date formats: </b> Date values should match your system preference, and must be zero-padded. |
233 |
<li><b>Date formats: </b> Date values should match your system preference, and must be zero-padded. |
234 |
<ul><li>Example: '01/02/2008'</li></ul> |
234 |
<ul><li>Example: '01/02/2008'</li></ul> |
235 |
- |
|
|