> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/open-v5.3-en/novedades/previas.md). # Previous Versions In versions prior to 5.3, the following changes were made ## Onesait Editran V5.1.0. ### Discontinued functionality #### Onesait · Editran Protocol * Compatibility with editran V3.1 is removed. This version will only be able to communicate with remote entities that have editran V4.0 installed at minimum. If profiles from earlier versions are migrated, sessions with version 3.1 or lower will be registered with version 4.0. #### editran /IC -- Confirmed exchanges * The editran /IC module for confirmed exchanges has been discontinued. ### New features #### editran /P **The maximum number of concurrent transmissions is 500.** The limit of concurrent sessions in previous versions was 100. It has been increased to 500, which will be the new default value for the field *"Maximum number of sessions"* of the local profile. **Activity control for connected sessions.** The protocol establishes a new inactivity timeout that controls whether, if a session is connected but there is no data traffic for a given time, it is released. The default timeout value is 600 s, which the user can modify by defining the EDI\_TOUT\_IDLE environment variable. Once the timeout expires, the release is recorded in the log with the following message: *"Release due to inactivity timeout"*. **Alphabet negotiation when establishing the session.** In V5.1 the protocol has been modified so that the alphabet is negotiated between entities whenever possible, removing from the user the responsibility of knowing that data for the remote installation. To maintain compatibility with version 5.0 or lower, the alphabet field has been kept in the editran /P profile, but note that it is only used when the connection is outgoing. If the remote entity is the one that calls, regardless of the version and the field value, the connection is accepted and communication takes place in its alphabet. #### editran /TCP **Addition of cause and diagnosis to disconnections.** In earlier versions, in TCP transmissions when the editran application is the one that rejects the connection (because the profile does not exist, due to time control, IP validation, etc.), the calling entity only receives the release, but cannot tell the reason. To avoid this situation, a TCP message has been added that sends the cause and diagnosis of the disconnection before closing the socket. #### editran /G **Download confirmation** The functionality for confirming remote downloads is implemented, so that the sender does not consider the transmission finished until it has confirmation that the receiver downloaded it correctly. In the editran /G profile the new parameter *"Request download confirmation"* determines whether sending should behave as before or whether remote confirmation is desired. On reception, the result of the last download is returned whenever the sender requests it. When the sender requests remote confirmation, once the transmission ends the Presentation remains in TRANSMITTED state and starts a timeout waiting for the remote response. If the timeout expires without the receiver having indicated the result of the download, the sender connects and asks for it. If the response is that the download process has still not finished, a new timeout is started until retries are exhausted; otherwise, the post-send user process is launched with result 200 if the download has failed or 0 if it completed successfully. #### Editran cryptography **Graphical utility for key management** A Java 6 application for key management has been added to CRIPTOlib, providing a graphical user interface that simplifies querying and generating the keys stored in the files ***ckds.des*** and ***ckds.rsa***. The utility is delivered in a JAR file called EDItranCript.jar. See the document *CRIPTOlib/DES 3.0 User Manual* for usage information. **Thread-safe CRIPTOlib/DES code** The code of the CRIPTOlib/DES library has been modified so it can be safely used in multithreaded applications, that is, so that it works correctly during the simultaneous execution of several threads. #### editran /GT: Web application for transmission scheduling. Transmission manager that incorporates the following functionality: * Configuration for scheduling outgoing and incoming transmissions, highly parameterizable, allowing time windows, retries, subsequent processes, etc. to be defined. * Consultation of information on the transmissions that have been carried out (sent files, start and end date-time of the transmission, current status of each transmission...). * Recording of incidents in transmissions that have ended with some type of error. This functionality existed in previous versions only for Windows. In this version it is available for all operating systems and has been designed as a Web application. Users can access the application from a browser. The web browsers tested are: IE8, IE9, Firefox, and Chrome. #### editran /PX **Incorporation of route table** The possibility has been added for a single proxy to listen on multiple IPs and/or ports and, in addition, for each one to be associated with different Hosts. Each route will establish a listening address and the list of corresponding Hosts, so that for each incoming connection the Hosts will be tried in the order they are listed. That is, only if the connection with the first Host fails will the first backup be tried, and so on. A maximum of 10 routes can be defined. An example of a configuration with several routes would be: Current configuration of the local environment: Name (or IP) - listening port: 127.0.0.1 - 1111 Name (or IP) - HOST port: 1.1.1.1 - 1111 Name (or IP) - listening port: 127.0.0.1 - 2222 Name (or IP) - HOST port: 2.2.2.2 - 2222 Name (or IP) - HOST port: 3.3.3.3 - 3333 **Graphical utility for configuration** The configuration of the editran Proxy in earlier versions was done in command mode. In this version, a utility has also been incorporated that allows it to be done through a graphical interface. It is a Java 6 application delivered in a JAR file called ConfigurarProxy.jar. See the document *EDItran/PX 5.1 Installation and User Manual* for usage information. **Log file size limit** The Log file generated by the editran /PX and editran /TX gateways has been limited in this version to a maximum size configurable by the user. When it is exceeded, the log file is rotated, leaving the old one renamed as log\.txt. By default, the maximum assigned size is 1 GB. ### Fixed issues | **Code** | **Module** | **OS** | **Description** | | ----------- | ------------ | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **I502-01** | editran /GC | All | editran /GC only generates DES subsystems with single key length; however, they were erroneously included as double in the ckds.des file. | | **I502-02** | Converters | HPs, Linux | When receiving uncompressed from remote entities V4.0, the download fails due to total control. | | **I502-04** | editran /X25 | Sun, Aix | Outgoing connections are rejected by the remote side due to NRI validation. | | **I502-05** | editran /X25 | HPs | Incoming calls always arrive at editran with reverse charge, even if it is not included in the facilities. | | **I502-13** | editran /X25 | Aix | Incoming calls without user data or facilities caused a memory failure. | | **I502-14** | EDITRAN/TCP | HP-Itanium | A transient failure in accept() caused editran to stop handling incoming connections. Outgoing ones continued to work without problems. | | **I502-17** | MenuG | Windows | Fails with Presentations with a name length of 26 (maximum possible). | | **I502-19** | editran /AL | All | Whenever the SMTP server supports the AUTH extension, the user was forced to authenticate even when it was not necessary. | | **I502-20** | Converters | All | Variable files with the last line lacking a separator were loaded, but remote download failed. | | **I502-22** | editran /CL | Windows | In some cases, the client Menu/G stored incorrectly formatted data in the server status file. | | **I502-23** | editran /CL | Windows | In distributed menus without an administrator license, every time a key is pressed on the sessions list, an error message appears. | | **I502-24** | editran /GT | Windows | In scheduled sendings, if there is a post-process to move files and it fails, the task ends as successfully completed, and this causes the file to be sent repeatedly until it manages to move it. | | **I502-26** | editran /X25 | HPs | Random stoppage of the process related to connection failures. | | **I502-27** | Menus | Linux | Menus close when restoring the previous window due to a memory problem. | | **I502-28** | editran /GC | All | When generating an Own DES key, which has to be signed, the file that exports it contains the version of the first local RSA subsystem instead of the version of the one that was actually chosen. | | **I502-29** | FichEmi | Windows | It did not modify the list of files to be sent in the editran /G profile. | | **I502-30** | editran /P | All | The connection time control did not work correctly with time ranges in which the start time is greater than the end time. | | **I502-31** | editran /GT | Windows | editran /G ignores hidden files, but editran /GT did not. This caused the scheduler to launch requests to editran /G that failed because there was no data to send. | | **I502-32** | Converters | All | On reception, the converter would get stuck when a year mask with maximum size was set in the reception destination (for example: %2Y). | | **I502-33** | editran /CL | Windows | When validation fails while creating/modifying the profile, the window does not close but the error is not reported to the user. | | **I502-34** | editran /GC | Windows | The graphical interface has a maximum limit of 100 Subsystems. When this limit is exceeded, the lists become empty but no warning message is shown. | | **I502-36** | editran /GT | Windows | In reception windows, the user is allowed to modify the single-shipment-per-window check. | | **I502-42** | License/SSL | All | SSL license generation fails when in the template the field **instances** exceeds the 40-byte limit. | | **I502-43** | IPCs | All | Random stoppage of editran due to a failure in the exchange of information between the processes and the menus. | | **I502-44** | editran /GT | Windows | The process did not release resources correctly, which over time could have consequences for the operating system. | | **I502-57** | editran /GC | All | When migrating editran /GC data, keys were lost. | ## Onesait Editran v5.2.0 ### Discontinued functionality #### Editran Protocol * Compatibility with editran V4.0 is removed * PKI cryptography for entity authentication disappears. #### editran /X25 * Due to Telefonica/Movistar discontinuing X25/X28 lines, editran removes these types of connections. * The editran /TX module, which provided access to the X25 network in mainframe environments without the need for a communications controller, has been discontinued. #### editran /EA -- Statistics and alarms * This module has been temporarily discontinued. A new version designed as a Web application is under development. ### New features #### Editran cryptography **New Version 4.0 for V5.2 transmissions** * Cryptography 4.0 only supports RSA as an endpoint authentication mechanism. In the Editran/GC module, DES key exchange is removed. * Cryptography 3.0 only supports RSA keys with a length of 1024; in the new version this is expanded to 2048 and 4096 keys. * The AES encryption algorithm is incorporated for data encryption. Supported keys are 128, 192 and 256 bits. The encryption key exchange relies on RSA cryptography of up to 4096 bits and the SHA-2 hash mechanism. * These changes do not affect presentation sessions configured with previous encryption versions (v2.2 or v3.0). In these cases the functionality remains the same. #### editran /PX * Route definition filtering by entity codes. The product can be configured so that remote connections are routed to different Editran servers on the internal network, depending on the code of the connecting entity. #### Other improvements **Different paths for Editran programs and data** In previous versions the configuration files and temporary files (buffers, status, etc.) were always stored in the editran working directory. In the new version it is possible to decouple them from the product installation path by defining the path where the processes look for and store those files. * This feature will be especially useful in production environments where several instances of editran installed on different machines, in active-passive mode, can share those files. * The data path is set via the EDI\_DATA environment variable in Unix and via the DataPath registry key in Windows. See editran *V5.2 Installation Manual* for more information. **New parameter in post-send/receive processes** In this version, when editran runs the user programs after sending or receiving, the parameter list is: Presentation, direction, local code, remote code, application, and the absolute path of the file containing the list of transmitted files. Unlike previous versions, the user will no longer need to know where editran leaves that file, since it is given to them. Post-processes will only run when the transmission has completed successfully. In these cases the file list can be used for integration with other applications, for example, moving received files or deleting files already sent. **editran /GT (Windows)** In scheduled sendings through editran /GT, the possibility of running the procedure implemented by the user has been added (usually batch programs). In this process, the sent files must be deleted or moved so they are not transmitted again. The program is invoked with the following parameters: Presentation and absolute path of the file containing the list of transmitted files. If when configuring the Presentation in editran /GT, you select *"Run process"* and leave it blank, nothing will be done after sending. This can be useful when the post-send tasks have already been performed in the user program defined in editran /G. ### Fixed issues The table shows only the incidents detected in V5.1.0 and which, due to their severity, have not been fixed in patches generated for the version itself. | **Code** | **Module** | **OS** | **Description** | | ----------- | ----------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **I510-75** | editran | All | In sessions configured with V3.0 key exchange and, for example, a different record length, entity (A) that receives the association request rejects it due to profiles, but entity (B) that calls does not receive that rejection and ends with "Retry attempts exhausted for establishing session". It is necessary to stop editran on entity (A) in order to associate again. | | **I510-85** | MenuG | Unix | A Presentation can be created with the APPLICATION field empty (blank). | | **I510-81** | editran /GT | Windows | If a scheduled Presentation is renamed from MenuG, editran /GT does not detect that change and continues launching transmission requests for the old Presentation. | | **I510-73** | editran /GT | Windows | It should be allowed to stop the search when there are presentations in state *"Finished with error. Retrying"*. It is only prevented when the state of any presentation is "T*ransmitting"*. | | **I510-70** | editran /GC | Windows | When the list of remotes associated with a local subsystem is so long that it needs scrolling, the panel with the list of own keys becomes so small that it does not allow any row to be displayed. | ## Onesait Editran v5.2.1 ### Improvement in integration with the signature module (Editran/FF) In the sending of signed files, Editran validates that none is transmitted that does not comply with the signature workflow defined for it in the Editran/**FF.** In previous versions, this validation process required developing ad hoc pre- and post-processes in each installation. In this version, a dialogue with the signature module has been incorporated as an improvement, allowing Editran to consult the files that are ready to be transmitted. ### Daily report of transmitted files. As an additional feature, the possibility of generating daily reports of transmitted files has been added. The product administrator can enable this option through the application's configuration settings in the Windows registry. The reports are named *FicherosEditran.\.txt*, and are CSV-formatted files in which each line corresponds to a file sent or received that day. You can consult the details of this report in the *Generic Application Interface User Manual*. ### Improvement in license control In this version the format of the license file delivered with the software has been modified to improve control of product usage. Specifically, the new format allows greater flexibility in two scenarios: * Installations with several local codes for which different functional modules are contracted. * The previous account control options have been replaced, increasing the parameters to be evaluated. This feature only applies to Editran transmissions that exchange banking standards. ### Upgrade to RHEL 8 operating system We updated the product to the operating system versions most installed by customers. Specifically, with the upgrade to RHEL 8, the product's dependency on an old unsupported version of OpenSSL (1.0.2) is removed. ## Incidents and improvements v5.2.1.2 (February 2023) * **ODEM-323 Presentation remains in Transmitting state** In a specific case, and associated with concurrent transmissions, this situation has occurred: ✔ The Presentation status remains TRANSMITTING indefinitely, and is only released when the operator requests it manually. ✔ In the log information, the last recorded event is that a call is made for which no response is received. ✔ In this situation, if the remote side calls, the incoming connection is released due to a collision. * **ODEM-330 Blockage in editrang process** A blocking situation occurs randomly that forces stopping the Editran service in order for it to work again. It has been detected only in installations with a billing license, and when files with a long path are transmitted (more than 80 characters). * **ODEM-334 Error in naming transmitted files report** It was being named as *"Editran.his"* so the file accumulated a history of transmitted files and not a daily report as it should. It is modified so that it is generated as follows:*"FicherosEditran.\.txt"*. * **ODEM-331 Error in cfgupt command** The command fails with the *"-f"* option when the file contains both the session profile and the presentation profile. * **ODEM-427 Error in download of a previously interrupted reception** In a transmission that is interrupted once part of the information has already been exchanged, the sender initializes and loads new information. In that case, both sendings are mixed together on the receiving end and the download ends up failing. * **ODEM-428 Improvements in Editran script** ✔ The script is modified so that processes inherit the PATH variable with the "." path. ✔ The script with the *stop* option ended without waiting for internal TCP ports to be fully released. This caused the system not to start immediately when doing *EDItran start* the system would not start. * **ODEM-434 Migration of DES v2.2 keys** The import of DES keys from the command file fails when they come from zOS environments. This is a special case of migration because an auxiliary variable is used. * **ODEM-471 Error in modiperfi command** Mass profile modification fails and leaves messages such as: > ERROR \[near <"SESSION-NAME">] in line x:\ > error in field:\ > (not registered) * **ODEM-506 Modiperfi fails in mass changes of several parameters** In executions of *modiperfi* with changes that apply to several sessions/presentations, and in which several parameters are specified, only the full change is made in the first session. For example: > modiperfi -oP --s"\*" -m"-Enomaplic=Aplic -Enomrem=Rem" In the first session the application and remote names change, but in the following sessions only the application name changes. * **ODEM-508 Memory leak in editranp with RSA authentication** In the *editranp* process, memory is being misused when there is RSA authentication. Reading the keys reserves memory that is not being freed in all cases. ## Incidents and improvements v5.2.1.3 (July 2023) * **ODEM-539 Error in TELEGC channel creation** The gc\_config command creates the TELEGC channel with incorrect data in the fields: CHECK SIGNATURES (Y/N) REQUEST DOWNLOAD CONFIRMATION (Y/N) * **ODEM-557 EDItran script option for license management** Modify the EDItran script so that it manages the start/stop/status of the license service. For this, a new -l option will be included: **EDItran -l start** starts the license service **EDItran -l** status checks the status of the license service **EDItran -l** stop stops the license service only if editranp is not active * **ODEM-570 Editran crashes when defining the LICSRV variable** The license server allows its listening port value to be modified (default 50777). In these cases, Editran must define the LICSRV environment variable with that value in order to connect to the server. It has been detected that this causes crashes in both the editranp and editrang processes. * **ODEM-598 Validation in session profile** When creating/modifying a session profile, the field "No. of records per send block" must only admit values greater than zero. * **ODEM-659 Improvement in the profile migration utility** The script *migra-cfg.bash* is adapted to take EDI\_DATA into account. * **ODEM-700 Additional information in file reports** An evolution that allows parametrizing the level of detail of the data shown in file reports. * \[**ODEM-726** *menucmd* **does not connect and shows no error**] The utility *menucmd* did nothing. * **ODEM-745 Error stopping service in Linux Ubuntu** When trying to stop the services (EDItran stop) on an Ubuntu distribution, the message "port: not found" is shown ## Incidents and improvements v5.2.1.4 (January 2024) * **ODEM-738 Exit from Editran/gc** When exiting the Editran/GC menu, the option typed is not shown in the confirmation window. * **ODEM-761 OPEN\_OUT error when the reception directory does not exist** If in "reception destination" a path ending in '/' is entered (for example /var/Editran/datos/), and the subfolders do not exist, the download fails with OPEN\_OUT error. In this case, what it should do is create the path and leave the received file with the name it had at the source. * **ODEM-765 Duplication in the file list when using the +\ wildcard** If the remote sends several files that the receiver wants to save as one, the wildcard *+\*is used in the destination path. In these cases, in the list of transmitted files (tmp/\*.ficheros) the same path appears several times when in reality only one has been left. * **ODEM-769 Migration of remotes with encryption** When the previous installation had remote templates defined with encryption options, migration fails and this error appears: Incorrect license (des/rsa)\ \[LicAPI]-\[ERROR] Local Entity does NOT exist: It is modified so that remote templates are migrated without license validation. * **ODEM-781 Use of modiperfi command** The program does not control the correct syntax of the command. When it is used to modify several parameters at once, all of them must be specified in the value of the option **--m**. If the option is entered several times by mistake, the command does not show an error, but only applies the last modification specified. * **ODEM-827 Compression in Editran/P causes an editranp crash** When the Editran/P profile is configured with *Compression=Yes*, the process stops randomly. The process log contains error messages related to an invalid SCP format. * **ODEM-863 Menus that consume CPU** This has been observed in tty connections that open a menu and close it using the X without exiting the program. With certain terminal configurations the process can remain running, and because it no longer has an associated tty, it starts consuming a lot of CPU. ## Incidents and improvements v5.2.1.5 (June 2024) * **ODEM-988 Bug in modiperfi command** In installations that do not have the "." directory in the PATH, when running modiperfi the message indicates that modifications have been made, although in reality they have not. * **ODEM-989 Start Editran as a service** A service unit is created and the script is adapted **EDItran.install** so that it can start as a service. * **ODEM-1012 File output paths with spaces** It is modified so that paths with spaces can be entered in the output file list. In previous versions, loading fails because these cases are not interpreted correctly. * **ODEM-1029 Installer for RH9** Editran is compiled for RH9. Editran requires the OpenSSL package to be installed. With this change, the application is migrated to OpenSSL 3.0. * **ODEM-1036 Improvements in Editran/GC commands** √ **migra\_rsa** The command is modified to verify that the labels passed as arguments correspond to the stored key type (public or private). √ **gc\_config** It is modified to include a new option: generation of a new version of a local subsystem. √ **gc\_vclaves** Modify the command so that all arguments are optional, and in that case display the list of keys that match the filter. * **ODEM-1069 Session Parameters** For security reasons, the maximum allowed values for these Session fields are changed:" *time out"*, "*synchronization time out"* and *"maximum number of retries*. * **ODEM-1085 Improvement in Editran/GC menu** Key management from the menu **editrangc** has limitations that are modified to achieve better usability. Specifically, the option "*OWN KEY ASSOCIATION > EXPORT NEW KEY*" is changed in these aspects: √ Resending is allowed when the key status is "File Generated". √ When sending is chained, the Editran/G profile is modified to place the generated file in the list. √ The send request is changed to synchronous. It was being done without the *"wait"*. ## Issues and improvements v5.2.1.6 (November 2024) * **ODEM-1127 PSTRECGC Script** When the variable *GUpgrade* the script *PSTRECGC* sends an incorrect application to the program *insertgc\_r* which causes the failure in RSA key exchange. * **ODEM-1149 checkgc utility** A new utility is added that checks the keys of local subsystems and validates that the password is correct. * **ODEM-1156 Error in multi-session downloads** When receiving through a presentation configured with multiple sessions, an error occurs during the download. The error shown in the log is of the type: EDITRAN/P profile not found(\) * **ODEM-1168 + wildcard in reception destination path** Profiles with a reception destination using the '+' wildcard receive the files in a path different from the one specified. ## Issues and improvements v5.2.1.8 (June 2025) * **ODEM-1150** Improvement **Editran/GC key migration** The migration process now includes review of the private keys of Editran/GC. * **ODEM-1214 Error when migrating profiles with double hyphen in key labels** An error detected during migration of profiles with DES 3.0 cryptography and authentication that have a double hyphen in the key label is resolved. * **ODEM-1231 Exception 130 in receptions with IMS** Review of releases with exception 130. * **ODEM-1268 The minor version is specified in the startup logs of editranp and editrang** The full product version is shown in the startup logs of editranp and editrang. ## Issues and improvements v5.2.1.9 (November 2025) * **ODEM-1300 Does not validate the proxy feature in menup** Before allowing the user to enable the “proxy” option, the system must verify that the license includes that functionality. * **ODEM-1306 The EDItran script starts the license service without having a license file** On Linux, it must be checked that the license file exists before starting the license server. * **ODEM-1322 Incorrect conversion table parameter in receptions** In reception, the changes indicated in the local character conversion table were not being applied. * **ODEM-1336 Error calculating password in checkgc** The password calculation in the checkgc module had a memory leak. * **ODEM-1342 Error deleting the physical file of a remote key** Before deleting a remote key associated with a local code, the system must check that the key is not referenced by other local codes. * **ODEM-1352 Microsoft Visual C++ 2015-2022 (x86) - 14.44.35211 Redistributables** The product distribution includes the Microsoft Visual C++ 2015-2022 (x86) - 14.44.35211 redistributables ## Issues and improvements v5.2.1.10 (June 2026) * **ODEE-6071 Hostid identifies Microsoft Windows 11 Enterprise multi-session as Windows Server 2025** Microsoft Windows 11 Enterprise multi-session is based on server components. As a result, Editran incorrectly classifies Windows 11 Enterprise multi-session as Windows Server 2025. * **ODEE-6072 Migration to OpenSSL 3.5** Migration to OpenSSL 3.5 LTS. * **ODEE-6073 Migration of the license service to Java 21** The license service is migrated to Java 21. * **ODEE-6074 clock() overflow on Windows causes failure in SDL timers and connection retries** SDL timers stop working properly because the expiration conditions are not met and the completion signals are not generated, which prevents, among other effects, the execution of connection retries * **ODEE-6075 Microsoft Visual C++ v14 Redistributable (x86) - 14.51.36231** The product distribution includes the Microsoft Visual C++ v14 Redistributable (x86) - 14.51.36231 redistributables. * **ODEE-6143 Inclusion of the license.sh script** The script creates the file hostid\_dd-mm-yyyy.txt in the \/bin directory with the version data, the hostid identifier, and the license data. --- # 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.editran.onesait.com/documentacion-editran/open-v5.3-en/novedades/previas.md?ask=&goal= ``` `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.