Difference between revisions of "Working with Level 2 – Activities"
From SmartWiki
Julia Decker (talk | contribs) |
Julia Decker (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | You can sometimes build a useful tracking application by just using the [[Level 1 Entity]]. But when you need to track “transactions” of some kind associated with the Level 1 item, you will then need to create a two level UTA. | + | You can sometimes build a useful tracking [[Application|application]] by just using the [[Level 1 Entity]]. But when you need to track “transactions” of some kind associated with the Level 1 item, you will then need to create a two level [[UTA]]. |
* When you examine the [[Built-in Field|built-in fields]] for the Level 2 (and Level 3) [[Entity|entities]] you will see they closely resemble activity type transactions with fields such as start date, end date, start time, end time, etc. And generally a lot of the Level 2 transaction types do have these types of activity based characteristics. | * When you examine the [[Built-in Field|built-in fields]] for the Level 2 (and Level 3) [[Entity|entities]] you will see they closely resemble activity type transactions with fields such as start date, end date, start time, end time, etc. And generally a lot of the Level 2 transaction types do have these types of activity based characteristics. | ||
* Sometimes the Level 2 transaction will not require any activity type fields. In that situation simply don’t use any of the built-in fields that related to activities and use [[Custom Field|custom fields]] for the rest of the [[Entity|entity]]. | * Sometimes the Level 2 transaction will not require any activity type fields. In that situation simply don’t use any of the built-in fields that related to activities and use [[Custom Field|custom fields]] for the rest of the [[Entity|entity]]. | ||
Revision as of 09:56, 1 November 2007
You can sometimes build a useful tracking application by just using the Level 1 Entity. But when you need to track “transactions” of some kind associated with the Level 1 item, you will then need to create a two level UTA.
- When you examine the built-in fields for the Level 2 (and Level 3) entities you will see they closely resemble activity type transactions with fields such as start date, end date, start time, end time, etc. And generally a lot of the Level 2 transaction types do have these types of activity based characteristics.
- Sometimes the Level 2 transaction will not require any activity type fields. In that situation simply don’t use any of the built-in fields that related to activities and use custom fields for the rest of the entity.
Steps to Activate Level 2 items
The steps to activate the Level 2 Entity are similar to the Level 1 Entity.
- Choose the standard fields using the Application Configuration page.
- Create the custom fields for Level 2 using either the Application Configuration page OR the Application Settings page.
- Define the “Types” of Level 2 entities using the Application Settings page. Instead of “template’ the word “type” is used for Level 2 and Level 3.
- Define the Level 2 statuses using the Application Settings page.
- Define the List view for Level 2 items.
