Solutions
On the Solutions page, Global Admins and Application Admins can view solutions according to the libraries the solutions belong to. On this page, they can also manage solutions.
Solutions are placed within libraries. Before you create a solution, ensure a library for that solution type exists.
Solution connection names are case sensitive. Apps to which a solution is imported must have a connection with the same name as the connection in the original app; if they do not, the connection name will not be recognized, and you will receive an error when you deploy the solution.
You cannot export a custom workflow solution for which the Studio script is still being reviewed.
User App - Library names and Library types created by default
In the User App, the library names and library types below are created by default.
Library Name | Library Type |
---|---|
Excel Workbooks Library |
Excel Solution
|
Forms Library |
Form Solution |
Queries Library |
Query |
Reference Data Lists Library |
Reference Data |
Transactions Library |
Transaction |
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 four different library types: Excel Solution, Form Solution, Query/Transaction, and Reference Data.
|
Library Types | |||
---|---|---|---|---|
Excel Solution |
Form Solution |
Query/Transaction |
Reference Data |
|
Capabilities |
Add Workflow |
Add Solution |
Delete |
Add Schema |
Delete |
Delete | Download a Copy | Copy Schema | |
Download a Copy |
Edit Solution |
Open in Excel |
Delete | |
Edit Workflow |
Export |
Open in Studio |
Edit Data |
|
Export |
Import | Process History | Export | |
Import |
Usage |
Usage |
Import | |
Open in Excel |
Version History | Version History |
Update Schema |
|
Open in Studio |
Import |
Usage |
||
Process History |
Export | Version History | ||
Usage |
View Data | |||
Version History |
View Schema |
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.
When you import a Reference Data Solution, the following radio buttons do not display: Allow Versioning and Rename Solution.
The various capabilities are described below.
Capability | Description |
---|---|
Add Solution | Solution designers can add solutions to Form Solution Libraries. |
Add Workflow | Solution developers can add a workflow to Excel Solution Libraries. |
Copy Schema | Solution developers can create a new schema by copying an existing reference data schema. The new schema will be based upon the existing one. |
Delete | Users can delete solutions. |
Download a Copy | Users can download a copy of the solution. |
Download to Excel | User can download Solution metadata to excel. This is applicable for all three Solutions i.e. Forms, Excel and Reference data Solutions. Note: Only the filtered and sorted data in the columns that are selected get exported. The downloaded Excel File name is same as library name. |
Edit Data | Users can edit data in a reference data solution. This option is available only for reference data solutions which were published without Excel. |
Edit Solution | Solution developers can edit solutions within Form Solution Libraries. |
Export | Users can export a solution or workflow to the desktop. Note: For the import and export of an Excel workflow, the SAP Server Connection name (bound to the Studio script in the source app) should have the same name as it has in the destination app. |
Import | Import a solution or workflow saved on the desktop. |
Open in Excel | Open a data file in the Studio Excel Add-in. |
Open in Studio | Open a solution in Studio directly. |
Process History | Users can view the process history of a solution. |
Update Schema | Solution developers can update existing reference data schemas. |
Usage | Users can see a list of all instances where the solution is being used. |
Version History | Users can view the version history of a solution. |
View Data | Users can view data in a reference data solution. |
View Schema | Solution developers can view schemas belonging to an existing reference data solution. |
Add Schema | Solution designers can add reference data schemas. |
API Properties | App Administrator or Solution Developer can Enable/Disable API for a Composer Solution. |
API Usage | User can check the API usage for a solution. |
Edit Workflow | Within Excel Solution Libraries, solution developers can edit workflows which have already been added to the Evolve app. |
Edit Library Workflow | Within Excel Solution Libraries, solution developers can edit workflows at library level, which have already been added to the Evolve app. |
View Library Workflow | Users can view workflow of library. |
Library Workflow Version Histroy | Users can view the version history of a library workflow. |
Export Library Workflow | Users can export a workflow in a library to the desktop or other Evolve App. |
Import Library Workflow | Users can import a workflow in a library from the desktop or other Evolve App. |
Download to Excel | User can download library to Excel. |
JSON Payload | User can download JSON Payload for form solution. |
Payload | User can download Payload (JSON) for Excel solution. |
XML Payload | User can download XML Payload for form solution. |
Limitation:
If template contains cell comments, drawing objects, pivot table, and form controls (such as buttons, check-boxes, list boxes) then these control will not be preserved from Excel files.