Community
Participate
Working Groups
Two problems with using the JWT aspects feature on automatically generated processes were reported by my collegue Benjamin Honke: Elements are not annotated with aspects if they exist and the profile has already been activated outside of the Workflow Editor. This is the case if workflows and their corresponding workflow_conf files are created externally, e.g. by a model transformation. It would be good if, on loading the generated workflow, the existing elements would be checked for and annotated with missing aspects just as is the case when enabling aspects in the management tab to ensure consistency. Another issue seems to be specific to custom aspect-based properties which are annotated on (activity)edges: If a custom property is placed on an edge and the corresponding profile is activated in the management tab, old edges are annotated with the aspect but not newly created ones.
