# Release 178- February 2020

**URL:** <https://community.tulip.co/t/release-178-february-2020/239>\
**Category:** Announcements\
**Created:** [January 30, 2020, 8:09pm UTC](https://community.tulip.co/t/release-178-february-2020/239 "2020-01-30T20:09:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [January 30, 2020, 8:09pm UTC](https://community.tulip.co/t/release-178-february-2020/239/1 "2020-01-30T20:09:30Z")

</div>

These are the product updates in release 178.

Release 178 goes live to all “production” customers on 2/10/2020.

&nbsp;

**["Undo" command now available in the App builder!](https://support.tulip.co/en/articles/3673145-how-to-undo-actions-in-the-app-builder)**

Good news! You can now “undo” these events with any widget (button, shape, image etc.)

- Moving a widget
- Resizing a widget
- Rotating a widget

Hit “Control+Z” on Windows or “CMD+Z” on Mac to try it out. You can only “undo” the latest event.

**Group by “Number” and “Integer” variables in the Analytics Builder**

- You can now group bars in the Analytics Builder based on a “number” or “integer” variable

**["Delete Record" Trigger action is now available](https://support.tulip.co/en/articles/3088631-list-of-actions-in-the-trigger-editor)**

- You can now delete records using logic in the Trigger Editor

**[New metadata columns in Tables](https://support.tulip.co/en/articles/2835889-an-overview-of-tables)**

- Tables now automatically display the time that each record was created and last updated. These timestamps cannot be used in trigger logic (yet!)

---

<div class="post-metadata">

**Author:** ![pencerw](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pencerw/32/68_2.png) [@pencerw](https://community.tulip.co/u/pencerw)\
**Post date:** [February 3, 2020, 4:06pm UTC](https://community.tulip.co/t/release-178-february-2020/239/2 "2020-02-03T16:06:13Z")

</div>

Very excited about the automatic metadata on tables - that’ll make my table triggers a lot more streamlined 🙂

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 3, 2020, 4:09pm UTC](https://community.tulip.co/t/release-178-february-2020/239/3 "2020-02-03T16:09:41Z")

</div>

@pencerw Just added a note, but those values cannot be used in trigger logic at the moment. It can only be displayed on the Triggers page.

---

<div class="post-metadata">

**Author:** ![pencerw](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/pencerw/32/68_2.png) [@pencerw](https://community.tulip.co/u/pencerw)\
**Post date:** [February 3, 2020, 4:14pm UTC](https://community.tulip.co/t/release-178-february-2020/239/4 "2020-02-03T16:14:02Z")

</div>

@kevin.kononenko Sorry, I was being unclear - I’ve been using datetime fields in a few tables (including the Entry Log [described here](https://community.tulip.co/t/tulip-for-managed-keyless-door-entry/238)) to see when events are happening. Getting those fields to propagate is a multi step process, though, and now that the record creation time is automatically set I can clear out all of those and make my table record creation triggers a lot simpler.

---

<div class="post-metadata">

**Author:** ![kevin.kononenko](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/kevin.kononenko/32/32_2.png) [@kevin.kononenko](https://community.tulip.co/u/kevin.kononenko)\
**Post date:** [February 3, 2020, 4:17pm UTC](https://community.tulip.co/t/release-178-february-2020/239/5 "2020-02-03T16:17:17Z")

</div>

Ahhh nice, got it! That makes sense.