Posts Tagged ‘flex asset model’


In this article, we will see a few important tables that are created in the database, when a Flex Family is created in Fatwire.

The Flex Asset model, as the name itself suggests, is a FLEXIBLE Asset model. The Database design of the Flex Asset Model is very complex, as compared to the Basic Asset model. Each asset type in a flex family will have several database tables.

Following are few Important Tables that are created in Database, when a Flex Family is created.

A Table with the name of the asset itself:

The primary storage table for the flex asset type. For example, the primary storage table for the sample asset type named MyFlex is MyFlex.

The  _Mungo Tables:

The flex asset and flex parent asset types have an AssetType_Mungo table (Example, MyFlex_Mungo), where AssetType is the name of the flex asset type. Its purpose is to store the attribute values assigned to an asset when an asset of this type is created. Each attribute value has a separate row. For example, if we create a Flex Asset type called MyFlex (MyFlex_C) , then the table MyFlex_Mungo holds the attribute values for MyFlex assets.

The MungoBlobs Table:

There is one single table called MungoBlobs, which holds all the values for all flex attributes of type BLOB. This table is used for all the flex attribute types in your system. Each attribute value has a separate row in the table.

The _AMap Tables:

Flex asset and flex parent asset types have an AssetType_AMap table (Example, MyFlex_AMap). Its purpose is to map the asset to the attributes it inherits from its parents.

There are several other tables that store data about the relationships between the flex assets as well as other information.

For more information regarding these tables, please refer to Fatwire/Oracle WebCenter Sites Developer and Administrator guides.


When to Use the Flex Asset Model in Fatwire?

Flex assets means FLEXIBLE ASSETS. Meaning, that we can add fields at any moment to the asset. You can update your site at any time, adding new fields, without disturbing the existing content.

FLEX ASSET MODEL has been the favorite model for the developers who concentrate on developing WEB EXPERIENCE MANAGEMENT applications. The Flex model helps in achieving the website’s goal of targeting the audience/visitors, and hence improving the overall business by the websites. The Flex Asset Model is the choice of developers, when the data has the following characteristics:

  • MANY ATTRIBUTES:  The assets have very large number of attributes, like some hundreds of attributes.
  • NEEDS HIERARCHY:  The assets need to inherit attributes from their parents.
  • UNPREDICTED ATTRIBUTES: This means that we know that we cannot predict what attributes might be necessary in the future.
  • NAVIGATION: Visitors browse your site by navigating through “drill-down” searches that are based on the attribute values of your data.
  • ENGAGE: You want to use Engage.

If implemented correctly, the Flex asset model yields major benefits for the business through websites.

But, to build a Flex asset model, a lot of complex work needs to be done. The following needs to be kept in mind, while choosing this Flex asset model.

  • COMPLEX DATABASE: The underlying database structure of flex assets is pretty complex.
  • SLOW RATE: Asset creation is slower that Basic assets.
  • SEARCH: Searching attributes requires complex code.