| 312 | |
| 313 | === Manipulating Profile Attributes === |
| 314 | |
| 315 | Administrators may add attributes to user profiles or remove them. That is to say, add a schema (including format constraints and descriptions), not set a value for a user. |
| 316 | |
| 317 | Creating an attribute: |
| 318 | |
| 319 | * '''Service:''' Users |
| 320 | * '''Operation:''' createUserAttribute |
| 321 | * '''Input Parameters:''' |
| 322 | * Name - the attribute name |
| 323 | * Type - the type (STRING, INT, FLOAT, OPAQUE) |
| 324 | * Optional - a boolean, true if this attribute is optional |
| 325 | * Access - an integer the user's ability to modify (READ_WRITE, READ_ONLY, WRITE_ONLY, NO_ACCESS) |
| 326 | * Description - natural language description of the field (optional) |
| 327 | * Format - a regular expression describing the format (optional) |
| 328 | * Formatdescription - a natural language explanation of the format (optional) |
| 329 | * Def - default value of the attribute (will be set for all users) |
| 330 | * '''Return Values:''' |
| 331 | * a boolean, true if the attribute was created |
| 332 | |
| 333 | And removing an attribute: |
| 334 | |
| 335 | * '''Service:''' Users |
| 336 | * '''Operation:''' removeUserAttribute |
| 337 | * '''Input Parameters:''' |
| 338 | * Name - the attribute name |
| 339 | * '''Return Values:''' |
| 340 | * a boolean, true if the attribute was removed |
| 341 | |
| 342 | |