-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
使用X6如何实现流程编排中的分支情况 #3611
Comments
👋 @Hideer Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. |
暂时还没有好的思路,容我思考一下。 |
对于确定布局方向(从上到下,从左到右)的情况: 站在数据信号的角度上看,假设节点的流入流出模型是多输入单输出的:y ← f(x1,x2,x3),流入节点的多条边上的数据可能是不一样的,是需要进行数据处理的,但是流出节点的多条边上的节点的数据是一致,可以不需要节点进行额外处理? |
可以参考这个 demo。 |
最新开发这样的功能,有源码能参考下吗 |
Describe the feature you'd like to request
在实现流程编排过程中,分支情况较为常见,目前的分支常见形态见下图
![image](https://private-user-images.githubusercontent.com/31301552/239968395-643b1730-9ed0-4f33-bb25-71513af91c3a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NjE1NzgsIm5iZiI6MTcyNTY2MTI3OCwicGF0aCI6Ii8zMTMwMTU1Mi8yMzk5NjgzOTUtNjQzYjE3MzAtOWVkMC00ZjMzLWJiMjUtNzE1MTNhZjkxYzNhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA2VDIyMjExOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk3NmRhNzNiZmU5ODFiNjJlMDBlMmUyNDMxN2YwYjhjYmFkYmNmNzhjZGU1NTM1ZTUwZGI2NGEzNjI3ZDQ5ODgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.XI124Cfq23DbSrlEer3SjgxugczY-lbWnm6w8xGgMKM)
针对此类场景 边 需要具备聚合能力,如多条件的入口和出口需要聚合合并,并针对 边 上的标签或按钮进行处理
Describe the solution you'd like
如底层已支持此类场景期望提供出场景案例,供参考
Describe alternatives you've considered
目前可想到的解决方案如下
方案一(不合适):利用 边 的路径点(vertices)能力做到分支处理,但推演存在以下问题
方案二(繁琐且边界多):见下图将边按期望场景分割为多段,按 Lable 或自定义按钮切割,两节点之间窜在多个边,多个边之间用空白节点连接
Your Example Website or App
No response
Screenshots or Videos
No response
The text was updated successfully, but these errors were encountered: