Difference between revisions of "About Objects in Lookup Fields"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 6: | Line 6: | ||
::*Documents associated with records in the object become ''clickable'' | ::*Documents associated with records in the object become ''clickable'' | ||
::*When clicked, the associated Document record is opened | ::*When clicked, the associated Document record is opened | ||
:* [[Teams]] | |||
::* A lookup field that targets the Team object can be clicked | |||
::* 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 for [[Campaigns]], which saves time (instead of hardcoding record id). | ::*Use this option when using the <tt>[[sendEmailUsingTemplate]]</tt> call in the [[Java API]]. This allows the Template [[Record Id]] to be fetched programmatically for [[Campaigns]], which saves time (instead of hardcoding record id). | ||
Revision as of 23:55, 28 November 2012
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
- Documents associated with records in the object become clickable
- When clicked, the associated Document 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 for Campaigns, which saves time (instead of hardcoding record id).