Asset: Difference between revisions
(Created page with "'''Assets''' are the mechanism through which expressions refer to resources within ContactsLaw. Each asset has a name (which distinguishes it from other assets) and a type (which determines the data that can be accessed through it). Assets are also hierarchical, e.g. an address asset belongs to a particular contact asset. This avoids the need to separately specify how to obtain the address. Relationships between assets may be mandatory (e.g. betwe...") |
No edit summary |
||
Line 1: | Line 1: | ||
'''Assets''' are the mechanism through which [[Expression|expressions]] refer to resources within [[ContactsLaw]]. Each asset has a name (which distinguishes it from other assets) and a type (which determines the data that can be accessed through it). | '''Assets''' are the mechanism through which [[Expression|expressions]] refer to resources within [[ContactsLaw]]. They can be used in [[Document Template|document templates]], [[Workflow:Process|processes]], description specifications and many other areas of the software. Each asset has a name (which distinguishes it from other assets) and a type (which determines the data that can be accessed through it). | ||
Assets are also hierarchical, e.g. an address asset belongs to a particular [[contact]] asset. This avoids the need to separately specify how to obtain the address. Relationships between assets may be mandatory (e.g. between addresses and contacts) or optional (e.g. between contacts and matters). | Assets are also hierarchical, e.g. an address asset belongs to a particular [[contact]] asset. This avoids the need to separately specify how to obtain the address. Relationships between assets may be mandatory (e.g. between addresses and contacts) or optional (e.g. between contacts and matters). | ||
Assets can resolve to multiple resources; for example, if a contact asset maps to a role on a [[matter]], and there are 3 contacts in that role, then the asset will be resolved 3 times. Whenever an expression refers to an asset, it may yield zero, one or multiple values (functions are provided to deal with this). Mechanisms such as repetition blocks (in | Assets can resolve to multiple resources; for example, if a contact asset maps to a role on a [[matter]], and there are 3 contacts in that role, then the asset will be resolved 3 times. Whenever an expression refers to an asset, it may yield zero, one or multiple values (functions are provided to deal with this). Mechanisms such as repetition blocks (in document templates) can be used to manage complex hierarchies of assets that resolve to multiple resources. | ||
== Types == | |||
Types of assets include: | |||
* [[Contact]] | |||
** Address | |||
** Communication | |||
** [[Member]] | |||
** [[Business]] | |||
* [[Matter]] | |||
** [[Invoice]] | |||
*** Invoice Item | |||
** [[Time Record]] | |||
*** Time Record Line Item | |||
* [[Document]] | |||
** Image | |||
** Fragment | |||
* [[Transaction]] | |||
** Transaction Line Item | |||
** [[Account]] | |||
* [[Workgroup]] | |||
* [[Custom Field]] |
Revision as of 12:50, 3 May 2024
Assets are the mechanism through which expressions refer to resources within ContactsLaw. They can be used in document templates, processes, description specifications and many other areas of the software. Each asset has a name (which distinguishes it from other assets) and a type (which determines the data that can be accessed through it).
Assets are also hierarchical, e.g. an address asset belongs to a particular contact asset. This avoids the need to separately specify how to obtain the address. Relationships between assets may be mandatory (e.g. between addresses and contacts) or optional (e.g. between contacts and matters).
Assets can resolve to multiple resources; for example, if a contact asset maps to a role on a matter, and there are 3 contacts in that role, then the asset will be resolved 3 times. Whenever an expression refers to an asset, it may yield zero, one or multiple values (functions are provided to deal with this). Mechanisms such as repetition blocks (in document templates) can be used to manage complex hierarchies of assets that resolve to multiple resources.
Types
Types of assets include:
- Contact
- Matter
- Invoice
- Invoice Item
- Time Record
- Time Record Line Item
- Invoice
- Document
- Image
- Fragment
- Transaction
- Transaction Line Item
- Account
- Workgroup
- Custom Field