On the Solutions page, Global Admins and Application Admins can view solutions according to the libraries the solutions belong to and they can manage solutions.
Solutions are placed within libraries. Before you create a solution, ensure a library for that solution type exists.
When you import a solution from one library to another library, one version of the solution is created in the new library - irrespective of how many versions of the solution were in the original library.
In a user app, the following library names and associated types are created by default:
|
Capabilities associated with library types
As a Global Admin or App Admin, you can create any number of libraries. The capabilities you have for any specific solution depend on the type of library to which the solution belongs.
The table below includes the capabilities or 'set of actions' you can take for solutions belonging to a Query or Transaction library.
| Capabilities: Query/ Transaction Library Type | Capability Description |
|---|---|
|
Delete |
Users can delete solutions. |
| Download a Copy | Users can download a copy of the solution. |
| Process History | Users can view the process history of a solution. |
|
Version History |
Users can view the version history of a solution. |
| Open in Excel | Open a data file in the Studio Excel Add-in. |
| Open in Studio | Open a solution in Studio directly. |
|
Usage |
Users can see a list of all instances where the solution is being used. |
Limitation
If template contains cell comments, drawing objects, pivot tables, and form controls (such as buttons, check-boxes, list boxes) then these control will not be preserved from Excel files.