UBIK Wiki / Augmensys - User contributions [en]

Import Runs

2025-11-25T13:29:38Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Blinding Operation Import =

To import Blinding Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* BlindingLocation (Text)
* Type (Text)
* BlindingPackage (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* Joint_Location_Number (Text)
* Name (Text)
* Remark (Text)
* Tag_Number (Text)
* Gasket_Type (Text)
* Flange_Spec (Text)
* Flange_Size (Text)
* Flange_Rating (Text)
* Bolt_Size (Text)
* Bolt_Number (Text)
* Bolt_Material (Text)
* Torque_Value (Text)
* Pressure (Text)
* Assembled_By (Text)
* Assembled Date (TT/MM/JJJJ hh:mm)
* Inspected_By (Text)
* Inspected_Date (TT/MM/JJJJ hh:mm)
* Equipment (Text)

= Blinding Location Import =

To import joint locations following columns are required:
* BlindingLocation_ID (Text)

Columns that can be imported additionally:
* No (Text)
* Equipment (Text)
* SOP (Text)
* Description (Text)
* BlindingNumber (Text)
* PID (Text)
* Size (Text)
* Type (Text)
* LocationType (Text)
* NormalPosition (Text)
* OnSite (Text)
* ICCNumber (Text)
* BlindSapNumber (Text)
* BlindQuantity (Number)
* GasketSAPNumber (Text)
* GasketQuantity (Number)
* Stage (Text)
* Height (Text)
* Scaff (Text)
* Insul (Text)
* Crane (Text)
* Remarks (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-25T13:24:42Z

DAK:

Import Runs

2025-11-17T14:22:58Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* Joint_Location_Number (Text)
* Name (Text)
* Remark (Text)
* Tag_Number (Text)
* Gasket_Type (Text)
* Flange_Spec (Text)
* Flange_Size (Text)
* Flange_Rating (Text)
* Bolt_Size (Text)
* Bolt_Number (Text)
* Bolt_Material (Text)
* Torque_Value (Text)
* Pressure (Text)
* Assembled_By (Text)
* Assembled Date (TT/MM/JJJJ hh:mm)
* Inspected_By (Text)
* Inspected_Date (TT/MM/JJJJ hh:mm)
* Equipment (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-17T14:22:32Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Joint Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

[[Category:MaTaP|Import Runs]]

Import Runs

2025-11-17T14:17:48Z

DAK:

Import Runs

2025-11-17T14:17:39Z

DAK:

= Equipment Import =

To import Equipments following columns are required:
* EquipmentID (Text)

'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!

Columns that can be imported additionally:
* PIDNumber (Text)
* Medium (Text)
* System (Text)
* SystemDescription (Text)
* PlanNumber (Text)
* GridCode (Text)
* Location (Text)
* LocationStage (Text)
* LocationHeight (Text)
* Plant (Text)
* Tag_Nr (Text)
* EquipmentDescription (Text)
* Maint_Plant (Text)
* AssistingSystem1 (Text)
* AssistingSystem2 (Text)
* Subsystem (Text)
* SubsystemDescription (Text)
* Zone (Text)
* CoordinateLong (Number)
* CoordinateLat (Number)
* CoordinateAltitude (Number)
* PrioritySAP (Text)
* EquipmentType (Text)
* EquipmentGroup (Text)

= Workorder Import =

To import WorkOrders following column is required:
* Workorder (Text)

Columns that can be imported additionally:
* EquipmentID (Text)
* Description (Text)
* WBS (Text)
* Comment (Text)
* Longtext (Text)
* DrainlistDocument (Text)

Following columns are optional, as we recommend to import them directly using the Equipment.import instead:
* EquipmentType (Text)
* EquipmentGroup (Text)

= Progress Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= QRF Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* QRFKey (Text)
* QRFDescription (Text)

= Blinding Operation Import =

To import Blinding Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* BlindingLocation (Text)
* BlindingPackage (Text)
* Type (Text)

= Joint Operation Import =

To import Joint Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)
* JointLocation (Text)

= Check Operation Import =

To import Operations following columns are required:
* OperationID (Text)

'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* Workorder (Text)
* Operation (Text)
* ShortText (Text)
* Number (Number)
* NormalDuration (Number)
* NormalDurationUnit (Text)
* Work (Number)
* WorkUnit (Text)
* Workcenter (Text)
* ActivityCode (Text)
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)
* Company (Text)
* CompanyCode (Text)
* LongText (Text)
* Comment (Text)
* PermitCode (Text)
* Planner (Text)
* Suboperation (Text)

= Scheduling Import (for Operations)=

To import scheduling data of Operations the following columns are required:
* OperationID (Text)

'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!

Columns that can be imported additionally:
* eStart (TT/MM/JJJJ hh:mm)
* eFinish (TT/MM/JJJJ hh:mm)
* lStart (TT/MM/JJJJ hh:mm)
* lFinish (TT/MM/JJJJ hh:mm)

= User Import =

To import users following columns are required:
* DesktopLogin (Text)

Columns that can be imported additionally:
* Name (Text)
* NFC (Text)
* MobileLogin (Text)
* Password (Text)
* CompanyCode (Text)
* ReportingUserrights (Text)
* PunchpointUserrights (Text)
* ScopechangeUserrights (Text)
* SuperuserUserrights (Text)
* Comment (Text)
* Position (Text)
* Availability (Text)
* Adress (Text)
* Skype (Text)
* Telephone (Text)
* Email (Text)

= Company Import =

To import companies following columns are required:
* CompanyCode (Text)

Columns that can be imported additionally:
* Company (Text)

= Material Import =

To import materials following columns are required:
* OperationId (Text)
* MaterialNr (Text)

'''NOTE:''' “Quantity” must be formatted as Number!

Columns that can be imported additionally:
* MaterialDescr (Text)
* BOMItemNr (Text)
* ItemCategory (Text)
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!
* Quantity (Number)
* Unit (Text)
* ReservationStatus (Text)

= Preparation Document Import =

To import materials following columns are required:
* Workorder (Text)
* FilePath (Text)

Columns that can be imported additionally:
* FileName (Text)

= Blinding Location Import =

To import Blinding Locations following columns are required:
* BlindingLocationID (Text)

Columns that can be imported additionally:
* No

= Joint Location Import =

To import joint locations following columns are required:
* Joint_ID (Text)

Columns that can be imported additionally:
* No
* Equipment
* SOP
* Description
* BlindingNumber
* PID
* Size
* Type
* LocationType
* NormalPosition
* OnSite
* ICCNumber
* BlindSapNumber
* BlindQuantity
* GasketSAPNumber
* GasketQuantity
* Stage
* Height
* Scaff
* Insul
* Crane
* Remarks

[[Category:MaTaP|Import Runs]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:49:12Z

DAK: /* Enhanced Instance Data Transfer */

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =
== Enhanced Instance Data Transfer ==
Since Version 5.0.0 the Instance Data Transfer has been enhanced.
* The Instance Data Transfer now supports transfers from any source database (version 3.7 or later).
* Instances that have changed in the source system since the last transfer will be updated in the target system when performing a new transfer.

A detailed description of how to transfer data from an {{UBIK}} 3 environment to an {{UBIK}} 4 is provided in the "Transfer Data from UBIK 3 to UBIK 4" tab.

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:49:00Z

DAK: /* Enhanced Instance Data Transfer */

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:47:49Z

DAK: /* Enhanced Instance Data Transfer */

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =
== Enhanced Instance Data Transfer ==
Since Version 5.0.0 the Instance Data Transfer has been enhanced.
* The Instance Data Transfer now supports transfers from any source database (version 3.7 or later).
* Instances that have changed in the source system since the last transfer will be updated in the target system when performing a new transfer.

A detailed descriptition on how to transfer data from an {UBIK 3} environment to an {UBIK 4} is provided in the "Transfer Data from UBIK 3 to UBIK 4" tab.

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:47:15Z

DAK: /* Enhanced Instance Data Transfer */

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =
== Enhanced Instance Data Transfer ==
Since Version 5.0.0 the Instance Data Transfer has been enhanced.
* The Instance Data Transfer now supports transfers from any source database (version 3.7 or later).
* Instances that have changed in the source system since the last transfer will be updated in the target system when performing a new transfer.

A detailed descriptition on how to transfer data from an {{UBIK 3}} environment to an {{UBIK 4}} is provided in the "Transfer from UBIK 3 to UBIK 4" tab.

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:41:17Z

DAK: /* General */

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =
== Enhanced Instance Data Transfer ==
Since Version 5.0.0 the Instance Data Transfer has been enhanced.
* The Instance Data Transfer now supports transfers from any source database (version 3.7 or later).
* Instances that have changed in the source system since the last transfer will be updated in the target system when performing a new transfer.

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T13:37:48Z

DAK: /* General */

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =
Since Version 5.0.0 the Instance Data Transfer has been enhanced.
* The Instance Data Transfer now supports transfers from any source database (version 3.7 or later).
* Instances that have changed in the source system since the last transfer will be updated in the target system when performing a new transfer.

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

HowTo:Transfer Data from UBIK 3 to UBIK 4+

2025-06-05T12:48:51Z

DAK:

With {{UBIK}} Server version 4, much has changed on database level. We had to sacrifice direct downward compatibility with respect to older database versions in order to gain new possibilities (see [[Dynamic_Live_Mode]]).

In order to upgrade a {{UBIK}} Environment from version 3.7 to version 4, it is necessary to create a new database and to transfer the data from the old database to the new one. Here's how.

{{Template:HowTo/Begin}}

= General =

= Transfer Data from UBIK 3 to UBIK 4 =


== Save all meta definitions to a SmartStudio Project ==
* Make sure the database is updated to 3.7.3 (recent fixes in uids require a database update to this version)
* If you don't need the CUI plugin, delete all meta classes related to CUI from your 3.7 database before continuing. The same is true for any other structure or content you don't want transferred.
* Make sure your SmartStudio version 3.7 has all the plugins required for your project.
* Open SmartStudio version 3.7.
* Open a new, empty Project.
* Connect to the old {{UBIK}} 3.7 Environment.
* Open a new Transport Container worksheet.
* Right-click to open the context menu and click "Load all MetaClasses".
=> Now, all MetaClasses and MetaProperties are added to the Transport Container. This can take a while.
* After loading all the meta definitions is finished, save the Transport Container to the Project.
* Save the Project to the file system.

{{Hint|Make sure to use the newest SmartStudio versions from the release portal (also for 3.7)!}}

== Create an empty {{UBIK}} 4.0 database ==
* Create a new, empty database for your {{UBIK}} 4 Environment. It has to be on the same server as your old database (or a copy thereof).
* Make sure your SmartStudio version 4 has all the plugins required for your project.
* If you haven't removed the CUI meta classes from your 3.7 database before loading the meta classes into the SmartStudio project, you also need the CUI plugin.
* Open SmartStudio version 4.
* Open the previously created Project.
* Connect to the new (and empty) {{UBIK}} 4 Environment.
=> SmartStudio now asks you to upgrade the empty database to version 4. Confirm the upgrade dialog. {{UBIK}} now creates all the basic system definitions in the previously empty database.

{{Hint|You might get an MSDTC related error. In that case you need to enable the MSDTC: https://learn.microsoft.com/en-us/biztalk/adapters-and-accelerators/adapter-sql/configure-msdtc-on-sql-server-and-adapter-client}}

== Transfer the previously copied meta definitions ==
* Open the Transport Container with all the 3.7 meta definitions from the Project.
* Merge & Save the Transport Container to the Environment.
=> All the meta definitions should be available in the new {{UBIK}} 4 Environment. Now we just have to transfer the instance data.

{{Hint|Known issue: SmartStudio assumes the relation data meta class of a relation has the same name. If the relation was renamed (but not the data meta class), a new data meta class with the same name will be created for the relation. In that case, you might have to set the correct data meta class after the transfer (all meta classes are transferred, just the reference might be wrong). The new data meta class with the same name as the relation can be deleted then.}}

{{Hint|Known issue: SmartStudio doesn't know about the Meta Property's "Serialize" property, which adds an additional column for file references. After migrating the meta definitions to your {{UBIK}} 4 Environment, please set this property to true manually if needed. }}

== Remove obsolete MetaClasses ==
* Some old meta classes have been transferred, but we can just delete them:
** System.Main.SYSTEMSETTINGS

== Make sure all languages are configured ==
* Open the Bulk Editor for the Language Meta Class (using SmartStudio or regular Studio) in your new 4.0 Environment.
* Enter all required languages (if you had more than 2).
* It is only important that there are enough languages, you can modify them afterwards.
=> Now, there should be as many languages as there were in the old 3.7 Environment.

== Transfer all instance data ==
* Open the "Instance Data Transfer Wizard" using the "Environment" menu.
* Follow the wizard's instructions until the end.
=> The wizard copies all the instance data from the old 3.7 Environment to the new {{UBIK}} 4 Environment.

{{Hint|If the transfer keeps failing after some time, the maximum transaction timeout configured on your machine might be the issue: https://stackoverflow.com/a/21274884 or https://thecodesaysitall.blogspot.com/2012/04/long-running-systemtransactions.html }}

== Maintain languages ==
* All languages have been transferred from the old 3.7 Environment.
* Now, there might be duplicate entries.
* Remove all language objects you don't need and make sure the details (index, primary language) are set correctly.
=> Now, all translations should be displayed correctly; please check.

== Optional: Maintain customizing ==

In case your customizing doesn't compile even after removing the obsolete meta classes, this might help.

* Copy your custom code library from your old DB to the new one.
* If a class cannot be found, please make sure it doesn't have the namespace "System". Alternatively, you can use "Sys." as a prefix in the custom code to find the class.

Also, some method signatures have changed, so we have to adapt custom code if these methods are used:

* For most View related methods, the parameter "bool sorted" does not exist anymore; it can be removed.
* The UBIKClassList does not derive from List anymore. If you're using it as List in your custom code, you have to adapt this, using UBIKClassList instead.

If you're stuck, please ask a developer.

== Optional: Maintain system object customizing ==
Most likely, you won't need to do anything here, but if you changed system meta objects in your old 3.7 Environment, additional adaptions might be necessary.
* In the unlikely event that there were custom changes to system objects like the NAMEDBASECLASS, please check whether anything is missing.
* Custom property values or relations must be amended manually.
* Custom code and icon can be restored by linking to the correct Display Data object, which was transferred.
* Ask a developer if you need help.

{{Template:HowTo/End}}

[[Category:How-To|Transfer Data from 3.7 to 4.0]]
[[Category:Install|Transfer Data from 3.7 to 4.0]]
[[Category:Installing|Transfer Data from 3.7 to 4.0]]
[[Category:Server|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.0|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.2|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.3|Transfer Data from 3.7 to 4.0]]
[[Category:Version 4.4|Transfer Data from 3.7 to 4.0]]

Version 4.9.0 (Server)

2025-05-07T14:35:57Z

DAK: /* Hot fixes */

= Kernel (initial release)=
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.

= Hot fixes =
Version 4.9.0.???? on 2025/0?/??:
* Importing of MATAP data containing empty strings does not result the Proxies having an import status of error any more.
* MATAP - AdminTool: An issue was fixed where new instances were added to the bottom of the list.
* CUI does not send empty update requests to the Comos RestAPI any more.
* An issue where MetaClasses with instances couldn't be deleted was fixed.
* The user group cache and rights evaluation mechanism was overhauled for better integrity and performance.
* Fixed an HotSpotting issue where the empty revision creation did not work.
* An issue where ComosMetaProxyProperties were created with the wrong meta class when importing from Comos XML was fixed.
* Fixed an issue where spare parts (materials) were not displayed on the client.

 
Version 4.9.0.10024 on 2025/04/17:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.
* An issue where database connections are not closed under certain erroneous circumstances was fixed.
* MATAP: Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* MATAP: An issue was fixed where template instances were not shown under the Template Use Case.
* MATAP:Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-05-06T12:48:57Z

DAK: /* Hot fixes */

= Kernel (initial release)=
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.

= Hot fixes =
Version 4.9.0.???? on 2025/0?/??:
* Importing of MATAP data containing empty strings does not result the Proxies having an import status of error any more.
* MATAP - AdminTool: An issue was fixed where new instances were added to the bottom of the list.
* CUI does not send empty update requests to the Comos RestAPI any more.
* An issue where MetaClasses with instances couldn't be deleted was fixed.
* The user group cache and rights evaluation mechanism was overhauled for better integrity and performance.
* Fixed an HotSpotting issue where the empty revision creation did not work.

 
Version 4.9.0.10024 on 2025/04/17:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.
* An issue where database connections are not closed under certain erroneous circumstances was fixed.
* MATAP: Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* MATAP: An issue was fixed where template instances were not shown under the Template Use Case.
* MATAP:Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-05-06T12:32:17Z

DAK: /* Hot fixes */

= Kernel (initial release)=
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.

= Hot fixes =
Version 4.9.0.???? on 2025/0?/??:
* Importing of MATAP data containing empty strings does not result the Proxies having an import status of error any more.
* MATAP - AdminTool: An issue was fixed where new instances were added to the bottom of the list.
* CUI does not send empty update requests to the Comos RestAPI any more.
* An issue where MetaClasses with instances couldn't be deleted was fixed.
* The user group cache and rights evaluation mechanism was overhauled for better integrity and performance.
* Fixed an issue where the empty revision creation did not work.

 
Version 4.9.0.10024 on 2025/04/17:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.
* An issue where database connections are not closed under certain erroneous circumstances was fixed.
* MATAP: Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* MATAP: An issue was fixed where template instances were not shown under the Template Use Case.
* MATAP:Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-15T08:40:36Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* MATAP Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Template Use Case.
* Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID.
* An issue was fixed where new instances were added to the bottom of the list.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-15T08:39:53Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* MATAP Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Template Use Case.
* Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID
* An issue was fixed where new instances were added to the bottom of the list.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-14T07:13:53Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.
* A bug where certain database adaptations were skipped if no db-views were configured was fixed.
* MATAP Imports were improved. They do not overwrite data that were manually changed by using the Admin Tool any more.
* A missleading (false) https status code was documented for failed http communication in the post log was fixed.
* CUI Document Proxies get saved immediately when exporting them to Comos. This will avoid duplicates in exports if further processing fails.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Template Use Case.
* Fixed an issue where it was not possible to import new operations with a previously deleted Operation ID

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-01T11:22:58Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Template Use Case.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-01T11:22:40Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Template Use Case

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-04-01T11:22:20Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
* System.Numerics.Vectors, Microsoft.Bcl.TimeProvider, Microsoft.Bcl.AsyncInterfaces DLLs were added to the OIDC Processor plugin
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.
* An issue was fixed where template instances were not shown under the Tempalte Use Case

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-03-28T12:07:55Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were added/removed/finished.

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Version 4.9.0 (Server)

2025-03-28T12:06:10Z

DAK: /* MaTaP Improvements and fixes */

= Kernel =
== Features ==
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].
* Human-readable database views can be created in the same database instance where the data is stored.
* Custom code for MetaProxies can now be edited and transported using SmartStudio.
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A custom query-based search is now available to be used in customizing.
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.

== Bug Fixes ==
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.
* System.Memory.dll is now provided in the release packages.
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.
* An issue where values for new languages weren't saved was fixed.
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case
* Issues in internal file handling (of queued notifications) were solved for the Event Notificatoin Endpoint.
 
Version 4.9.0.? on ?:
* An issue where proxy attributes were created unnecessarily was fixed.
* An issue where MetaClasses couldn't be loaded from a Plugin was fixed.
* A memory Leak in the Enterprise Service (Notification Controller - Usease) was fixed.

== Enhancements ==
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.
* MetaProxy properties are now modeled more consistently in SmartStudio.
* A set of vulnerable 3rd party components were updated.
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.
* UBIK supports *.docx as standard filetype now
* The UBIK.EnterpriseService now processes queued tasks in an awaitable manner, with configurable pauses and idle-interruption when adding new tasks.

== MaTaP Improvements and fixes ==
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.
* Predefined views get saved and are available for Admin Tools now.
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.
* MATAP supports encrypted passwords for imported MATAP users now.
* MATAP supports Quality Record Forms now.
* MATAP supports Check Tasks now.
* MATAP Wallpaper Client supports project-related Punchpoint columns now.
* The Project Status is now managed on the Project Instance itself.
* UBIK MATAP supports project-related data caching on the View Cache now.
* The communication feature is now available in MATAP.
* All operation imports support the import of a work property.
* MATAP supports reports now.
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.
* MATAP supports the import and presentation of materials per operation now.
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.
* Identified an issue where activity codes were cut off when the project name was too long.
* Identified an issue where companies were cut off when the project name was too long.
* Deletion of default activity codes works now.
* Reimporting deleted objects is now possible.
* Wallpaper Client does not crash when opening a Scope Change anymore.
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.
* The Admin Tool is now able to download the customizing.
* Operations being set to Not Applicable show the right status color now (gray).
* Scheduling import works now for check and QRF operations too.
* Wallpaper does not crash anymore during progress reporting.
* Location assigning performance was improved.
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.
* MATAP imports will not overwrite once edited string data with empty values anymore.
* The "Turnaround Project" use case was renamed to "Project".
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.
* The currency on projects is now set to "€" by default.
* Key and unique filename have now been removed from the Plot Plans use case.
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)
* The Plot Plan Name is now displayed in Plant Layouts (Client)
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.
* The Zone column is now available in the Commissioning Package Usecase.
* Systems and subsystems are available in the Commissioning Tasks use case now.
* Documents below work orders are sorted by their type now.
* Names for systems and subsystems show in the expected order now.
* MATAP allows project names with a length of up to 100 characters now.
* New instances are now also saved if a refresh occurs beforehand.
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.
* Timesheets calculation issue for standard operations was solved.
* A sorting error for operations was fixed.
* When selecting import files, the file picker now remembers its last position.
* Template Usecases will now be replicated including their column configurations.
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.
* The Admin Tool Turnaround Project Usecase now provides project creation status information.
* A problem in the Admin Tool which led to random warnings is solved now.
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.
* Fixed recurring warnings in UBIK.Studio.
* Fixed recurring warnings in Admin Tool.
* The key column for MATAP users gets automatically filled if the object is created manually.
* Document system property will not be delivered to the client anymore.
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.
* The scope change workflow shows the user details again.
* A problem in the View Item Setup for the Communication Feature was fixed.
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.
* CODE_TYPE property doesn't get replicated when creating a Scope Change.
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.
* Performance improvements and general bug fixes for Admin Tool.
* The Bulk Editor scroll bars now retain their positions after a refresh.
* Admin Tool shows the name of the referenced project when displaying use cases now.
* Punchpoints show a changelog for the 'Responsibility' property now.
* The Admin - Tool Scope Change Usecase shows scope changes only now.
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.
* The Admin - Tool Scope Change Attachment Usecase works now.
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.
* Execution Documents show the Local Full Path in the AdminTool now.
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.
* The current Project Status can now be seen in the project header of the start screen.
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool
* Users can change a project name only until the creation is finished.
* Wrong order of CTS and UTS columns at Commissioning Package and Commissioning Task Use Cases was fixed.
* Corrected the locked status for timesheet Use Case columns.
* Fixed an issue where users with Create only permissions could not edit Scopechange details.
* Added final document location to file path in Scope Change attachment use case.
* An issue was fixed where the information on the Commissioning Wallpaper did not update when grouped commissioning tasks were finished

== Known Issues ==
* Exclusive Access is not fully supported (missing aspect: lock on database level)

Auto add MetaProperties to MetaClassScope

2025-03-18T13:37:24Z

DAK: /* Add MetaProperties to Scope */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.

==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only non-Signature MetaProperties will be added. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default value:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the "MetaClass" Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only non-Signature MetaProperties will be added. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default value:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto add MetaProperties to MetaClassScope

2025-03-18T13:36:15Z

DAK: /* Set MetaClass and add MetaProperties to Scope */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.

==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only non-Signature MetaProperties will be added. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default value:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the "MetaClass" Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto add MetaProperties to MetaClassScope

2025-03-18T13:34:52Z

DAK: /* Set MetaClass and add MetaProperties to Scope */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.

==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default value:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the "MetaClass" Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T11:56:37Z

DAK: /* Functionality (Before Version 4.9) */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope. Otherwise [https://wiki.augmensys.com/index.php?title=Auto_creation_of_a_MetaClassScope#Adding_an_existing_MetaClass_Scope_to_a_Context| Add fitting Scope to Context] will be executed.
The Drag and Drop Action will only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default value:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:57:23Z

DAK: /* Functionality (from Version 4.9 onwards) */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope. Otherwise [https://wiki.augmensys.com/index.php?title=Auto_creation_of_a_MetaClassScope#Adding_an_existing_MetaClass_Scope_to_a_Context| Add fitting Scope to Context] will be executed.
The Drag and Drop Action will only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:56:24Z

DAK: /* Functionality (Before Version 4.9) */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope. Otherwise [https://wiki.augmensys.com/index.php?title=Auto_creation_of_a_MetaClassScope#Adding_an_existing_MetaClass_Scope_to_a_Context| Add fitting Scope to Context] will be executed.
The Drag and Drop Action will only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default:
* Priority -> 0
* Lockstatus -> Read
* Visibility -> Visible
* Sort Order -> 0
* Compare Value -> DoNotCompareValue

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:50:46Z

DAK: /* Creation of a MetaClass Scope for a Context */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope. Otherwise [https://wiki.augmensys.com/index.php?title=Auto_creation_of_a_MetaClassScope#Adding_an_existing_MetaClass_Scope_to_a_Context| Add fitting Scope to Context] will be executed.
The Drag and Drop Action will only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:45:56Z

DAK:

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope. Otherwise [https://wiki.augmensys.com/index.php?title=Auto_creation_of_a_MetaClassScope#Adding_an_existing_MetaClass_Scope_to_a_Context| Adding an existing MetaClass Scope to a Context] will be executed.
The Drag and Drop Action will only add non-Signature MetaProperties. The MetaProperties "Tenant" and "Namespace" are excluded.
Also the following RelationProperties will be set to to their default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:28:08Z

DAK:

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:27:52Z

DAK: /* Functionality (from Version 4.9 onwards) */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* MetaProperties to be scoped
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* MetaProperties to be hidden

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:27:08Z

DAK: /* Functionality (from Version 4.9 onwards) */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* Scoped MetaProperties
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* Hide

[[File:MetaClassScopeConfiguration.png]]

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

File:MetaClassScopeConfiguration.png

2025-03-18T10:27:01Z

DAK: File uploaded with MsUpload

File uploaded with MsUpload

Auto creation of a MetaClassScope

2025-03-18T10:26:10Z

DAK: /* Creation of a MetaClass Scope for a Context */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
A "Detail Configuration" will appear where the user can specify following things:
* Name of the MetaClassScope
* Description of the MetaClassScope
* Scoped MetaProperties
* Status of MetaProperty e.g. ReadOnly, ReadWrite etc.
* Hide

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:18:57Z

DAK: /* Functionality fromVersion 4.9 onwards */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality (from Version 4.9 onwards)===

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:18:39Z

DAK: /* Functionality Before Version 4.9 */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality (Before Version 4.9)===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality fromVersion 4.9 onwards===

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:18:02Z

DAK:

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality Before Version 4.9===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Functionality fromVersion 4.9 onwards===

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:16:02Z

DAK: /* Functionality */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality===
====Before Version 4.9====
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

====From version 4.9 onwards====

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:13:53Z

DAK: /* Functionality */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds a fitting MetaClass Scope that already exists to the Context.

===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:13:02Z

DAK: /* Trigger */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".

[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds an fitting MetaClass Scope that already exists to the Context.
===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:12:44Z

DAK: /* Trigger */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.


==Creation of a MetaClass Scope for a Context==
===Functionality===
This Drag and Drop Action first looks for an identical MetaClassScope. Only if no matching scope exists, the action creates a suitable MetaClassScope.
The Drag and Drop Action will only add MetaProperties that are not "Signature". The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.
Also the following RelationProperties will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
Can be triggered by dragging a MetaClass over a Context when no fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Create a Scope and adds it to the Context".
[[File:CreateAScopeAndAddItToTheContext2.png]]

==Adding an existing MetaClass Scope to a Context==
===Functionality===
Adds an fitting MetaClass Scope that already exists to the Context.
===Trigger===
Can be triggered by dragging a MetaClass Scope over a Context when a fitting MetaClassScope is existing.
Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Add fitting scope to Context".

[[File:AddFittingScopetoContext.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:12:10Z

DAK: /* Trigger */

Auto add MetaProperties to MetaClassScope

2025-03-18T10:09:58Z

DAK: /* Trigger */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.

==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only MetaProperties that are not "Signature" will be added to the MetaClassScope.
The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the "MetaClass" Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto add MetaProperties to MetaClassScope

2025-03-18T10:09:05Z

DAK:

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.

==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only MetaProperties that are not "Signature" will be added to the MetaClassScope.
The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto add MetaProperties to MetaClassScope

2025-03-18T10:08:50Z

DAK:

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.



==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only MetaProperties that are not "Signature" will be added to the MetaClassScope.
The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto add MetaProperties to MetaClassScope

2025-03-18T10:08:35Z

DAK: /* Set MetaClass and add MetaProperties to Scope */

{{Version/ServerSince|4.8}} One of the [[Drag and Drop Actions]] in UBIK 3.7.1 and above is the automatic creation of new MetaClass Scope.



==Set MetaClass and add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will set the MetaClass on the MetaClassScope and add MetaProperties.
Only MetaProperties that are not "Signature" will be added to the MetaClassScope.
The MetaProperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is not set. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope MetaClass and its properties".

[[File:ScopeMetaClassAndMetaProperties.png]]

== Add MetaProperties to Scope==
===Functionality===
This Drag and Drop Action will add missing MetaProperties.
Only Metaproperties that are not "Signature" will be added to the MetaClassScope.
The Metaproperties "Tenant" and "Namespace" are excluded and will not be added by this Drag and Drop Action.

The following Relation Properties of every MetaProperty will be set to 0 by default:
* Priority
* Lockstatus
* ACM Visibility
* Order
* Compare Value

===Trigger===
It can be triggered by dragging a MetaClass onto a MetaClassScope where the MetaClass Property is already set but required MetaProperties are missing. Confirm your decision to create a MetaClassScope by clicking on the upcoming context menu item "Scope missing MetaClass properties".

[[File:ScopeMissingMetaProperties.png]]

=See also=

* [[HowTo:Create a new ViewItem]]
* [[HowTo:Create a new View]]
* [[Drag and Drop Actions]]

Auto creation of a MetaClassScope

2025-03-18T10:07:26Z

DAK: