jomarko commented on issue #870:
URL: 
https://github.com/apache/incubator-kie-issues/issues/870#issuecomment-1919226205

   Hi @tiagobento , let me share my thoughts about this topic. and my 
expectation, how the editor should work for this scenario.
   
   ----
   
   I understand **DRDs** and **Decision Services** as two similar concepts, 
where both tries to simplify the model for users. However each does different 
simplification.
   
   ----
   
   I understand **DRDs** more just like filtering of the nodes from the 
diagram. And each **DRD** as some stored filtered view of the main **DRG**. If 
I recall correctly, there can not be a node in **DRD** that wouldn't be in 
**DRG**. And I think **DRD** should contain:
   - either whole **Decision Service** node
   - or no **Decision Service** node
   
   my reasoning for this is bellow.
   
   ----
   
   I understand **Decision Services** as wrapper for some complex logic. These 
wrappers/decision services helps user to reuse some already created logic on 
more places, same as BKM nodes does. But from my point of view, it makes no 
sense to try reuse some wrapper/decision service on some other place and not 
include all its content. It would break not deterministic. I mean, if we once 
define Decision Service, it should always return the same results for the sme 
inputs. And this means Each occurrence of a decision Service node, is the same, 
containing all its **encapsulated** and **output** decisions.
   
   So I think if a **Decision Service** node appears in any **DRD**, it should 
alywas represent the same logic. I do not have strong opinion if we use 
collapsed or expanded views to achieve this.
   
   ----
   
   I think I speak about the same, what you describe as Option 3 but using 
other words?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to