# CHANGELOG: October 1 / Create Documents and Whiteboards inside entities, Automatically link entities based on rules

**URL:** <https://community.fibery.io/t/changelog-october-1-create-documents-and-whiteboards-inside-entities-automatically-link-entities-based-on-rules/1023>\
**Category:** Changelog\
**Created:** [October 1, 2020, 6:50am UTC](https://community.fibery.io/t/changelog-october-1-create-documents-and-whiteboards-inside-entities-automatically-link-entities-based-on-rules/1023 "2020-10-01T06:50:49Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 10, 2020, 8:38pm UTC](https://community.fibery.io/t/changelog-october-1-create-documents-and-whiteboards-inside-entities-automatically-link-entities-based-on-rules/1023/10 "2020-10-10T20:38:18Z")

</div>

[EDIT: I have updated the app since this post was written, and it is now over here: [Basic Test Management app](https://community.fibery.io/t/basic-test-management-app/1099) and sharing seems to work now]

So I managed to make something useful using the automatic relations feature: a rudimentary test management app.  
The idea is that a Test Case has several ordered Steps (with Action and Expected Result fields), and is linked to one or more Test Executions.  
The Test Execution also links to a set of (ordered) Step Results (which have an Actual Result field, to be filled in by the tester when the test is run).  
Then by auto-linking the Step Results to the Steps (based on the test case and order number) it’s easy to have a table view for each execution showing action/expected result/actual result for each step.  
I also added a bit of logic so that it’s possible to see which execution is the latest for each test case, plus a summary report of all testing.

> **[Start for free, upgrade when you love it — Fibery](https://shared.fibery.io/sign-up?appShareId=98fd17b3-01d4-47f0-8b54-d5ece68b748e-testing)**
>
> Create Fibery account. Build your company workspace with no code.

I hope people will have a play with it and give feedback.

[edit: I have tried to import the app into another instance of fibery and I get an error message:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/17b5f73de062b1a7dc5b83e9c6a29ee1f1471f63.png)  
so hopefully @mdubakov or the team can figure out what’s going on. I think it may be a bug in sharing apps that contain automatic relations]

For the next iteration, I was thinking of adding an action button for the Test Case (‘Execute Test’) which would automatically create a Test Execution and all the necessary Step Result entities, so that a tester only needs to enter the Actual Result data 🙂

There are still some practical issues to be considered/fixed, such as how to handle changes to the test case after it has been executed, but it seems that versioning might be coming from the fibery team at some point, so I won’t try and tackle it just yet 🙂

> [@Versioning in Rich Text Fields (and entities as a whole, too)](https://community.fibery.io/t/approved-versioning-in-rich-text-fields-and-entities-as-a-whole-too/260):
>
> Hi, I think versioning in general is an important feature and versioning of each entity as a whole is not only useful, it is a requirement in certain compliance context. To begin with, the rich text fields should have versioning (and afterwards diff view between versions, revert back to a specific version, etc. too). In general, using an event-sourced architecture greatly helps with features like versioning, undo-redo, etc. Thanks!

---

_[View the full topic](https://community.fibery.io/t/changelog-october-1-create-documents-and-whiteboards-inside-entities-automatically-link-entities-based-on-rules/1023)._