Status Update
Comments
sa...@google.com <sa...@google.com> #2
Thank you for filing this feature request.
I redirected it internally.
fr...@gmail.com <fr...@gmail.com> #3
Given that this is a non-intrusive function, I would prefer that reading be prioritized.
At least for my use cases, knowing that a document is in an approved/not approved state allows me to integrate approval workflows into things like slack in custom ways...
-FT
ma...@papercut.com <ma...@papercut.com> #4
The ability to automate approvals on incoming documents via API or Apps script.
Additional to this, the ability to check approval status or subscribe to an approval event to allow scripts to move or update the file
ra...@banked.com <ra...@banked.com> #5
Maybe only API Documentation needs to be prepared. Any ETA would be appreciated.
mu...@arrival.com <mu...@arrival.com> #6
ni...@arrival.com <ni...@arrival.com> #7
[Deleted User] <[Deleted User]> #8
Create and read approvals in Google Drive via API -- extremely helpful
ma...@muskokagrown.com <ma...@muskokagrown.com> #9
This would be very helpful for our use case.
cl...@noaa.gov <cl...@noaa.gov> #10
Read approvals with Drive API. Determine requestor, requested time, approvers, when approvers approved or reject, Get approved version and version number.
mf...@broadinstitute.org <mf...@broadinstitute.org> #11
ti...@centrocristiano.com.co <ti...@centrocristiano.com.co> #12
da...@onplan.co <da...@onplan.co> #13
he...@tradener.com.br <he...@tradener.com.br> #14
br...@pwc.com <br...@pwc.com> #15 Restricted+
a....@ixopay.com <a....@ixopay.com> #16
[Deleted User] <[Deleted User]> #17
fe...@gmail.com <fe...@gmail.com> #18
[Deleted User] <[Deleted User]> #19
jo...@aliz.ai <jo...@aliz.ai> #20
jo...@tearfund.org <jo...@tearfund.org> #21
ni...@imagination.com <ni...@imagination.com> #22
d....@unicas.it <d....@unicas.it> #23
[Deleted User] <[Deleted User]> #24
np...@broadinstitute.org <np...@broadinstitute.org> #25
mf...@broadinstitute.org <mf...@broadinstitute.org> #26
bh...@broadinstitute.org <bh...@broadinstitute.org> #27
[Deleted User] <[Deleted User]> #28
pe...@gmail.com <pe...@gmail.com> #29
[Deleted User] <[Deleted User]> #30
fa...@gmail.com <fa...@gmail.com> #31
- Open the document you want to start approval;
- Click File > Approval > Start new Approval flow, select option "Lock file before sending approval request"
- Call API /drive/v3/files/:fileId?fields=contentRestrictions, the response will look like this:
{
"contentRestrictions": [
{
"readOnly": true,
"restrictingUser": {
"kind": "drive#user",
"displayName": "........",
"me": true,
"permissionId": "........",
"emailAddress": ".........."
},
"restrictionTime": "2022-04-27T11:03:42.430Z",
"type": "globalContentRestriction"
}
]
}
- Back to the document, make the approval, and file will be locked.
- Call again API /drive/v3/files/:fileId?fields=contentRestrictions, and now the response response will look like this:
{
"contentRestrictions": [
{
"readOnly": true,
"reason": "Locked for File Approval",
"restrictingUser": {
"kind": "drive#user",
"displayName": "......",
"me": true,
"permissionId": ".......",
"emailAddress": "........"
},
"restrictionTime": "2022-04-27T10:54:24.594Z",
"type": "globalContentRestriction"
}
]
}
The difference is in the "reason" field, "Locked for File Approval" means that file was approved.
P.S.: I don't how trustable this workaround is, I tested several several and it seems consistent.
P.S.: I don't know if there are a better way to do it, just could find this one at the moment
xd...@gmail.com <xd...@gmail.com> #32
That's great that you can detect existing approval status via API, but this issue is requesting the ability to create approvals via API.
ma...@muskokagrown.com <ma...@muskokagrown.com> #33
How does this actually work though? Do enough of us say +1 and a system upvotes that in terms of priority? Or do we just wait until they get their way down their list?
xd...@gmail.com <xd...@gmail.com> #34
Google uses the number of starred items to help them prioritize what to work on internally. The people who post "+1" add nothing and simply spam those of us who have starred the issue.
mi...@hinghamsavings.com <mi...@hinghamsavings.com> #35
jb...@lbcu.mobi <jb...@lbcu.mobi> #36
sa...@gmail.com <sa...@gmail.com> #37
ra...@airbus.com <ra...@airbus.com> #38
[Deleted User] <[Deleted User]> #39
st...@careem.com <st...@careem.com> #40
[Deleted User] <[Deleted User]> #41
ya...@gmail.com <ya...@gmail.com> #42
This would be very useful to at least view any status changes to the Approvals process or trigger events on full approval.
An example: I have a client who has sub-contractor tenders go through an approval process using a shared document for review o each tender. If all parties involved approve the tender, then we want to update their procurement schedule and start an onboarding workflow.
[Deleted User] <[Deleted User]> #43
ev...@gmail.com <ev...@gmail.com> #44
dy...@dreamyoungs.com <dy...@dreamyoungs.com> #45
k-...@mark-inc.jp <k-...@mark-inc.jp> #46
[Deleted User] <[Deleted User]> #47
so...@riverlearningtrust.org <so...@riverlearningtrust.org> #48
[Deleted User] <[Deleted User]> #49
ev...@gmail.com <ev...@gmail.com> #50
fa...@gmail.com <fa...@gmail.com> #51
ka...@meta.com <ka...@meta.com> #52
[Deleted User] <[Deleted User]> #53
[Deleted User] <[Deleted User]> #54
mi...@360x.com <mi...@360x.com> #55
gi...@maasi.eu <gi...@maasi.eu> #56
[Deleted User] <[Deleted User]> #57
VF...@cadillacfairview.com <VF...@cadillacfairview.com> #58 Restricted
am...@abuseedotrading.com <am...@abuseedotrading.com> #59
ab...@presti.ai <ab...@presti.ai> #60
br...@broadsims.com <br...@broadsims.com> #61
Please update me if any good news.
[Deleted User] <[Deleted User]> #62
ni...@fulll.fr <ni...@fulll.fr> #63
[Deleted User] <[Deleted User]> #64
gu...@fulll.fr <gu...@fulll.fr> #65
fr...@veolia.com <fr...@veolia.com> #66
ev...@gmail.com <ev...@gmail.com> #67
fr...@veolia.com <fr...@veolia.com> #68
fl...@fundacao1bi.com.br <fl...@fundacao1bi.com.br> #69
ds...@holycross.edu <ds...@holycross.edu> #70
an...@webcapsule.io <an...@webcapsule.io> #71
be...@ecosio.com <be...@ecosio.com> #72
jp...@google.com <jp...@google.com>
[Deleted User] <[Deleted User]> #73
la...@careem.com <la...@careem.com> #74
we...@noaa.gov <we...@noaa.gov> #75
c....@plukon.nl <c....@plukon.nl> #76
ba...@nutanix.com <ba...@nutanix.com> #77
ol...@stratioautomotive.com <ol...@stratioautomotive.com> #78
pr...@tzmo-global.com <pr...@tzmo-global.com> #79
sv...@gmail.com <sv...@gmail.com> #80
nu...@gmail.com <nu...@gmail.com> #81
jl...@gmail.com <jl...@gmail.com> #82
jl...@gmail.com <jl...@gmail.com> #83
ev...@gmail.com <ev...@gmail.com> #84
fr...@veolia.com <fr...@veolia.com> #85
al...@aperam.com <al...@aperam.com> #86
ro...@fulll.fr <ro...@fulll.fr> #87
da...@ville-noumea.nc <da...@ville-noumea.nc> #88
de...@gmail.com <de...@gmail.com> #89
l0...@gmail.com <l0...@gmail.com> #90
ch...@and.digital <ch...@and.digital> #91
38...@gmail.com <38...@gmail.com> #92
ca...@citizenrelations.com <ca...@citizenrelations.com> #93
mi...@gmail.com <mi...@gmail.com> #94
po...@medbeat.se <po...@medbeat.se> #95
Accessing the Approvals of a document and adding that to an exported version would be vital to our continued use of Google Drive, gdocs and gsheets.
Is there any time frame for this?
an...@demo.strataprime.com <an...@demo.strataprime.com> #96
lu...@trt15.jus.br <lu...@trt15.jus.br> #97
al...@twenty-four.io <al...@twenty-four.io> #98
za...@bpkp.go.id <za...@bpkp.go.id> #99
bo...@haiilo.com <bo...@haiilo.com> #100
fa...@capitalone.com <fa...@capitalone.com> #101
it...@premierpress.com <it...@premierpress.com> #102
bo...@impact-nano.com <bo...@impact-nano.com> #103
ta...@sanmina.com <ta...@sanmina.com> #104
jo...@xqinstitute.org <jo...@xqinstitute.org> #105
ik...@gmail.com <ik...@gmail.com> #106
sw...@beckvilleisd.net <sw...@beckvilleisd.net> #107
There is a +1 button near the top right of this page. Leaving a comment is good, but make sure you hit the +1 as well.
Description
A short description of the request: the Google Docs/Sheets/Slides Approvals system via the Google Drive or Docs API.
Use of
What is the purpose of this new feature?
Right now, the only way to create a new "Approval" is through the Web UI. Automating bulk approvals is essential to our use case.
What existing APIs would this affect?
Either the Google Drive API or the respective Docs, Sheets, and Slides APIs.
What existing data does this use?
It affects a Docs/Sheets/Slides entity stored in Google Drive to create a new Approval entity. It also "locks" the Doc/Sheet/Slide.