-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] The process orchestration judge is best to allow it to drag the upper and lower order of the judgment conditions. #2648
Comments
感谢反馈,一个分支中条件的前后顺序不影响执行结果,暂无计划支持调整顺序。 |
Thanks for feedback, the order of the conditions in a branch does not affect the execution results, and there is no plan to support the adjustment order. |
影响的,流程很复杂时,分件分支的顺序非常重要,要把前面的都删了重新排IF条件,其实这个功能非常简单,就是JSON的替换而以,严重影响用户体检
…------------------ 原始邮件 ------------------
发件人: "1Panel-dev/MaxKB" ***@***.***>;
发送时间: 2025年3月24日(星期一) 上午9:55
***@***.***>;
***@***.******@***.***>;
主题: Re: [1Panel-dev/MaxKB] [Bug] The process orchestration judge is best to allow it to drag the upper and lower order of the judgment conditions. (Issue #2648)
感谢反馈,一个分支中条件的前后顺序不影响执行结果,暂无计划支持调整顺序。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
baixin513 left a comment (1Panel-dev/MaxKB#2648)
感谢反馈,一个分支中条件的前后顺序不影响执行结果,暂无计划支持调整顺序。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
影响结果的应该是调整分支的前后的顺序,你希望的是调整分支 IF、ELSE IF1 、ELSE IF2 的顺序吧。这个可以考虑 |
What affects the result should be to adjust the order of branches before and after. What you want is to adjust the order of branches IF, ELSE IF1, and ELSE IF2. This can be considered |
对阿,就是说这个意思,太好了,你优化一下吧,如果那些用户输入的变量,有些是下拉列表的,太多的时候,你也让它可以拖动上下顺序就更好了,辛苦了兄弟
…------------------ 原始邮件 ------------------
发件人: "1Panel-dev/MaxKB" ***@***.***>;
发送时间: 2025年3月24日(星期一) 上午10:21
***@***.***>;
***@***.******@***.***>;
主题: Re: [1Panel-dev/MaxKB] [Bug] The process orchestration judge is best to allow it to drag the upper and lower order of the judgment conditions. (Issue #2648)
影响结果的应该是调整分支的前后的顺序,你希望的是调整分支 IF、ELSE IF1 、ELSE IF2 的顺序吧。这个可以考虑
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
baixin513 left a comment (1Panel-dev/MaxKB#2648)
影响结果的应该是调整分支的前后的顺序,你希望的是调整分支 IF、ELSE IF1 、ELSE IF2 的顺序吧。这个可以考虑
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
另名还有那个问题阿,python函数库执行不行sqlserver的存储过程里的临时表插入数据时报错的问题阿,你看有办法处理不?应该是权限的问题?
…------------------ 原始邮件 ------------------
发件人: "1Panel-dev/MaxKB" ***@***.***>;
发送时间: 2025年3月24日(星期一) 上午10:21
***@***.***>;
***@***.******@***.***>;
主题: Re: [1Panel-dev/MaxKB] [Bug] The process orchestration judge is best to allow it to drag the upper and lower order of the judgment conditions. (Issue #2648)
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
What affects the result should be to adjust the order of branches before and after. What you want is to adjust the order of branches IF, ELSE IF1, and ELSE IF2. This can be considered
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
shaohuzhang1 left a comment (1Panel-dev/MaxKB#2648)
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
What affects the result should be to adjust the order of branches before and after. What you want is to adjust the order of branches IF, ELSE IF1, and ELSE IF2. This can be considered
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Contact Information
No response
MaxKB Version
v1.10.1-lts (build at 2025-02-13T18:52, commit: 0640d4c)
Problem Description
Steps to Reproduce
The expected correct result
No response
Related log output
Additional Information
No response
The text was updated successfully, but these errors were encountered: