.
Key | Issue Type | Summary | Resolution | Note |
---|---|---|---|---|
SAFETY-241 | Bug | Canceling the "clean" command still deletes the compile information |
Fixed | |
SAFETY-226 | Improvement | Copy Safety Application ID to clipboard |
Duplicate | |
SAFETY-202 | Bug | [IO]: Repeating names in IO-mappings when adding them via "Scan for Devices" |
Fixed | |
SAFETY-201 | Bug | Exception on closing CODESYS |
Fixed | |
SAFETY-191 | Bug | CODESYS GIT Safety Task commit not possible |
Fixed | |
SAFETY-190 | Bug | Incorrect communication TAN after update device |
Won't Fix | [[GENERAL]] There is nothing to fix for this issue in the Safety Extension because the TANs sent to the runtime are already correct and there is no need to change anything. Instead, the problem is caused by a suboptimal check of the connection IDs on the runtime side and will be handled independently with SIL3SL-646. |
SAFETY-188 | Bug | Auto Declare: It is not possible to select the instance of the available FSoEMaster |
Fixed | |
SAFETY-186 | Improvement | New application state: No online application state within the state "Wait for operator confirmation to start the bootapplication" |
Fixed | |
SAFETY-184 | Improvement | Safety Oberfläche: Logout auf Sys_Err response bei Appstatus service |
Fixed | |
SAFETY-176 | Bug | SafetyTaskEditor: Editor cannot be opened on Chinese Windows |
Fixed | |
SAFETY-82 | Improvement | SoftSafety: Show app based license metrics for safety applications |
Duplicate | [[GENERAL]] Duplicates SAFETY-105 |