Release notes Thinkstore (2024.2)

Hello everyone,

In this release, we have improved a couple of models and removed models that had become obsolete.

About the Thinkstore

The Thinkstore is a fully integrated way for downloading and installing ready-made solutions directly into your models right from the Thinkwise IDE.
It contains a collection of scripts and samples to help you get the most out of the Thinkwise Platform.
You can find the Thinkstore in the Software Factory, in the menu Enrichment > Thinkstore.

You can read more about the Thinkstore in the Thinkstore guide.

Contents

Improved

Improved the model Logging data available in the GUI

change

We have updated the Thinkstore model Logging data available in the GUI to improve performance and readability.
The control procedure that generates tables, columns, and references no longer uses temporary tables.
It now uses staged tables.

Improved the model "Trace tasks"

change

We have made the following changes:

• Adjusted the dynamic model "Trace tasks" to be fully controlled.
• Added "where not exists" to the columns.
• Changed that the table and columns are no longer set as "generated".
• Changed the strategy to "Staged".
• Changed the order of the assigning. We now weave the functionality into the program object in step 3 instead of step 2.
• If a task has a transaction, the code is now within the transaction.

Improved the model "Illegal XML characters"

change

We have made the following changes:

• Adjusted the dynamic model "Illegal XML characters" to be fully controlled.
• Added "where not exists" to the subroutine and parameters.
• Changed that the subroutine is no longer set as "generated".
• Changed the strategy to "Staged".

Improved the model "Facts"

change

We have added roles for each base table to the model "Facts". We have also created unique indexes for the names per table.

Improved the model "Logging data available in the GUI"

new change

In the model "Logging data available in the GUI", we have created the needed domains in case they are not yet in the model via the dynamic model code.
We have also added the following fixes:

• There was an issue with the row_number when determining the conditional layout code values. This has been fixed.
• If the total length of combined tab_ids exceeds 1000, the extended property will now give an error since this column is a varchar(1000).
• If there is a reference on the computed column, the ref was deleted from #ref but not #ref_col, which would give an error. This has been fixed.

Improved the model "Auto create a function for system versioning"

change

For the model "Auto create a function for system versioning", we have made the following improvements:

• Changed the dynamic model strategy to 'staged'.
• Added the creation of the domain.
• Aligned the code with our Code guidelines.
• Changed the control_procedure strategy to 'staged'.

Improved the model "Working with dates in SQL"

change

For the model "Working with dates in SQL", we have made the following improvements:

• Revised the table and removed some columns.
• Changed the control procedure to 'staged' so the assigning will be done automatically.
• Changed the code for the insertion of the date_helper to be able to update and insert new records where needed.
  Note: Feel free to add extra columns and functionality where needed, for example:
  is_working_day / production_week / number_of_days_in_month
  This is merely a first setup for a date_helper table.

Improved the model "Getting domain elements in SSMS shortcut"

change

We have made the following improvements to the model "Getting domain elements in SSMS shortcut":

• Changed the control_procedure strategy to 'staged'.
• Changed the dom_id domain to varchar(128) (was 200) to be aligned with the dom_id of the Software Factory.
• Changed the template with all the domains to contain elements from the Software Factory instead of checking IAM, which is not desirable and costs more performance.

Improved the model "Extract a file name from a file path"

We have made the following improvements to the model "Extract a file name from a file path":

• Added 2 domains and a function.

   

• Changed the control procedure strategy to 'staged'.
• Added 2 unit tests.
• Fixed that an error would occur when a file path without a backslash ('') was given as input.

Improved the model "Translating model objects in business logic"

We have made the following improvements to the model "Translating model objects in business logic":

• Added the function get_dom_elemnt_id to be able to retrieve the element_id of a domain value.
  For example: order_status with database value 1 can be retrieved with select dbo.get_dom_elemnt_id('order_status',1).
• Added some more examples of type_of_objects in the control procedure code.

Combined and improved the models "Convert UTC marked dates to locale dates" and "UTC and local time conversion"

change

We have merged the models "Convert UTC marked dates to locale dates" and "UTC and local time conversion" into one model.
The resulting model has only one function, with an input date time, from_time_zone, and to_time_zone.
This way, you are flexible in how you use the function.
When you are always in the same timezone, you could create your own function:

convert_local_to_utc
convert_utc_to_local

You can then define your own timezone as convert_local_to_utc and convert_utc_to_local.

Removed

Removed the model "Auto refresh"

change

We have removed the model "Auto refresh". Auto refresh can be done by an extended property.
For more information, see the Extended properties,
RefreshOnDocumentSwitch and RefreshOnTabSwitch.

Removed "Auto generate reports"

change

We have removed the model "Auto generate reports".
In version 2022.1 of the Thinkwise Platform, we introduced the generate report connector. See Generate report.

This connector covers the functionality of the model that was removed.
Connecting it to a write file / SMTP connector is explained in this Community post.
Use these resources for creating a system flow.

Removed the model "Knowledge application"

change

We have removed the model "Knowledge application" from the Thinkstore.

Removed the model "Change detection"

change

We have removed model "Change detection". The documentation has the same example: https://docs.thinkwisesoftware.com/docs/sf/business_logic#change-detection

Removed the model "Replace HTML font family"

change

The model "Replace HTML font family" is outdated and no longer relevant, so we have removed it.

Removed the model "Change font of html fields from Segui ui to Arial"

change

We have removed the model "Change font of html fields from Segui ui to Arial". This model did not add anything functional. It only replaced a tag with another span tag that included a font in HTML.

Removed the model "Session variables"

change

We have removed the model "Session variables".
See the documentation for how to use the session variables:
Extended properties
Generated session variables
https://learn.microsoft.com/en-us/sql/t-sql/functions/session-context-transact-sql?view=sql-server-ver16

Removed the model "Default error handling on SQL Server"

change

We have removed the model "Default error handling on SQL Server" because the Software Factory handles the most common errors with atomic transactions.
See the documentation:
Atomic transactions
Weave code into atomic tasks

Removed the model "Drag and drop between subjects example"

change

We have removed the model "Drag and drop between subjects example" which demonstrated drag and drop between subjects.
In version 2024.2 of the Software Factory, an enrichment is available to create a drag-and-drop task between two subjects.
See Available model enrichments.

Fixed

Fixed the model "SAP API stock, consumption and production booking"

fix

We removed broken prefilters from the model "SAP API stock, consumption and production booking" and fixed some broken prefilter queries missing the t1. prefix.

Fixed the model "Multi lang data"

fix

We have changed the error handling. Before, if the table was not in the model, there would be an error.
Now, the code will not be executed in that case.

Questions or suggestions?