What action can users perform through records in Appian?

In Appian, records serve as a consolidated interface that allows users to interact with data. The primary function of records is to enable users to view, analyze, and take actions based on the information presented. This can include tasks such as updating data, initiating processes, and monitoring the status of related items.

The ability to view and take action on data is central to the purpose of records in Appian, as they are designed to provide a comprehensive view of relevant information in one place. Users can engage with this data by performing operations such as editing entries, triggering workflows, or generating reports directly from the records interface.

The other choices do not align with the functions of records in Appian. Documenting project requirements usually involves separate tools or documentation processes outside of Appian's record functionality. Manipulating application code directly is also not a capability users would have through records; such actions require the use of the Appian Designer or other development environments. Designing new applications is a broader development task that would take place in the Appian platform, but it is not a function attributed to records themselves, which are focused on data interaction rather than application creation.