Difference between revisions of "System Object Types"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 24: | Line 24: | ||
|- | |- | ||
|User Team||<tt>USER_TEAM</tt> || [[REST API:userTeam Resource|REST API:userTeam Resource]] || none | |User Team||<tt>USER_TEAM</tt> || [[REST API:userTeam Resource|REST API:userTeam Resource]] || none | ||
|} | |||
These objects are related to records in other objects. The objects are not visible as independent entities in the UI. The records they contain can be see only by viewing the records they are related to. However, they can be accessed programmatically: | |||
:{| border="1" cellpadding="5" cellspacing="0" | |||
!System Object | |||
!Object Type Identifier | |||
!Reference Information | |||
|- | |||
| Attachments | |||
| attachments | |||
| | |||
|- | |||
| Notes | |||
| notes | |||
| | |||
|- | |||
| Tasks | |||
| tasks | |||
| | |||
|} | |} |
Revision as of 00:52, 24 September 2013
System Objects are listed here, showing the names that appear in the UI, along with the object-type identifiers used in the APIs.
System Object
(As shown in the Platform UI)Object Type Identifier
Reference Information Customization Capabilities Case CASE REST API:record Resource Virtually unlimited ability to Customize Objects Role ROLE REST API:role Resource none User USER REST API:user Resource - Add Fields
- Modify labels of existing fields
- Use a restricted set of Event Rules and Scheduled Rules
Team TEAM REST API:team Resource - Use a restricted set of Event Rules and Scheduled Rules
User Team USER_TEAM REST API:userTeam Resource none
These objects are related to records in other objects. The objects are not visible as independent entities in the UI. The records they contain can be see only by viewing the records they are related to. However, they can be accessed programmatically:
System Object Object Type Identifier Reference Information Attachments attachments Notes notes Tasks tasks