Product Tip: How to use system fields like _created_at and _modified_by to record timestamps and user actions in Kissflow

In this video, you’ll learn how to use system fields to record timestamps and user actions.

System fields in Kissflow capture data about every item that goes through a flow. The values in these fields are system-generated and cannot be manually created or edited. You may have seen system fields like created at, submitted at, modified at, completed at, created by, and modified by. 

Here’s a quick summary to help you understand the purpose of these fields. 

_created_at: This field captures the date and time the initiator initiated the item as a draft. The date and time captured are static. This field captures the date and time the row in the table was created. The field always displays the time in GMT. 

_submitted_at: This field captures when the initiator submits the item into the workflow. The captured values are static. 

_modified_at: This field captured the time when the item was last modified. The captured value changes dynamically every time an action is performed on the item. 

_completed_at: This field captures the time when the item exits the workflow. The value captured is static. 

_modified_by: This field captures the user who last modified the item.

_created_by: This field captures the user who created the item.
https://www.loom.com/share/6c5cf8384fd1424fafe8c3ab4bf136c2

Read more about system fields here.

Upvote this post if you have learned something new.

Have you used system fields in your process forms?

A) Yes 

B) No

C) I’m going to implement this