Stephen Russett

Jira ticket created: https://issues.redhat.com/browse/KOGITO-6638

same issue occurs with Message Start Events in 1.16.1

Anything that is a property name created by the modeler could cause collision. so should be isolated.

Having the "data" in the body makes it easy for consumption. Getting into headers starts to create complexity for regular business data consumption. What about an optional data wrapper that...

@cristianonicolai yes roles in practice are the best practice and SHOULD be used over usernames. In real world though, there are many times where you need to code in usernames...

@cristianonicolai can the sec properties be used in **parallel** with ODIC/openid auth? (was under the impression you have to pick ~one of the providers such as Sec Properties file **OR**...

But profiles would mean different ENVs. In my scenario it is all the same ENV configurations: Process Starters that are coded to specific usernames would be at a dev level,...

For 1,3,4 yes that doc exists but it misses the implementation part: @fjtirado Skip is a phase as described here: https://docs.jboss.org/kogito/release/latest/html_single/#con-task-lifecycle_kogito-developing-process-services so initial interpretation of the modeler UI would suggest...

@fjtirado 100% agree... The skippable is a great concept. But unless you want to implement it, it is just confusing and creates mental connections that don't correlate with actual implementation.

@fjtirado What you are describing is the service task's and script tasks chosen implementation. I am describing the BPMN business semantic and visual usage for describing a process/workflow. In other...