Auto approve glossaryTerm changes if they are done by a reviewer.
Is your feature request related to a problem? Please describe. A reviewer is often the Data Steward or Data Governance team member.
Currently, if the change is done by a reviewer, the term goes into InReview and Approval task is generated.
Reviewers/Data Stewards often does mass updates (for example add a new tag/change tag) via the upload. This means that the same Steward then gets 100s of approval tasks.
Describe the solution you'd like If change is performed by a reviewer, it should be auto approved.
Describe alternatives you've considered Running a separate process via API to approve. Not very effective, almost would be a clean-up work done daily.
Additional context Add any other context or screenshots about the feature request here.
Internally, we've determined that the new approval process (Draft → Auto in Review → Approved) will require us to create a separate tag dedicated solely to the approval process, with approvals based only on that tag.
Additionally, in our process, a term requires much more than just a description to be considered officially "in review." As a result, the current "In Review" status is somewhat meaningless, and we need an additional flag to indicate items that are truly under review.
@karanh37 @sonika-shah
Here are the workflows that would work