ICT:Asset-Chain Children Button logic (with boolean field) - Revision history

Mngr at 16:44, 30 March 2026

2026-03-30T16:44:41Z

← Older revision		Revision as of 16:44, 30 March 2026
Line 45:		Line 45:
	* '''Result:''' Prevents a Parent from being assigned a Parent (Nested recursion).		* '''Result:''' Prevents a Parent from being assigned a Parent (Nested recursion).
	* '''Exception:''' Top Assets without children can still be edited to assign a parent, allowing for data entry error correction.		* '''Exception:''' Top Assets without children can still be edited to assign a parent, allowing for data entry error correction.


			== Heritage Project: Asset Hierarchy System ==

			=== Overview ===
			This system manages a single-level recursive asset hierarchy. It uses a custom boolean field to drive the User Interface (showing buttons) and data integrity (locking the hierarchy).

			=== Data Structure ===
			* '''Entity Types:''' Supports standard <code>node</code> and custom <code>asset</code> entities.
			* '''Field: Parent Asset''' (<code>field_as_parent_asset</code>): An Entity Reference field on child assets pointing to their Top Asset.
			* '''Field: Has Children''' (<code>field_as_has_children</code>): A boolean field on Top Assets used as a flag for hierarchy state.

			=== Implementation Logic (heritage_tweaks.module) ===

			The module automates the hierarchy through two main PHP hooks.

			==== 1. Hierarchy Automation (The Switch) ====
			The <code>heritage_tweaks_entity_presave()</code> function acts as a "detector" during the save process.
			* '''Trigger:''' When any asset is saved.
			* '''Action:''' If <code>field_as_parent_asset</code> is not empty, the code identifies the parent entity.
			* '''Result:''' It programmatically sets the parent's <code>field_as_has_children</code> to '''1 (TRUE)'''.
			* '''Outcome:''' This "wakes up" the children button in the main list view automatically.

			==== 2. Hierarchy Protection (The Safety Rail) ====
			The <code>heritage_tweaks_form_alter()</code> function protects data integrity during editing.
			* '''Trigger:''' When an existing asset is opened in the Edit form.
			* '''Logic:''' It checks the <code>field_as_has_children</code> value.
			* '''Constraint:''' If the value is '''1''', the <code>field_as_parent_asset</code> field is hidden (<code>#access = FALSE</code>).
			* '''Outcome:''' This prevents a Parent from being assigned to another Parent, strictly enforcing the '''single-level design rule'''.

			=== Views Configuration ===
			The "Children" button is rendered via a '''Global: Custom Text''' field using Twig logic:
			<syntaxhighlight lang="twig">
			{% if field_as_has_children %}
			<a href="/admin/asset-chain/{{ nid }}" class="button button--primary">Children</a>
			{% endif %}
			</syntaxhighlight>

			=== User Experience (UX) Guidelines ===
			* '''Single-Tab Navigation:''' The "Children" button opens in the current tab (no <code>_blank</code> target).
			* '''Gin Styling:''' Primary actions (Forward) use <code>button--primary</code>. Secondary actions (Back) use <code>button--secondary</code>.
			* '''Error Correction:''' Top Assets without children can still be edited to assign a parent if they were created as "Top" by mistake.

			=== Maintenance & Troubleshooting ===
			* '''Syncing Existing Data:''' To update assets created before this module, simply Edit and Save one child record for each Top Asset.
			* '''Cache:''' After any module code changes, perform a <code>drush cr</code> to refresh the hook registry.

Mngr at 16:39, 30 March 2026

2026-03-30T16:39:23Z

← Older revision		Revision as of 16:39, 30 March 2026
Line 37:		Line 37:
	* '''Adding Children:''' The button appears automatically the moment the first child is saved.		* '''Adding Children:''' The button appears automatically the moment the first child is saved.
	* '''Existing Data:''' To "wake up" a button for a Top Asset that already has children, simply Edit and Save one of its child records.		* '''Existing Data:''' To "wake up" a button for a Top Asset that already has children, simply Edit and Save one of its child records.



			=== Hierarchy Integrity Rule ===
			To enforce the "Single Level" hierarchy design:
			* '''Logic:''' The <code>field_as_parent_asset</code> field is hidden from the Edit form if <code>field_as_has_children</code> is TRUE.
			* '''Result:''' Prevents a Parent from being assigned a Parent (Nested recursion).
			* '''Exception:''' Top Assets without children can still be edited to assign a parent, allowing for data entry error correction.

Mngr: Created page with "== Asset Hierarchy: "Children" Button Logic == === Overview === This implementation displays a clickable button in the Top Assets table only when an asset has at least one child. It avoids complex and performance-heavy Views relationships by using a data-driven boolean flag. === Data Model === * '''Entity Type:''' Asset (or Node) * '''Parent Field:''' `field_as_parent_asset` (Entity Reference pointing to the parent). * '''Indicator Field:''' `field_as_h..."`


2026-03-30T16:26:23Z
Created page with "== Asset Hierarchy: "Children" Button Logic ==  === Overview === This implementation displays a clickable button in the Top Assets table only when an asset has at least one child. It avoids complex and performance-heavy Views relationships by using a data-driven boolean flag.  === Data Model === * '''Entity Type:''' Asset (or Node) * '''Parent Field:''' <code>field_as_parent_asset</code> (Entity Reference pointing to the parent). * '''Indicator Field:''' <code>field_as_h..."
New page
== Asset Hierarchy: "Children" Button Logic ==



=== Overview ===

This implementation displays a clickable button in the Top Assets table only when an asset has at least one child. It avoids complex and performance-heavy Views relationships by using a data-driven boolean flag.



=== Data Model ===

* '''Entity Type:''' Asset (or Node)

* '''Parent Field:''' <code>field_as_parent_asset</code> (Entity Reference pointing to the parent).

* '''Indicator Field:''' <code>field_as_has_children</code> (Boolean).

** Default: Off (0)

** Logic: Marks if a Top Asset is a parent.



=== Automation (The Tweak Module) ===

The logic is handled automatically by the '''Heritage Tweaks''' module via <code>hook_entity_presave</code>.



* '''Trigger:''' When a child asset is saved.

* '''Action:''' The code identifies the parent referenced in <code>field_as_parent_asset</code>.

* '''Result:''' It programmatically flips the parent's <code>field_as_has_children</code> to '''True (1)'''.



=== Views Configuration ===

The button is rendered using a '''Global: Custom Text''' field in the Assets View.



==== Logic ====

The button uses Twig to check the boolean state before rendering:

<syntaxhighlight lang="twig">

{% if field_as_has_children %}

  <a href="/admin/asset-chain/{{ nid }}" class="button button--primary">Children</a>

{% endif %}

</syntaxhighlight>



==== Key Settings ====

* '''Filters:''' <code>field_as_parent_asset</code> is EMPTY (Ensures only Top Assets are listed).

* '''Gin Styling:''' Uses <code>button button--primary</code> classes to match the Gin Admin Theme accent colors.

* '''Field Order:''' The <code>field_as_has_children</code> field must be positioned '''above''' the Custom Text field and set to "Exclude from display."



=== Maintenance ===

* '''Adding Children:''' The button appears automatically the moment the first child is saved.

* '''Existing Data:''' To "wake up" a button for a Top Asset that already has children, simply Edit and Save one of its child records.