Gravity Forms Entry Object

Gravity Forms Entry Object is the packet of information that was captured upon successful submission of a particular entry.

The data format is an array:

“An array in PHP is actually an ordered map. A map is a type that associates values to keys. This type is optimized for several different uses; it can be treated as an array, list (vector), hash table (an implementation of a map), dictionary, collection, stack, queue, and probably more.” – PHP.net

In principle:
array(
key => value,
key2 => value2,
key3 => value3,
…
)

In Gravity Forms, there are 22 potential entry object properties – in other words, 22 pieces of entry information that can be stored on submission:

1. id = unique ID of a particular entry
2. form_id = the ID of the form that produced an entry
3. created_by = the ID of the ‘logged-in’ user who submitted the entry
4. date_created = UTC date and time that the entry was submitted
5. date_updated = (the same as created, but updated)
6. is_starred = (boolean) if the entry was marked with a star in the entry list
7. is_read = (boolean) if the entry had been viewed
8. ip = IP address of the user who submitted the entry
9. source_url = the URL of the page that hosted the Gravity Form used
10. post_id = (a legacy object which is either null or contains the ID of the post created by legacy post fields)
11. user_agent = a string that identifies the browser, user name and device used when submitting the entry (though not 100% accurate)
12. status = if the entry is in the either active, spam or trash queue
13. currency = if pricing fields were used, a 3-character code indicating the currency
14. payment_status = null, or a 15-character status of a transaction completed via an add-on Authorized, Paid, Processing, Pending, Active, Expired, Failed, Cancelled, Approved, Reversed, Refunded, Voided
15. payment_date = null, or UTC date and time that a payment via an entry was completed
16. payment_amount = the payment amount in digits, without a currency symbol
17. transaction_id = unique transaction ID given by the payment gateway
18. is_fulfilled = (boolean) if the entry or transaction order has been fulfilled, or completed
19. transaction_type = indicating either a one-off payment or recurring subscription transaction
20. source_id = null, or the ID fo the post or page which hosted the form used in submission
21. [field or input id] = every field or input in the form has its own ID
22. [meta key] = meta data passed from add-ons used in the entry creation

Each of these entry objects, mapped out in this array, gives you the ability to control outcomes with form entry possibilities on a granular level.

Each entry object affords you precision when manipulating form processes as a developer.

For example, screening out all entries created by a particular user might give approval advantages in certain workflow examples..