-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Feature][admin] Task submit support approval #4061
Comments
Hello @MactavishCui, this issue is about web, so I assign it to @Zzm0809. If you have any questions, you can comment and reply. 你好 @MactavishCui, 这个 issue 是关于 web 的,所以我把它分配给了 @Zzm0809。如有任何问题,可以评论回复。 |
If you need to implement such a function, whether you need to add the function of on-site notification to remind the corresponding approver for approval, and at the same time, you can generate the corresponding approval form link for quick approval |
Thank you very much for your suggestion on the approval function. I think the approval management page should be in the authentication center (or other center) instead of adding a new approval center. |
I think this can be considered later. It is an optimization and does not affect the existing logic. You can continue to add such functions after the current task is completed. |
Thx for your reply. Firstly, thanks for your suggestion, I agree with @Zzm0809 it will be helpful to remind users and generate an approval link. And I also agree with what @gaoyan1998 said, I think after finishing current task maybe an alert instance can be build or other methods can be used to notify users, which can improve this function better. And I'm willing to continue working on it. |
@aiwenmo Thanks for your suggestion! The reason I add a new approval center page is that I think in the future, more process can be controlled by approval like datasource register, document management and so on. I agree with your idea that in current version, it will be better to put approval page into auth center. I'll update codes today based on the new page layout. |
Besides, may I divide this function implement into several small PRs and submit them step by step? I think it can be divided into these steps:
Looking forward to your reply |
@MactavishCui OK. Besides, in the future, when more processes are controlled by approval, an approval center should not be added either, because approval is an auxiliary function and it should be classified into one center. Looking forward to your PR |
@aiwenmo Thanks a lot! Your reply helps me understand the page layout design better, and that can surely helps me a lot in further contribution to dinky! |
Search before asking
Description
Currently, Dinky has implemented the features including auth management, task version control to support team development cooperation. In my opinion task review is also an important feature for team development .The code and configuration review before deployment can help teams make a better data ware house quality. As a result, l proposed this task approval feature.
Use case
In order to implement task approval, l think dinky should have following abilities:
Approval configuration center
It has following options:
The following pics list my attempts, mentioned options can be changed in configuration center:
Task submit aspect
The pic below shows the process of task submit with approval.
Approval Center
In this page ,users can get the approvals they submitted or required for review. Like what has been implemented below, users can do some operations including withdraw, reject and approve. The different between previous and current version can also be reviewed Approval search is also supported.
pic task approval list
pic task info
pic reject or approve
pic approval status and handle event
Of course, when enable task approval configuration is disabled, this page is also not available:
All mentioned above is my new attempt about task approval. What is your opinion about this feature and my scheme?
Looking forward to your reply and discussion!
Related issues
No
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: