> For the complete documentation index, see [llms.txt](https://docs.ifreeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ifreeq.com/developer/configure-in-platform/function-definition/standard-functions.md).

# Standard Functions

Defining product functionality is the first step in product development. Product features are combined in 3 parts, including standard, custom, and cloud functions.

![](/files/-MBnfLia-LLMNxcuhkS7)

 The standard feature are common features available under this category. If your product is created based on development-free solutions. The function point is fixed and it is not allowed to be changed.

You can directly choose to enable it. After enabling, you can edit it according to the actual product features. Useless features can be deleted, can still be re-enabled after deletion.

![](/files/-MBnfQwwxFHlye99H5PU)

It is important to note that the standard functionality does not support changing identifiers, function types, and data transfer classes because it is already bundled with some App interface components. Other properties can be edited.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ifreeq.com/developer/configure-in-platform/function-definition/standard-functions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.