# Templates - increasing functionality beyond task descriptions

**URL:** <https://community.fibery.io/t/templates-increasing-functionality-beyond-task-descriptions/3878>\
**Category:** Get Help\
**Created:** [January 30, 2023, 2:46pm UTC](https://community.fibery.io/t/templates-increasing-functionality-beyond-task-descriptions/3878 "2023-01-30T14:46:18Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [January 30, 2023, 2:57pm UTC](https://community.fibery.io/t/templates-increasing-functionality-beyond-task-descriptions/3878/3 "2023-01-30T14:57:49Z")

</div>

Here’s another Fibery entity-templating pattern:

> [@How I Implemented "Entity Templates"](https://community.fibery.io/t/how-i-implemented-entity-templates/3273):
>
> I’m sharing my implementation of an entity Templating pattern, which has a simple interface to trigger copying the fields from a Template entity to a new entity (including cloning its collections). The pattern requires adding a “Template” relation (self-related) to a DB, which identifies a Template entity to copy from, and a Rule to do the copying. I’ll illustrate the implementation using my “Project” DB: I added the one-to-many self-relation “Template” (called “Template Target” on the other …

---

_[View the full topic](https://community.fibery.io/t/templates-increasing-functionality-beyond-task-descriptions/3878)._