Extended Attribute Sets

Extended Attribute Sets are essentially <fieldset> elements. In other words, they're a set of form controls, grouped under a common name. To create an Extended Attribute Set, follow the steps outlined below.

1. From the back-end administration area of Mura, select Site Settings, click Class Extensions, and select Class Extensions.
   
2. You should be directed to the Class Extensions screen.
   
3. Select the Class Extension you wish to add an Extended Attribute Set to, from the listing of available Class Extensions.
   
4. You should be directed to the Class Extension screen. Here, you can view any available Extended Attribute Sets or Related Content Sets.
   
5. To add an Extended Attribute Set, click the Add button, then select Add Attribute Set.
   
6. You should now see the Add Attribute Set screen.
   
   • Attribute Set Name
     • The text entered here will be used as the <legend> for the generated <fieldset>.
   • Container (Tab)
     
     • You may select the tab you wish to include your Extended Attribute Set on, from the listing of available tabs. The listing will differ, depending on the Base Type you selected when creating the Class Extension itself.
     • If you select the Custom UI option, you're essentially telling Mura that you'll take care of collecting any attributes you're going to define. If you wish to add a new tab, and include a custom form for collecting the data, you may find this Gist useful: https://gist.github.com/stevewithington/f3dd405d5a188fb594a1
7. Once you've entered an Attribute Set Name, and selected your desired Container (Tab), click the Add button to create your new attribute set.
   
8. You should be directed to the Manage Extended Attribute Set screen. This is where you'll add, and manage your new attributes, or form fields.
   
9. To create a new attribute, click the Add New Attribute button.
   
10. The screen should now reveal a form to add a new attribute.
    
    • Name (No spaces)
      • Text entered here will be used as the name attribute of the form field. In addition, the text entered here is how you will reference any data entered for this attribute, as you'll see in the Displaying Extended Attributes section. It is important to use a proper naming convention, as if you were manually creating the input using HTML. Keep in mind that this form field will be included on a much larger form, and as such, you'll want to avoid using any of the bean object's attribute names so you don't run into any naming collisions. For example, you don't want to use the Name "title", since Content Beans already have an attribute labeled "title".
      • The recommended best practice is to prefix the Name with the Subtype of your class extension. For example, if your Subtype equals "Location", instead of using "title" for the Name, you might use "locationtitle" for the Name.
    • Label
      • Text entered here will be used as the <label> element.
    • Input Type
      
      • Select your desired input type from the option list.
    • Default Value
      • Optionally, enter a default value here. To include a dynamic value, you may use Mura [m] tags.
    • Tooltip
      • Optionally, enter text to be used as a tooltip.
    • Required
      • Whether the field is required. If True, Mura will use the option selected in the Validate field when the user submits the form.
    • Validate
      
      • If you desire the input to be validated before the form is submitted, select one of the following options.
        • None
          • Do not validate input.
        • Date
          • Validates data entered is a valid date. Mura will display a calendar UI widget for content managers to use when completing this form field.
        • DateTime
          • Validates data entered is a valid date and time. Mura will display a calendar and time UI widget for content managers to use when completing this form field.
        • Numeric
          • Validates data entered is an integer.
        • Email
          • Validates data entered matches standard email address formats.
        • Regex
          • Validates data entered against the JavaScript regular expression entered in the Regex field.
        • Color
          • If the Input Type is set to TextBox, and this option is selected, Mura will display a "color picker" UI widget for content managers to use when completing this form field.
        • URL
          • Validates data entered matches standard URL formats.
    • Regex
      • If Validate is set to Regex, Mura will use the JavaScript regular expression entered here to validate data entered in this form field.
    • Validation Message
      • If Required is set to True, text entered here will be displayed to content managers if the data entered in this form field does not pass validation rules.
    • Option List ("^" Delimiter)
      • This carat ("^") delimited list of "option values" will be used if Input Type is set to SelectBox, MultiSelectBox, or RadioGroup. For example, "option1^option2^option3". To include a dynamic value, you may use Mura [m] tags.
    • Option Label List (Optional, "^" Delimiter)
      • This carat ("^") delimited list of "option labels" will be used if Input Type is set to SelectBox, MultiSelectBox, or RadioGroup. For example, "Option 1^Option 2^Option 3". To include a dynamic value, you may use Mura [m] tags.
    • For Administrative Use Only?
      • If Yes, the field will not display for content editing purposes, and will be a hidden form field.
11. After you've completed the form, click the Add button to create your new attribute.
    
12. Repeat these steps to create additional attributes for the Extended Attribute Set.
13. The attributes sort order is the order in which they will be displayed to content managers. If you wish to reorder any of them, click the Reorder button.
    
14. Then, hover over the attribute you wish to move, and then click, drag, and drop to your desired location.
    
15. When finished reordering, click the Save Order button.
    

Related Content Sets

Related Content Sets allow content managers the ability to associate content to something other than the default catch-all "Related Content" field, allowing you to create fields such as Related Videos, Related Files, Related Authors, and so on. To create a Related Content Set, follow the steps outlined below.

1. From the back-end administration area of Mura, select Site Settings, click Class Extensions, and select Class Extensions.
   
2. You should be directed to the Class Extensions screen.
   
3. Select the Class Extension you wish to add a Related Content Set to, from the listing of available Class Extensions.
   
4. You should be directed to the Class Extension screen. Here, you can view any available Extended Attribute Sets and Related Content Sets.
   
5. To add a Related Content Set, click the Add button, then select Add Related Content Set.
   
6. You should be taken to the Add Related Content Set screen.
   
   • Related Content Set Name
     • Text entered here will display above the new field as the label for content managers to identify it.
   • Allow users to add only specific subtypes?
     
     • If Yes, you may select one, or more options from the available list. This will restrict the type of content that content managers are able to assign to the specific Related Content Set.
7. When finished completing the form, click the Add button.
   
8. Now, when a content manager edits content, and selects the Related Content tab, your new Related Content Set will appear. Also note that any Subtype restrictions will be displayed as well.
   

Elements Of The "config.xml.cfm" File

At the top level, a config.xml.cfm document should contain the mandatory <mura> element. There are no attributes available for this element, unless being used with a module/display object.

The following table describes available attributes, only if used with a module/display object.

Example <mura>

This attributes will only be used with a display object.

<mura name="My Display Object" contenttypes="*" iconclass="mi-book">
  ...
</mura>

Subordinate to the <mura> element is an <imagesizes> element, which may contain one or more custom image sizes, and an <extensions> element, which may contain one or more custom class extension definitions.

<mura>
    <imagesizes>
    </imagsizes>
    <extensions>
    </extensions>
</mura>

Note: Plugins have additional elements, and will be covered in the Plugin Development section.

<imagesize> is a sub-element of <imagesizes>

The following table describes the available attributes.

Example <imagesize>

<imagesize name="yourimagesizename" width="600" height="100"/>

<extension> is a sub-element of <extensions>

The following table describes the available attributes.

Example <extension>

<extension type="Page" subType="Product" hasSummary="1" hasBody="1" isActive="1">
	...
</extension>

<attributeset> is a sub-element of <extension>

An attribute set is similar to creating a <fieldset> element in HTML.

The following table describes the available attributes.

Available Container/Tab Options

Valid Container/Tab Options

The following table describes available options to use as the value for each Base Type.

Example <attributeset>

<attributeset name="Mobile Options" container="Basic" orderno="1">
    ...
</attributeset>

<attribute> is a sub-element of <attributeset>

An attribute describes a data container (form field) and its validation rules.

The following table describes required and optional attributes of the <attribute> element:

Note: To enable a color picker for a form field, set type="TextBox" and validation="Color"

Example config.xml.cfm

<?xml version="1.0" encoding="UTF-8"?>
    <mura>
        <!-- Image Sizes -->
        <imagesizes>
          <imagesize
            name="locationimage"
            width="600"
            height="400"/>
        </imagesizes>

        <!-- Class Extensions -->
        <extensions>
            <extension 
                adminonly="0" 
                availablesubtypes="Page/Location" 
                description="" 
                hasassocfile="0" 
                hasbody="0" 
                hasconfigurator="0" 
                hassummary="0" 
                iconclass="mi-map-o" 
                subtype="Locations" 
                type="Folder"/>

            <extension 
                availablesubtypes="" 
                description="" 
                hasassocfile="1" 
                hasbody="0" 
                hasconfigurator="0" 
                hassummary="1" 
                iconclass="mi-map-pin" 
                subtype="Location" 
                type="Page">

                <attributeset 
                    container="Basic" 
                    name="Location Options" 
                    orderno="1">

                    <attribute 
                        adminonly="0" 
                        defaultvalue="" 
                        hint="" 
                        label="Location Street" 
                        message="Please enter a Location Street" 
                        name="locationstreet" 
                        optionlabellist="" 
                        optionlist="" 
                        orderno="1" 
                        regex="" 
                        required="true" 
                        type="TextBox" 
                        validation=""/>

                    <attribute 
                        adminonly="0" 
                        defaultvalue="" 
                        hint="" 
                        label="Location City" 
                        message="Please enter a Location City" 
                        name="locationcity" 
                        optionlabellist="" 
                        optionlist="" 
                        orderno="2" 
                        regex="" 
                        required="true" 
                        type="TextBox" 
                        validation=""/>

                    <attribute 
                        adminonly="0" 
                        defaultvalue="" 
                        hint="" 
                        label="Location State" 
                        message="Please enter a Location State" 
                        name="locationstate" 
                        optionlabellist="" 
                        optionlist="" 
                        orderno="3" 
                        regex="" 
                        required="true" 
                        type="TextBox" 
                        validation=""/>

                    <attribute 
                        adminonly="0" 
                        defaultvalue="" 
                        hint="" 
                        label="Location Postal Code" 
                        message="" 
                        name="locationpostalcode" 
                        optionlabellist="" 
                        optionlist="" 
                        orderno="4" 
                        regex="" 
                        required="false" 
                        type="TextBox" 
                        validation=""/>

                </attributeset>
            </extension>
        </extensions>
    </mura>

Export Single Class Extension

To export a single Class Extension, follow the steps outlined below.

1. From the back-end administration area of Mura, select Site Settings, click Class Extensions, and select Class Extensions.
   
2. You should be directed to the Class Extensions screen.
   
3. Select the Class Extension you wish to export, from the listing of available Class Extensions.
   
4. You should be directed to the Class Extension screen.
   
5. Click the Export Class Extension button.
   
6. You should directed to the Export Class Extensions screen.
   
7. You can hover over the code, and press <CTRL>+C on a PC, or <CMD>+C on a Mac to copy it to your clipboard, then paste the code into your own XML file.
8. Or, you can simply click the Download button at the bottom of the screen, to download the code as a XML file.
   
9. You now have a file that can be used to import the Class Extension into another instance of Mura, or package it with a display object's config.xml.cfm file or a plugin's config.xml.cfm file for future distribution.

Export Multiple Class Extensions

To export multiple Class Extensions at the same time, so they can be packaged together in a single XML file, follow the steps outlined below.

1. From the back-end administration area of Mura, select Site Settings, then click Class Extensions, and select Export Extensions.
   
2. Or, from the Class Extension screen, select the Actions button, then click Export.
   
3. You should be directed to the Export Class Extensions screen.
   
4. Select the Class Extensions you wish to export, or simply click Select All to check all available Class Extensions if you desire to do so.
   
5. Click the Export button.
   
6. You should now be directed to the Export Class Extensions screen.
   
7. You can hover over the code, and press <CTRL>+C on a PC, or <CMD>+C on a Mac to copy it to your clipboard, then paste the code into your own XML file.
8. Or, you can simply click the Download button at the bottom of the screen, to download the code as a XML file.
   
9. You now have a file that can be used to import the Class Extension into another instance of Mura, or package it with a display object's config.xml.cfm file or a plugin's config.xml.cfm file for future distribution.

Example Mura ORM Entities

To have a more cohesive understanding of how to work with Mura ORM, let's describe a simple application, and the objects we'll need to create for it.

Let's assume our client has asked us to create an "Address Book" type of application. This application would require an authorized user to be able to add, edit/modify, and/or delete Address Book entries. Each authenticated user would have their own Address Book. In other words, if Suzie logged in, she would only be able to see, create and/or modify her own entries.

Again, we're going to try and refrain from overcomplicating things. However, as a developer, It's easy to begin anticipating all kinds of enhancements and/or modifications you may want to make, and that's great. For now though, let's just stick to the script.

Address Book

Since a typical address book is filled with people, we'll start off by creating a Person object. Next, we'll have to consider the kind of properties or attributes a Person object should have. For example, they could have a first name, last name, zero or more phone numbers (PhoneNumber objects), zero or more addresses (Address objects), and so on.

The address book entry (Person) would be treated as a single object. It could be referenced by a single variable containing a pointer to the object. In addition, various helper methods could be associated with the object, such as a method to return the preferred phone number, the home address, and so on.

The following illustration is a sample UML diagram of our objects.

So, using our very basic objects, we can now begin to create our Mura ORM entities.

Person

Using our previous example, we could start our Person.cfc with the following code.

component 
    extends="mura.bean.beanORM" 
    table="custom_persons" 
    entityname="person" 
    bundleable="true" 
    displayname="PersonBean" 
    public=true 
    orderby="namelast,namefirst" {

    // primary key
        property name="personid" fieldtype="id";

    // person attributes
        property 
            name="namefirst" 
            datatype="varchar" 
            length="255" 
            nullable=true;

        property 
            name="namelast" 
            datatype="varchar" 
            length="255" 
            nullable=true;

    // relationships
        property 
            name="phonenumbers" 
            singularname="phonenumber" 
            cfc="personphonenumber" 
            fieldtype="one-to-many" 
            loadkey="personid" 
            cascade="delete" 
            orderby="phonetype";

        property 
            name="addresses" 
            singularname="address" 
            cfc="personaddress" 
            fieldtype="one-to-many" 
            loadkey="personid" 
            cascade="delete" 
            orderby="addresstype";

    // Custom Methods
        public string function getFullName() {
            return get('namefirst') & ' ' & get('namelast');
        }

        public any function getHomeAddress() {
            var rs = QueryExecute(
                ('
                    SELECT addressid 
                    FROM custom_personaddresses 
                    WHERE addresstype = "Home" 
                        AND personid = :pid
                ')
                , { pid=get('personid') }
            );

            return rs.recordcount
                ? getBean('personaddress').loadBy(addressid=rs.addressid)
                : getBean('personaddress').set('adddresstype', 'Home');
        }

}

PersonPhoneNumber

The PersonPhoneNumber.cfc defines our PersonPhoneNumber entity.

component 
    extends="mura.bean.beanORM" 
    table="custom_personphonenumbers" 
    entityname="personphonenumber" 
    bundleable="true" 
    displayname="PersonPhoneNumberBean" 
    public=true {

    // primary key
        property name="phonenumberid" fieldtype="id";

    // foreign key
        property 
            name="person" 
            fieldtype="many-to-one" 
            cfc="person" 
            fkcolumn="personid" 
            nullable=true;

    // attributes
        property 
            name="phonetype" 
            datatype="varchar" 
            length="255" 
            nullable=true; // Home, Office, Mobile, etc.

        property 
            name="phonenumber" 
            datatype="varchar" 
            length="255" 
            nullable=true;
}

PersonAddress

The following code comprises our PersonAddress.cfc and will define our PersonAddress entity.

component 
    extends="mura.bean.beanORM" 
    table="custom_personaddresses" 
    entityname="personaddress" 
    bundleable="true" 
    displayname="PersonAddressBean" 
    public=true {

    // primary key
        property name="addressid" fieldtype="id";

    // foreign key
        property 
            name="person" 
            fieldtype="many-to-one" 
            cfc="person" 
            fkcolumn="personid" 
            nullable=true;

    // attributes
        property 
            name="addresstype" 
            datatype="varchar" 
            length="255" 
            nullable=true; // Home, Office, etc.

        property 
            name="street1" 
            datatype="varchar" 
            length="255" 
            nullable=true;

        property 
            name="street2" 
            datatype="varchar" 
            length="255" 
            nullable=true;

        property 
            name="city" 
            datatype="varchar" 
            length="255" 
            nullable=true;

        property 
            name="state" 
            datatype="varchar" 
            length="255" 
            nullable=true;

        property 
            name="zip" 
            datatype="varchar" 
            length="255" 
            nullable=true;
}

Example

The example below illustrates how to use the entities we've created to get an iterator of a person's phone numbers.

contactBean = m.getBean('person').loadBy(persionid=m.event('pid'));

// Phone Numbers Iterator
itPhones = contactBean.getPhoneNumbersIterator();

while ( itPhones.hasNext() ) {
  phone = itPhones.next();
  WriteOutput( phone.get('phonenumber') );
)

Enable/Disable Mura ORM Assembler & Scaffolder

Warning! This feature is in ALPHA status as of Mura v7.1, and functionality may change without notice.

To enable or disable the Mura ORM Assembler and Scaffolder, follow the steps below.

1. From the back-end administration area of Mura, go to Site Settings > Edit Settings.
   
2. Select the Modules tab.
   
3. Set "Mura ORM Scaffolding (ALPHA)" to "On" to enable, or "Off" to disable.
   
4. Then, click Save Settings to save your desired settings.
   

How to Use the Mura ORM Assembler

Warning! This feature is in ALPHA status as of Mura v7.1, and functionality may change without notice.

As previously mentioned, the Mura ORM Assembler enables for the creation and management of Mura ORM entity definitions and relationships. Once you've enabled the Mura ORM Assembler & Scaffolder, you may follow the steps outlined below to create Mura ORM entity definitions and relationships. Only Super Admin Users are able to use the Mura ORM Assembler.

1. From the back-end administration area of Mura, select Content on the main navigation, then select the Custom tab.
   
2. To create a new Mura ORM entity, click the Add button.
   
3. You should be taken to the Custom Mura ORM Entity screen.
   
4. Complete the information on the Definition tab. The primary fields are described below.
   
   • Entity Name
     • A variable-safe name (no spaces, begins with a letter, letters, numbers and underscores only). For instance, if you were creating a "Book" entity, you might call this entity simply "book".
   • Display Name
     • This is the human-readable version of the Entity Name, such as "Department Heads" or "Types of Pets".
   • Table Name
     • This is the table name the entity's data will be stored in. It is usually advisable to match it to the entity name, and is often prefixed with some special name to distinguish it in the database and avoid naming collisions with Mura's own table names. For instance, a "book" entity might have a table name like "custom_books" or "mycompany_books".
   • Order By (optional)
     • This is the default property (column) by which to sort/order your entity data by. It must match one of the Property Names of the entity (see below).
   • Scaffold
     • If enabled, this gives the entity permission to be managed in the Mura ORM Scaffolder for data entry/management.
   • Bundleable
     • If enabled, the entity and any stored data will be included in any site bundles.
   • Publicly Accessible
     • If enabled, the entity may be displayed and/or managed via the front-end of your Mura site. However, you will also be responsible for building the user interface for display and/or management on the front-end itself.
5. Also on the Definition tab, is where you manage the Entity Properties and relationships. An entity's "properties" are the fields where data will be stored, and will essentially be turned into columns within the defined Table Name. Every entity has a mandatory "id" property, which you may rename, but not delete. In addition, new entities also begin with an optional "siteid" property, which is important for tying the data to a specific Mura site. An entity's "relationships" are the keys that bind your entity to other Mura ORM entities.
   
   • How to Add /Edit Properties
     • Click the Add Property button, or select a property to edit.
       
     • You should now see the Property Details screen. The fields are described below.
       
       • Property Name
         • The variable-safe name for the property. For example, "booktitle" or "bookauthor".
       • Display Name
         • The human readable version of the property name. For example "Book Title" or "Book Author".
       • Data Type
         • The SQL data type the property should be saved as.
         • Valid options are:
           • VarChar
           • Text
           • Int
           • Boolean
           • DateTime
           • Any
       • Field Type
         • Valid options are:
           • None
             • This is the default value, and if selected, no database index will be created.
           • Index
             • If selected, a database index will be created on the property.
       • Default
         • The value entered here will be used as the default value in the Mura ORM Scaffolder. This is useful when the property's Form Field type is set to Dropdown or Radio to pre-select one of the the option list values.
       • Form Field
         • The value selected here will determine how the form field will appear in the Mura ORM Scaffolder when administrators are entering data.
         • Valid options are:
           • Text Field
           • Text Area
           • HTML Editor
           • Dropdown
           • Checkbox
           • Radio
           • Hidden
           • Do not render
       • Length
         • The maximum length of the data field.
       • Required
         • If checked, the property will be required in the Mura ORM Scaffolder.
       • List
         • If checked, the property will be displayed in the list view of the Mura ORM Scaffolder.
       • Filter
         • If checked, end users may use the "Filter By" functionality on this property in the list view of the Mura ORM Scaffolder.
       • Nullable
         • If checked, the property will be set to "NULL" in the database if no value is entered in the Mura ORM Scaffolder.
       • Option List
         • This field will appear if the Form Field type is set to Dropdown or Radio. Enter a carat (^) delimited list of values to be used as the labels for the form field. For example, "Matt^Grant^Steve".
       • Option Value List
         • This field will appear if the Form Field type is set to Dropdown or Radio. Enter a carat (^) delimited list of values to be used as the value which will be stored in the database. For example, "001^002^003". 
     • When finished, click the Add Property button.
       
     • To reorder Entity Properties, click+drag and drop the properties.
       
     • Click Save when finished.
       
     • A message will appear at the top of your screen to indicate when the entity definition has been saved.
       
     • In addition, a ".CFC" file will be auto-generated and saved under {context}/modules/dynamic_entities/model/beans/{EntityName}.cfc. If you wish, you could copy this file and save it under your own ../model/beans/ directory, and then delete the auto-generated file itself.
       
     • If you wish to delete the entity, simply click the Delete button, and select OK on the Alert dialog window. Also, when deleting entities, only the entity definition itself will be deleted from Mura, and the auto-generated ".CFC" file. However, all data will still be stored in the associated tables.
       
   • How to Add/Edit Relationships
     • Click the Add Relationship button, or select a relationship to edit.
       
     • You should now see the Relationship Details screen. The fields are described below.
       
       • Property Name
         • The variable-safe name that references the related entity. For example, a "book" entity might have related "authors". So, you could enter "author" or "authorid".
       • Display Name
         • The label, or human readable version of the relationship. For example, "Author" or "Author ID".
       • Relationship Type
         • When working with relationships, read the relationship from left to right. In other words, the left word refers to the current entity, and the word on the right refers to the related entity.
         • Valid Options:
           • one-to-many
             • This common type of relationship indicates the current entity may be related to multiple related entities. For example, one "order" entity could be related to multiple "product" entities.
           • one-to-one
             • This very simple relationship indicates there will only be one related entity to the current entity. For example, each "product" entity can be related to only one "manufacturer" entity.
           • many-to-one
             • Similar to the one-to-many relationship, this common relationship type indicates there may be multiple current entities related to a single entity. For example multiple "product" entities can be related to only one "order" entity.
         • If you wish to create a "many-to-many" relationship, the recommended approach is to simply create a one-to-many/many-to-one association between three participating entities. In other words, you would create a special entity to bind the related entities together. For example, you could have an "author" entity, a "book" entity, and a "authorsbooks" entity which stores the primary key values of both "authors" and "books" as a "many-to-one" relationship. For more information on this approach, view our blog post titled Mura ORM and Many-to-Many Relationships.
       • Relates To
         • Select the actual entity that this entity is related to. Only defined entities will appear in the list, in addition to Mura's own entities (such as "content" and "user"). If the desired entity has not been defined yet, you will need to define the entity, and come back to create the relationship.
       • Foreign Key Column
         • In most cases, this should be the related entity's "Primary Key" field. However, there may be an occasion where another field should be used to bind the entities together.
       • Render Field
         • The select menu will be populated with the properties of the selected entity from the "Relates To" field. Select the desired property to display when viewing the entity list in the Mura ORM Scaffolder table. For example, if the related entity is "author", you may wish to select the "Last Name" property instead of some obscure "authorid" property.
       • Load Key
         • This field relates to the Foreign Key Column. If the current entity is related by something other than the Primary Key, you should enter it here.
       • Cascade Delete?
         • Valid Options:
           • none
             • Do nothing if any related entities are deleted.
           • delete
             • If selected, this entity will be deleted when the related entity is deleted.
     • When finished, click the Add Relationship button.
       
   • The relationship will now display under the Entity Properties area. Simply click the gears icon to edit the relationship again, if desired.
     
6. The JSON tab displays the string to be saved in the database as the definition of the entity, and captures all of the properties and relationships created using the Mura ORM Assembler. This is especially useful information when using Mura.js to work with Mura ORM entities.
   
7. When finished, click the Save button to save your entity definition.
   
    

How to Use the Mura ORM Scaffolder

Warning! This feature is in ALPHA status as of Mura v7.1, and functionality may change without notice.

As previously mentioned, the Mura ORM Scaffolder lets you create, read, update/edit, and delete Mura ORM entity data. Once you've enabled the Mura ORM Assembler & Scaffolder, you may follow the steps outlined below to manage your Mura ORM entity data, assuming Mura ORM entities enabled for use in the Scaffolder exist.

Also, by default, Super Admin Users, and members of the Admin group are automatically granted permissions to the Mura ORM Scaffolder. However, members of these groups may also enable other groups access by managing the permissions to this section.

1. From the back-end administration area of Mura, select Content on the main navigation, then select the Custom tab.
   
2. You should be able to view to the Custom Entities table. This landing page lists all entity types available for editing via the Scaffolder. For example, the list below includes "Author", "Book", and "BooksAuthors Relationships".
   
3. To view an entities data entries, click the entity name on the list, or select the three-dot menu to the left of the entity name, and click the "List" option.
   
4. You should be taken to the entity's listing of entries. For example, in the illustration below, you can see the "Author" entries.
   
5. If a column (attribute) is filterable, there will be a text box above the column header. You may enter the search text and click the Enter/Return key or the Apply Filter button to filter the results.
   
6. To remove the filter, click the Remove Filter button.
   
7. You may also click on a column header to sort data on that column, and an arrow will appear by the header to indicate the sort direction.
   
8. To edit a entity, click on an entity attribute, or select the three-dot menu to the left, and click Edit.
   
9. You will then be taken to the entity's data entry screen.
   
10. To save the entity after making your edits, click the Save button.
    
11. To delete an entity, click the Delete button.
    
12. To add a new entity, from the entity's listing of entities, click the Add button.
    
13. You will be taken to the Edit screen. When creating or editing an entity, the form that appears will be determined by the entity's definition as created in the Mura ORM Assembler.
    
14. Complete the form data, then click Save to save your new entity.
    
15. Congratulations! You've successfully edited or added an entity.