major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
enhancement
BPE handles on its own who has the right to start or edit a workflow.
Therefore, it is not necessary for the TL Security System to be involved as well. This only works to a limited extent: If a person is dynamically added to the “Actor” role, it has no effect on their permissions. The person would see the tasks (depending on the workflow), but when selecting a task, an error would occur (due to security restrictions).
Code Migration
- Role profile definition files (security.xml) must be updated.
- Entries for
- ...#createProcessExecutionCreateAttributedDialog
- ...#CollaborationTableTileSecLayout
- ...#StartEventTableTileSecLayout
- ...#ProcessExecutionTableTileSecLayout
- ...#ActiveTasksTableTileSecLayout
- ...#ActiveTaskEditTileSecLayout must be removed
- Role profiles for SecurityStructure.processStart and SecurityStructure.processActor must be removed.
- The default role (SecurityStructure.user) must be granted all permissions in com.top_logic.bpe.app/bpe/app/structure/tileTab.layout.xml#tileTab: {{{
- Entries for
<view name="com.top_logic.bpe.app/bpe/app/structure/tileTab.layout.xml#tileTab"> <commandGroup name="Create"/> <commandGroup name="Read"/> <commandGroup name="Write"/> </view> }}}
Test
In BPE, only the same users as before are still allowed to view and edit tasks.