Re:Google and Box Announce Partnership
by parent5446 on Thursday September 08, 2016 @01:16AM
(#12450454)
Posting evidence of this would be useful, because Drive is pretty comprehensive in terms of compliance. Also not sure what you mean by "workflow needs". Why would you use a file storage service to manage workflows in the first place?
[ Parent
| on HN ]
Re:Google and Box Announce Partnership
by enraged_camel on Thursday September 08, 2016 @01:46AM
(#12450563)
Because most workflows involve some kind of document. Automatically routing that document to different people and standardizing the way they interact with it can be very beneficial.
Re:Google and Box Announce Partnership
by parent5446 on Thursday September 08, 2016 @11:26AM
(#12453899)
Wouldn't that what the Drive API can be used for? I may be answering my own question here, but I imagine that would be the most useful part of this Box/Drive partnership. :D
Re:Google and Box Announce Partnership
by flukus on Thursday September 08, 2016 @03:43AM
(#12451035)
> Why would you use a file storage service to manage workflows in the first place?
Person A can only read document X because they are performing duty b on project y.
Not everything works with binary can/can't read scenarios.
Re:Google and Box Announce Partnership
by parent5446 on Thursday September 08, 2016 @11:25AM
(#12453884)
> Person A can only read document X because they are performing duty b on project y.
How is this _not_ a binary can/can't read scenario? The person can either read it because they're performing the duty, or can't ready it because they're not.
Re:Google and Box Announce Partnership
by flukus on Thursday September 08, 2016 @07:21PM
(#12458341)
It's not binary because they should only be able to read it while performing duty b. There needs to be something that enables/disables access when they start/stop working on it, or checks access before the read it.