Release notes Thinkstore (2024.1)

Hello everyone,

As of this release, data verification is available in the Thinkstore instead of in the Software Factory. We have also enhanced the functionality for Trace fields, Logging data available in the GUI, and Active prefilter.

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

New, changed, and fixed in the Thinkstore models

Data verification moved to the Thinkstore

new

The base models SQLSERVER_VERIFICATION, ORACLE_VERIFICATION, and DB_VERIFICATION have been relocated to the Thinkstore. Previously, they were included in the initial installation of the Thinkwise Platform.

If you need an update for these models, download a new version from the Thinkstore.

Trace fields

We have converted the Trace fields functionality to align with the latest version of the Dynamic model.

new changed

• The script now uses a temporary table to identify the set of tables for which you want to generate the trace fields. This change significantly enhances the script's maintainability.
• The script now has settings at the top for the names of the trace columns. Note: If you change the name of a trace column, you must also adjust the template in the control procedure.
• The script now generates the tag automatically if it does not exist. Use this tag to exclude trace columns from a specific table.
• The script now creates the necessary domains automatically if they are not already present.
• The strategy is now set to Staged, which means trace columns are no longer deleted and re-generated when created.
• The insert user and insert datetime columns now have a default expression that automatically gets an insert from the database if you do not specify them. This change simplifies the insert statements.
• The DATETIME domain control now uses the Time zone setting Local to store the trace information in UTC format. You can manually adjust this in the scripts to store the DATETIME control as non-UTC. Note: if you are already using a DATETIME control and the script is not in charge of that domain (i.e., the Generated by control_proc_id is not the same as from the dynamic model trace_fields), this will not be set automatically.
• Instead of tsf_user(), we now use tsf_original_login() to represent who changed or inserted data, even when user simulation is used. See also User name.
• The template no longer sets the update trace functionality when adding a record. These lines are now in a comment. You can uncomment them if you wish to keep this functionality.
• Data sensitivity is now automatically applied to the add and update user columns. The data will be replaced by Added user and Updated user. This prevents showing user names to third parties. The date fields are set to Not sensitive. Data sensitivity is a setting at the top of the script; set it to 0 if you do not want it to be set automatically.
• We have introduced the Use for optimistic locking setting for the update_date_time trace field. This is a setting at the top of the script; set it to 0 if you do not want to use optimistic locking on the trace field.

fixed

• The missing commas in the template functionality, which caused the script to break, have been corrected.
• The length of the user_name domain is now set to 128 to match the tsf_original_login.

Logging data available in the GUI

new

New settings are available:

• Exclude trace cols - You can exclude 4 trace columns (by default, insert_user, insert_date_time, update_user, and update_date_time) if you prefer not to show them in your history views.
• view_suffix- Specify your desired suffix for the history view. Note: the suffix cannot be _history as this is reserved for temporal tables. Previously, it could be a prefix or suffix, but now only a suffix is allowed.
• show_as_detail - Indicate whether the history should be shown as a detail of the subject. Set it to 0 if this is not required.
• setup_roles- Set up roles based on the base tables.
• force_recompile_extended_property_id - In the views, the query hint "Use force recompile" is used now. This hint is beneficial when the view is used as a screen in your application. SQL server uses it to optimize the query plan.

changed

• We have updated the names of the generated views to history_overview to align them with our naming guidelines.
• In addition to the regular primary keys, we have added valid_from and valid_to as primary keys to the generated views.
• We have changed the default sort order to only sort based on the valid_from and valid_to columns.
• Optimistic locking has been deactivated for all columns in the generated views.
• The use of handlers has been disabled for the generated views. Previously, this information was derived from the base table for which the view was generated.

fixed

• The naming of the created references was not always correct. This has been adjusted.
• The column generated_by_control_proc_id was not correctly filled in every place. Note: when this model causes generation errors, update the objects with the correct generated_by_control_proc_id or remove the existing views and generate them again.
• The value of the conditional layout has been changed from grid_order_no to abs_order_no since the abs_order_no is always unique within the table.

Active prefilter

new changed

We have revised the code for creating active prefilters.

This dynamic model is based on the strategy Delete because it only assists in creating prefilters and does not maintain them. Once the prefilters are created, you can modify their settings without being overwritten by the dynamic model.

• Settings in the scripts are available for adjustment to your preferences.
• It is now possible to use an icon. First, upload it to the icon table.
• A tag is now available to exclude a prefilter from a table. If you add the tag when the prefilter has already been added, you must manually delete the prefilter.
• The prefilter is now column-based instead of query-based.
• You will no longer get a prefilter for generated tables (for example, history views).

Questions or suggestions?