Difference between revisions of "About Objects in Lookup Fields"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
::*Users associated with records in the object become ''clickable'' | ::*Users associated with records in the object become ''clickable'' | ||
::*When clicked, the associated User record is opened | ::*When clicked, the associated User record is opened | ||
:*;[[Teams]]: | :*;[[Teams]]: | ||
::* A lookup field that targets the Team object can be clicked | ::* A lookup field that targets the Team object can be clicked | ||
::* When clicked, the corresponding Team record is opened | ::* When clicked, the corresponding Team record is opened | ||
:*;[[Email Templates|Templates]]: | :*;[[Email Templates|Templates]]: | ||
::*Use this option when using the <tt>[[sendEmailUsingTemplate]]</tt> call in the [[Java API]]. This allows the Template [[Record Id]] to be fetched programmatically | ::*Use this option when using the <tt>[[sendEmailUsingTemplate]]</tt> call in the [[Java API]]. This allows the Template [[Record Id]] to be fetched programmatically, which saves time (instead of hardcoding record id). | ||
Latest revision as of 21:00, 25 June 2013
Any Object can be the target of a Lookup, as well as:
-
- Users associated with records in the object become clickable
- When clicked, the associated User record is opened
- A lookup field that targets the Team object can be clicked
- When clicked, the corresponding Team record is opened
- Use this option when using the sendEmailUsingTemplate call in the Java API. This allows the Template Record Id to be fetched programmatically, which saves time (instead of hardcoding record id).