Asset Actor

An Asset Actor models general business data. It serves as a template for representing data that don’t fit special actors like Order and Payment. Asset is also different from Ticket because it holds data for the long-term. In contrast, a Ticket is valid until it is completed.

You can define an Asset to model customers, vendors, suppliers, products, buyer personas, and other general data.

Asset actors are also dynamic because they support custom Types, Items, and Relations. These allow you to model data more closely and accurately to represent sub-types and existing links with other resources. For instance, a Customer Asset can include items such as one-off and repeat customers, and relations with Order and Payment.

Core Concepts of Asset Actors

Assets stand out because they:

• Support custom types: Create custom Asset Types with Items and Relations to closely model general business data.
• Hold general data: Model non-specialized actor classes not found on Hantera, such as, Customer and Vendor data.

Quick Start for Asset Actors

Follow these steps to create and work with new Assets.

1. Define an Asset type, for instance Customer, Vendor

2. Create an instance of an Asset

3. Modify instances of Asset types

Asset Rule Hooks

Rule Hooks for Assets are:

Name	Discount	Rule	Reactor
OnAssetBeforeCreated
OnAssetBeforeDeleted
OnAssetCommands
OnAssetCreated
OnAssetDeleted