> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-tm-cloud-integrations/version-history.md).
# Version History
## **GUMU™ Cloud (Deprecated)**
GUMU™ is built on modern cloud architecture and microservices to deliver high performance across all processes. Its parallel execution capability enhances productivity and speed by enabling near real-time data synchronization. Each process runs as an independently deployable service, ensuring scalability and flexibility.
GUMU™ connectors are designed for plug-and-play usage, with pre-defined mappings that can be tailored to meet diverse business integration needs. This allows customers to seamlessly integrate [multiple enterprise applications](/gumu-tailored-solution-integration.md) with minimal effort.
GUMU™ aims to eliminate the complexity of traditional integration development and implementation by offering a Software-as-a-Service (SaaS) platform for rapid deployment of integration solutions.
The GUMU™ Cloud platform is highly customizable, allowing users to define entity relationships, configure field mappings between applications, and implement custom processes and validations to meet specific business requirements.
### **Process Settings**
**Last Sync Date**
When first time user login and subscribe the connector at that time user can see below card as a blank last sync date.
1. Click on the edit icon
2\. Click the Calendar icon as shown below.
3\. Select the date from the date you want to fetch the data and click on the save button highlighted in below image. When the sync is completed, the value in this field is changed to the current date value.
### **Schedules**
The Schedule tab is to view all the scheduled processes in the portal as shown in the following Screen.
 Select the connector as per your choice
Select the process as per your choice
Click on this to Filter Schedule to apply filter as per connector and process.
 Click on this to Refresh button to refresh the scheduler status.
 click on this to Edit Schedule. It will show window as per Occurrence to set Schedule. If Occurrence is Monthly then Monthly Schedule window will appear as follows.
Do changes as you want and submit.
 Click on this icon to delete the Particular Schedule.
It will popup Confirmation window as follows.
Click Ok to Delete Schedule and Click Cancel if you do not want to delete. Once you Click Ok will popup message as follows.
### **Logs**
The Logs section is to view all the logs in the portal. Logs will display, **l**og details like Process name, Log Date, Time and Message.
By default, Error Filter is selected. User can set Filters such as Info, Warning, Debug accordingly as shown below
**Refresh**
Click on the Refresh button to see all the logs generated during the time of running process, it updates the log detail screen.
**Reset**
Click on the Reset button to reset all applied filters back to default.
**Clear**
Click on Clear icon to clear the logs.
**Filter**
Click on the Filter icon to apply the selected filters.
**Search**
Search functionality for quick search logs of specific process by keys you provide in the search box.
---
# 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:
```
GET https://docs.greytrix.com/gumu-tm-cloud-integrations/version-history.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.