System, method, and apparatus for a unified document surface
Systems and methods for publication and external interfacing for a unified document surface are disclosed. An example system may include a document serving circuit structured to access a document data, the document data comprising data for a unified document surface, and provide at least a portion of the document data to a client serving circuit. The client serving circuit may be structured to implement a unified document surface interface in response to the at least a portion of the document data, implement an extension creation interface, provide a pack implementation value to the document serving circuit in response to user interactions with the extension creation interface, and determine an executable object in response to the pack implementation value.
1. A system, comprising:
a document serving circuit structured to:
access a document data, the document data comprising data for a unified document surface; and
provide at least a portion of the document data to a client serving circuit; and
the client serving circuit structured to:
implement a unified document surface interface in response to the at least a portion of the document data;
implement an extension creation interface;
provide a pack implementation value to the document serving circuit in response to user interactions with the extension creation interface; and
determine an executable object in response to the pack implementation value wherein the executable object comprises an access authorization description and the access authorization description comprises authorization information for access to at least one of: a service or an external data value; and
a second client serving circuit structured to:
access a pack;
implement an extension utilization interface; and
incorporate at least a portion of the pack into a second document;
determine the executable object in response to the pack implementation value and access at least one of the service or the external data value based on the access authorization description, wherein the document serving circuit is further structured to isolate the access authorization description from the second client serving circuit.
2. The system of claim 1 , wherein:
the pack implementation value comprises an access authorization value.
3. The system of claim 2 , wherein the document serving circuit is further structured to expose a pack to a workspace in response to the executable object.
4. The system of claim 3 , wherein the access authorization description comprises an authorization type for each one of a service or an external data access of the pack.
5. The system of claim 4 , wherein the document serving circuit is further structured to require authorization information for the service or the external data access from a second user of a second document utilizing the pack in response to the authorization type comprising a user authorization type.
6. The system of claim 5 , wherein the document serving circuit is further structured to access the service or the external data access using separate credentials from the required authorization information.
7. The system of claim 4 , wherein the document serving circuit is further structured to provide access to the service or the external data access to a second user of the second document utilizing the pack in response to the authorization type comprising a system authorization type.
8. The system of claim 1 , wherein the document serving circuit is further structured to expose a pack to a workspace in response to the executable object.
9. The system of claim 1 , wherein the executable object comprises at least one of: a button, a unified document surface interface object, a code-based object, a third-party object, or a column object.
10. The system of claim 1 , wherein the extension creation interface comprises a software development kit (SDK) layer.
11. The system of claim 1 , wherein the pack implementation value comprises an arbitrary code component.
12. The system of claim 11 , wherein the document serving circuit is further structured to determine the executable object by isolating operations of the arbitrary code component from at least one of: the client serving circuit or the document serving circuit.
13. The system of claim 12 , wherein the document serving circuit is further structured to determine the pack implementation value by operating a virtual machine to execute the arbitrary code component.
14. The system of claim 13 , wherein the document serving circuit is further structured to determine the executable object by operating the virtual machine on a workflow serving circuit.
15. The system of claim 14 , wherein the document serving circuit is further structured to create a dedicated instance of the virtual machine for the arbitrary code component.
16. The system of claim 1 , wherein the document serving circuit is further structured to perform, in response to determining that an update to the pack implementation value comprises an incompatibility risk, at least one operation among:
providing an incompatibility warning value to a client device;
providing an update option value to a second client serving circuit accessing a document utilizing a pack exposed to a workspace in response to the executable object; or
providing an update delay value to the second client serving circuit accessing the document utilizing the pack exposed to the workspace in response to the executable object.
17. The system of claim 1 , wherein the document serving circuit is further structured to:
implement a sandbox interface as a part of the extension creation interface; and
provide a calculated output value to a client device in response to user interactions with the sandbox interface.
18. The system of claim 17 , wherein the document serving circuit is further structured to operate an external data access authorization in response an access credential supplied by the user to the sandbox interface.
19. The system of claim 18 , wherein the document serving circuit is further structured to store the access credential in a local hidden file of the client device.
20. The system of claim 1 , wherein the document serving circuit is further structured to:
perform a validation of the executable object; and
create a pack in response to the executable object and the validation.
21. The system of claim 1 , wherein the document serving circuit is further structured to:
perform a validation of the executable object; and
provide a notification to the extension creation interface in response to the validation indicating a pack error.
22. The system of claim 21 , wherein the pack error comprises at least one of: a formula error, an authorization error, or a code operation error.
23. The system of claim 1 , wherein the extension creation interface further comprises an assistance interface.
24. The system of claim 23 , wherein the assistance interface further comprises at least one of:
a tooltip associated with at least one of: a component of the extension creation interface, a formula command, or a text value;
a description value associated with the at least one of: the component of the extension creation interface, the formula command, or the text value; or
a code example associated with the at least one of: the component of the extension creation interface, the formula command, or the text value.
25. The system of claim 1 , wherein the extension creation interface is configured to limit access to an external data access value to a defined external data component of the extension creation interface.