Hello everyone,

As of this release, we have introduced several new solutions to the Thinkstore. Furthermore, we have restructured and enhanced a large number of other solutions.

Contents

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.

New and changed in the Thinkstore models

Standard http queue with system flow (API)

new

We have introduced a new solution in the Thinkstore: Standard http queue with system flow (API). This solution provides a queue table with all the input and output variables of a HTTP connector process action.

A system flow executes HTTP calls and stores the response data into the table. This allows both users and the system to process the retrieved information.

Columnstore index and AI search

new

This new solution contains an example of how to use a columnstore index in the Software Factory, combined with AI search.

The data model consists of a product table that can compare itself to other products within that table and provide a matching score. A higher score indicates that the product is more similar to the selected product.

The columnstore index ensures that this functionality is extremely fast. Columnstore indexes store data by column instead of row, offering significant data compression and reducing storage needs. This leads to faster queries because less data is accessed during query execution.

• More general information about columnstore indexes: Microsoft
• More information about columnstore indexes in the Software Factory: Indexes

Add index temporal table

change

The model Add index temporal table has been changed because of the introduction of the Non-clustered (history) index in the Software Factory.

Add index temporal table now contains a dynamic model. When the tag add_history_index is added to a table, the dynamic model creates an index on the history table based on the primary key of the original table.

This index helps when you have included the Thinkstore solution Logging data available in the GUI in your model or when you query your history table with the original primary key.

Email system flow

change

The Email system flow has been completely restructured for improved efficiency and reliability. This update streamlines email handling and ensures a more scalable and robust solution for managing email workflows.

Key changes include:

• New email table: We have introduced an email table with a status field, serving as a queue table for email processing.
• Background process: A new system flow, email_read_next_queue_id, has been implemented to manage queued emails. It identifies and picks up the next email to be sent automatically.
• Subflow execution: The system flow triggers a subflow that sends emails using the Email connector.

Maps and Routes

change Universal GUI

The models Maps (mymappi) and Google Maps have been merged into a new model named Maps and Routes. This new model serves the purpose of teaching how to work with the Maps component in the Universal GUI. It also uses two Web connection endpoints for retrieving the GPS coordinates and routes.

The model includes a menu for addresses and routes:

• Adding an address initiates a process flow that uses the Web connection to retrieve and display the GPS coordinates on the Maps component.
• Once you have at least two addresses, you can add a route. The Web connection retrieves and displays the fastest route on the Maps component.

Renamed 'Using OAuth to get data from external applications'

change

The model Using OAuth to get data from external applications has been renamed to Using OAuth to get data from Exact Online. In addition:

• The MS Graph connection has been removed. This will be a separate Thinkstore model.
• Instead of an HTTP connector, a Web connection is now used.

Default tooltip

change

The model Default tooltip has been updated:

• The generation strategy has been changed to Fully Controlled.
• The code has been changed so the trace columns are updated.
• The code has been changed so the tooltip translation is also updated when the translation is updated.

Make sure your display values are unique

change

The generation strategy has been changed to Staged.

Turn off enable tab task when empty

change

• The generation strategy has been changed to Fully Controlled.
• The code has been changed to a where not exists.
• The code has been changed to create the tag when it does not exist yet.

Find a certain char in a string

change

We have added a table valued function so the functionality will be easier to use.

Generate a unique randomized token

change

We created a subroutine (procedure) for the functionality. Previously, it was only an example script.

Thinkwise Guideline Validations

change

• We renamed the validation column_name_starts_with_the_table_name to tsf_guideline_column_name_starts_with_the_table_name. This is to be in line with the rest of the naming of the validations.
• In the validation tsf_guideline_column_name_starts_with_the_table_name, the like missed the '%', this has been corrected.
• tsf_guideline_domain_which_contains_the_name_of_an_rdbms_datatype now only checks for the RDBMS type of the model.
• All the validations that use a cursor with a table variable have been changed to a temporary table to improve performance and stability. See this Community post.

Check constraint for easy user input validation

change

We changed the strategy for the meta control procedure "check_constraint_message_add" from delete to staged.

For more information about the custom check constraints, see the blog Check constraints using the Software Factory.

Difference in data between two databases

change

We removed unnecessary parts of the model, reducing the size of the export file model.dat, without any other changes.

Friendly error msg for databaseconnector

change

We changed the strategy for the meta control procedure database_connector_process_action from delete to fully controlled. We also modified the insert statement for the table process_action_output_parmtr to include the column output_parmtr_type with a value of fixed_option.

We changed the strategy for the control procedure error_log_code from delete to staged. We also removed the parameter @error_log_code from the error handling code in the template error_log_code, as it was not declared.

Date prefilters

change

Previously, this model included a table named date_of and a prefilter group called date_filters with 4 prefilters. Now, it only contains a meta control procedure tab_date_prefilter that adds the prefilter group and prefilters to all tables linked with the tag tab_date_prefilter. In the tag value, you must specify a column with a domain of data type DATE, DATETIME, or DATETIME2.

The 5 prefilters created are:

• Current week
• Year to date (new compared to the previous model)
• Current month
• Current quarter
• Current year

These prefilters can be adjusted within the dynamic code if you desire more or fewer prefilters, or if you wish to modify any details of the prefilters. We set the strategy for the meta control procedure tab_date_prefilter to fully controlled, giving you the freedom to change the details after creation. Note that changes to the dynamic code will not modify the already created prefilters.

The model includes a menu for addresses and routes.

• Adding an address initiates a process flow that uses the web connection to retrieve and display the GPS coordinates on the maps component.
• Once you have at least 2 addresses, you can add a route. The web connection will then retrieve and display the fastest route on the maps component.

Questions or suggestions?