Change Details

With more scripts running in our Drive/GSuite environment it's also more important that these can be discovered/re-used. It also prevents scripts from being accidentally deleted when documents get converted/deleted. Drive allows scripts to be either stand-alone files or bound to another file. Bound scripts can do things non-bound cannot whereas non-bound ones can be shared trough team drives. Scripts can also be published for consumption within the organisation.

With more scripts running in our Drive/GSuite environment it's also more important that these can be discovered/re-used. It also prevents scripts from being accidentally deleted when documents get converted/deleted. Drive allows scripts to be either stand-alone files or bound to another file. Bound scripts can do things non-bound cannot whereas non-bound ones can be shared trough team drives. Scripts can also be published for consumption within the organisation. The goal of the task is to come up with either a mechanism for more easily discovering scripts, alternatively a best practice around this for ensuring scripts don't get lost.

With more scripts running in our Drive/GSuite environment it's also more important that these can be discovered/re-used. It also prevents scripts from being accidentally deleted when documents get converted/deleted. Drive allows scripts to be either stand-alone files or bound to another file. Bound scripts can do things non-bound cannot whereas non-bound ones can be shared trough team drives. Scripts can also be published for consumption within the organisation. The goal of the task is to come up with either a mechanism for more easily discovering scripts, alternatively a best practice around this for ensuring scripts don't get lost.