Changes

Working with Level 2 – Activities

151 bytes added, 21:19, 13 July 2009
no edit summary
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 Standard Field|built-in fields]] s 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 [[Standard Field]]s that related to activities and use [[Custom Field|custom fields]] for the rest of the [[Entity|entity]].
==Steps to Activate Level 2 items==
* Choose the standard fields using the '''Application Configuration''' page.
* Create the [[Custom Field|custom fields]] for Level 2 using either the '''Application Configuration''' page OR the '''Application Settings''' page.
* Define Level 2 '''[[Creating Level 2 Types|Types]] ''' using the '''Application Settings''' page. (The term ''Type'' at Level 2 and Level 3 is the equivalent of ''Template'' at Level 1)
* Define the Level 2 [[Statuses]] using the '''Application Settings''' page.
* Define the [[List View]] for Level 2 items.
 
==See Also==
* [[Configuring the Level 2 Entity]]
* [[Level 2 Types]]
* [[Restricting Level 2 Types to Specific Level 1 Templates]]
[[Category:Universal Tracking Application]]
0
edits