Release 4.1.3

Latest release

This version includes many fixes and improvements.

NEW FEATURES

  • API Engine Improvements

The API Engine feature can now be executed using the update value action in all tools where the update value operation can be performed, such as ComboBox, Text Box, Graph, Dropdown List, etc.

In the API Engine process, multiple parameters can now be retrieved from the Parameter Query field within the action and sent as parameters to the CHILDDATASOURCE field in the API Request definition screen.

 

  • Netsis / SAP API Engine Operations

To perform operations with Netsis and SAP API services, the token and   parameters have been added to the Xpoda API Request screen.

  • Running with the API Engine Assistant

Operation with the API Engine Assistant has been enabled.

 

  • Dynamic Retrieval of Design Name in Print Action

Development has been carried out to dynamically retrieve the design name with $P in the print action. (SELECT $PDesignName$)

 

  • List Tool Dropdown Feature

A dropdown feature has been added to the list tool. This allows selections to be made using a dropdown within the cells of the list tool.

For a detailed example of how to use this feature, see:

Example 11 – List – Xpoda Support Center

 

  • User Menu Right Panel Feature

A right panel feature has been added to the user menu. This allows different menu screens to be opened while on the client screen.

  1. Button opens in the same tab feature
  2. Button opens in a new tab feature
  3. Button opens in the right panel feature

 

For a detailed example of how to use this feature, see: 

Client Menu Right Panel – Xpoda Support Center

 

  • Process of Retrieving Column Headers from the List Tool

In the list tool, a column name with a space in it was being taken without the space; with the new arrangement, the column name is taken in the same way.

Example = Column  >   User Name | Value Retrieval Format >  User Name

 

Note: In the List tool, field names retrieved from the query using the $P expression were written consecutively before version 4.1.3. However, starting with version 4.1.3, they must be written exactly as defined in the SQL query alias.

For example:

  • Before 4.1.3: $PProjectName


  • After 4.1.3: $PProject Name

Therefore, it is important to adjust domain names after the version update so that they are compatible with the alias used in the SQL query.

BUG FIXES

  • Kanban Template Issue

The progress bar, circular progress bar, and rating tools now work within the template in the Kanban tool.

 

  • Update Row in List Action Issue 

The Update Row in List action was not working with version 4.0, but the issue has been resolved.

For detailed information on updating specific rows in the list, see: 

Update Row in List – Xpoda Support Center

 

  • Radio Group Button Tool Action Not Working Issue

The Radio Group Button tool now performs the selected value action using the update value action.

 

  • Take Screenshot Action Issue

The issue with Turkish characters in files saved in PDF format using Action has been resolved.


  • API Request Details and Authentication Definition Issue 

When defining API Request Details and Authentication parameters, pressing Enter caused an issue with saving to the table. A 'Save' button added to the top right corner of the screen now ensures that all defined parameters are saved.

  • Button Group Linked List Feature Issue

When using the Linked List feature in the Button Group tool, the buttons were not visible in the List tool; this issue has been resolved.

 

  • Case Usage Error in Print Action

The ability to display different design files using the case when statement in the Print action has been enabled.

 

  • List Tool Auto Extension Feature Issue

When the Auto Extension feature was enabled in the List tool, it was not dragging the tools under the List tool downwards; the issue has been resolved.

 

  • List Tool Column Header Special Character Issue

When special characters were used in list tool column headers, data would not load into the list tool. This issue has been resolved.

 

  • List Tool User-Based View Save 

When the view saving process was performed for all users in the list tool, records were stored in the XPODA_VIEWS table. However, when the Save View operation was performed for the active user, issues arose during version transitions because the view was stored in cookies. With the new update, the active user's views are now also stored in the XPODA_VIEWS table. This prevents list tool views from being corrupted during version transitions.

Note: The above process will be active after the next version upgrade.