Please enable JavaScript to view this site.

Made in EU
Freshdesk Forums

Navigation: Catalog: Freshdesk > Schemas > Schema: Freshdesk > Tables

time_entries: Freshdesk Time Entries

Catalog: Freshdesk

Schema: Freshdesk

Primary Keys: id

Label: Time Entries

This is a read-only table function. The Freshdesk API may not support changing the data or the Invantive UniversalSQL driver for Freshdesk does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Freshdesk API.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function time_entries. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name

Data Type

Required

Default Value

Documentation

agent_id

int64

☐

 

Agent ID of entry.

billable

boolean

☐

 

Limit to specific state of billable flag.

company_id

int64

☐

 

Company ID of entry.

executed_after

datetime

☐

 

Minimum value of execution date.

executed_before

datetime

☐

 

Maximum value of execution date.

 

Columns of Table Function

The columns of the table function time_entries are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

agent_email

varchar2

Agent Email

☐

The agent email in the response related to user_id.

agent_id

int64

Agent ID

☐

 

agent_name

varchar2

Agent Name

☐

System fills the agent name in the response from the user_id.

billable

char

Billable

☐

Whether the entry is billable.

company_id

int64

Company ID

☐

 

contact_email

varchar2

Contact Email Address

☐

The requester email of the ticket.

created_at

datetime

Created at

☐

Date/time at which the record was created.

customer_name

varchar2

Customer Name

☐

The customer name.

executed_at

datetime

Executed at

☐

Time at which this time-entry id added/created.

hhmm

varchar2

Time Mask

☐

The number of hours (in hh:mm format). Used to set the total time_spent. If this property is set via update call the timer_running will be stopped and reset to the passed value.

id

int64

ID

☐

ID of the time entry.

note

varchar2

Note

☐

Description on this time entry.

start_time

datetime

Start Time

☐

The time at which the time entry is added or the time of the last invoked 'start-timer' action using a toggle.

ticket_id

int64

Ticket ID

☐

The ID of the ticket to which this time entry is associated. Id is passed as part of the handle URL.

time_spent

int64

Time Spent

☐

Time spent in the format hh:mm but converted to seconds.

timer_running

char

Timer Running

☐

Whether the start timer is invoked and is currently running.

updated_at

datetime

Updated at

☐

Date/time at which the record was last updated.

user_id

int64

User ID

☐

The user/agent to whom this time entry is associated.

 

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

  
Disclaimer