New configuration for Tekla Platform partners

A new Tekla Platform configuration has been added for Tekla Platform partners.

To start using the new configuration, make these changes in your environment.

If you use a bypass.ini file to define the default license when you start Tekla Structures, add the following line to the file:
```
rem set XS_DEFAULT_LICENSE=PLATFORM
```
Update the Tekla Structures version number in paths to TeklaStructures.exe, bypass.ini, and user settings files.

Licensing improvements

To help users to resolve licensing issues independently so that they can continue working as fast as possible, these licensing improvements have been made.

A message is now shown to users when Tekla Structures cannot start because of clock inaccuracy. If time synchronization settings are managed at the organization level in your company, ensure that the time zone, UTC time, and local time are consistent with each other for all users. For more information, see Tekla Structures cannot start because of clock inaccuracy.
Previously, after updating from Windows 10 to Windows 11, or installing some other Windows updates, some subscription licenses were no longer available or Tekla Structures did not start. Tekla Structures licenses are now more stable after Windows updates.

Changes in the Inquire Cast Unit report

In the Inquire Cast Unit report, the Parts listing has been changed to show PART_POS instead of ASSEMBLY_POS in the first column. The default sorting direction has also been changed to ascending.

If you use a custom copy of TS_Report_Inquire_Cast_Unit.rpt, update the file.

Replace ASSEMBLY_POS with PART_POS.

Before:

formula = "GetValue(\"ASSEMBLY_POS\")";

After:

formula = "GetValue(\"PART_POS\")";

Change the value of sortdirection to ASCENDING.
Before:
```
sortdirection = NONE;
```
After:
```
sortdirection = ASCENDING;
```

Flange slope ratio added to UPN profiles

UPN profiles in the default environment now have a flange slope ratio defined.

This change fixes problems when using components, such as stiffeners with bad shape.

If you use a custom profile catalog, add a flange slope ratio for each UPN profile, depending on the size:

For UPN 300 and smaller: 0,08
For UPN320 and large: 0,05.

Improved visualization for non-foldable and broken chamfers

The visualization for non-foldable and broken chamfers in the model view has been improved.

When the XS_DRAW_CHAMFERS_HANDLES advanced option is set to CHAMFERS, non-foldable and broken chamfers are shown in the model view as follows:

Non-foldable chamfers are shown in yellow. Whether a chamfer is non-foldable depends on the plate thickness and the chamfer parameters. An example of a non-foldable chamfer is a square chamfer that is too tight to fit a curve into.
If the solid cannot be created for the polybeam, all the chamfers are shown in red. Only stick representation is shown for the part in the model view.

The default value of the XS_DRAW_CHAMFERS_HANDLES advanced option is HANDLES. Check the value of the XS_DRAW_CHAMFERS_HANDLES advanced option in your environment and update it if needed.

Changes to UDA tabs and default values

A Structural Information UDA tab was added for items and concrete items in the common environment. The default values of all drop-down lists on the tab are now empty.

Previously, the default values were set to a specific value. For example, the default value for the Load bearing drop-down list was No.

Note: If you open a model that was created with a previous Tekla Structures version in Tekla Structures 2024, option attributes that have a value other than the default show an incorrect value.

If you do not use the objects_structural.inp file or the IfcPropertySetConfigurations.xml files from the common environment, update your custom files for these changes.

Add these lines to your objects_structural.inp file:

/***************************************************************************/
/* Item (BREP) attributes                                                  */
/***************************************************************************/
item(0,"j_Item")
{
 tab_page("StructuralInformation","jd_StructuralInformation",15)
 modify(1)
}

/***************************************************************************/
/* Concrete item (BREP) attributes                                         */
/***************************************************************************/
concrete_item(0,"j_Concrete_Item")
{
 tab_page("StructuralInformation","jd_StructuralInformation",15)
 modify(1)
}

In your objects_structural.inp file, move Unset to be the first value in the option attributes for drop-down lists on the StructuralInformation tab.

Before

tab_page("Structurallnformation")
{
    attribute("REF_ID”, "j_user_ref_id", string, ”%s", no, none, "0.0", ”0.0")
    {
        value("", 0)
    }
    attribute("RENOVATION_STATUS", "j_RGnovation_status", option,"%s", no, none,”0.0", "0.0"
    {
        value("j_New", 0) 
        value("j_Existing", 0) 
        value(”j_Demolish”, 0) 
        value(”j_Temporary”, 0) 
        value("j_Other", 0) 
        value(”j_Unknown", 0) 
        value("j_Unset, 2)
    }
    attribute(”IS_EXTERNAL", "j_Is_external", option,"%s", no, none,"0.0", ”0.0")
    {
        value("j_No", 0) 
        value("j_Yes", 0) 
        value("j_Unset", 2)
    }

After

tab_page("Structurallnformation")
{
    attribute("REF_ID”, "j_user_ref_id", string, ”%s", no, none, "0.0", ”0.0")
    {
        value("", 0)
    }
    attribute("RENOVATION_STATUS", "j_RGnovation_status", option,"%s", no, none,”0.0", "0.0"
    {        
        value("j_Unset, 2)
        value("j_New", 0) 
        value("j_Existing", 0) 
        value(”j_Demolish”, 0) 
        value(”j_Temporary”, 0) 
        value("j_Other", 0) 
        value(”j_Unknown", 0) 
    }
    attribute(”IS_EXTERNAL", "j_Is_external", option,"%s", no, none,"0.0", ”0.0")
    {
        value("j_Unset", 2)
        value("j_No", 0) 
        value("j_Yes", 0) 
    }

Check the default values in your custom IfcPropertySetConfigurations.xml files and update them if needed.

Prevent the copying of UDAs from the cutting part to the cut part

You can now use the XS_PART_CUT_INHERIT_UDAS_FROM_CUTTING_PART advanced option to prevent user defined attributes (UDAs) from being copied to the cut part when using the Part cut command.

When the value of the XS_PART_CUT_INHERIT_UDAS_FROM_CUTTING_PART advanced option is FALSE, the Part cut command does not copy UDAs from the cutting part to the cut part.

The default value of the XS_PART_CUT_INHERIT_UDAS_FROM_CUTTING_PART advanced option is FALSE.

Finish field in Floor Layout tool

You can now define the Finish property for layer parts on the Layer tab of the Floor Layout tool.

Update your attribute files if you want to use the new property.

New objects supported in Drawing property pane

New object types are available in the Drawing property pane.

Some previous attribute files, such as Symbol.txt and RevisionMark.txt, might not work properly.

Test these new object types and attribute files.

For example, create a symbol, select it, and load a new attribute file.
If the attribute file does not work properly, update the attribute file.

Configuration file for Multi-report generator

Multi-report generator is added as extension in environment installers.

The MultiReportGenerator.inp configuration file for filtering reports can be localized. An example MultiReportGenerator.inp file is included in the default environment.

Example MultiReportGenerator.inp file

|
Excel|excel
ID|ID
IFC|IFC
Inquire report|Inquire
PDF|PDF
TeklaPowerFab|TeklaPowerFab

Tekla Structures searches for the MultiReportGenerator.inp file in the folders defined by the XS_PROJECT, XS_FIRM, and XS_SYSTEM advanced options.

Create a MultiReportGenerator.inp configuration file in your environment.

The syntax is: [Visible text] | [String found in name of the report]
Example MultiReportGenerator.inp file
```
|
Excel|excel
ID|ID
IFC|IFC
Inquire report|Inquire
PDF|PDF
TeklaPowerFab|TeklaPowerFab
```
Save the file in a folder that is specified in the XS_SYSTEM advanced option.

Enhancements in the Management Console for Tekla Model Sharing

If you are an administrator in the Management Console for Tekla Model Sharing, these new enhancements help you to manage your organization's shared models more precisely and efficiently.

Default model data storage location

You can now select the default model data storage location for shared models in your organization. The default model data storage location defines the region where Tekla Model Sharing model data is stored

The default location is automatically selected as the model data storage location when users share a model. Users can only select a different model data storage location if you allow them to do so.

For more information, see Manage organization settings in the Management Console.

Advanced filtering

You can now define advanced filter criteria in the Management Console for Tekla Model Sharing to more precisely search for users and models.

For more information, see Introduction to the Management Console user interface.

Set user/role for multiple models

The Management Console for Tekla Model Sharing now has an action to add a user to multiple models at the same time.

For example, if the previous owner of several shared models leaves the company, you can add a user as a new owner for all of that user's shared models.

For more information, see Manage users in shared models in the Management Console.

Administrator's release notes: Miscellaneous general improvements