An "appling upgrade" action is shown as failed in Power CID with error message "Value cannot be null. (Parameter 'input')" but completed successfully in environment.
After an import was completed in a target environment two uninstall processes start. This leads to an error because the second uninstall will fail. One uninstall is enough.
"Cannot start another [Uninstall] because there is a previous [Uninstall] running at this moment. Use Solution History for more details. -- The solution installation or removal failed due to the installation or removal of another solution at the same time. Please try again later."
ToDos
inspect actual behavior, why second uninstall starts? Is it necessary? Why was it implemented? Edge cases?
prevent start of second uninstall (check if uninstall is running or completely disable install from portal)
A view is to be created in which all environment variables of an environment are displayed with display name, name, type, default value and current value.
ToDos
Add new TypeScript service class
Add method in TypScript service: make two authenticated calls to the Dataverse API to retrieve environmentvariabledefinitions and environmentvariablevalues of an environment defined by MS Id (due 13.06.23, 4 hours)
Create model class for merged data (due ??, 1 hour)
Add method in TypScript service: Merge return values environmentvariabledefinitions and environmentvariablevalues into an array (due ??, 4 hours)
Add menu item "Environment Variables" to the first level of the main menu with matching icon (due ??, 2 hours)
Create Angular component, connect with menu item and routing ("/variables") (due ??, 4 hours)
Calling the portal API via existing (?) TypeScript service method to query the stored environments (due ??, 2 hours)
Display of a DevExtreme dropdown with the queried environments (due ??, 2 hours)
After selecting an environment in the dropdown, call methods to query and merge the respective environment variables (due ??, 2 hours)
Display a DevExtreme data grid, with the columns see issue description (due ??, 8 hours)
If a change to the base URL of an environment has not been transferred in the PowerCID portal, no error message appears but the loading process freezes. There must be a meaningful error handling here.
The DataGrid in the solution overview only shows the last 30 entries (upgrades/pacthes). It should have a infinity scrolling enabled. Also the horizontal scrollbar is only shown at the bottom the page, should be on the bottom of the winodow.
ToDos
fix infinity scrolling
show horizontal scrollbar at the bottom of the window
Each application should get a property "Group". Data type "Group" is to be checked (free text, entity, ...). In the soltion overview there are two dropdowns to select the entity. The first dropdown is for selecting the group, the second one is for selecting the application within the group.
ToDos
Add "Group" to Application
UI feature to set/edit group of Application
Edit Solution Overview Dropdown(s)
Group Applications by group in Applications Component
An import should be triggered reliably on the target system. Only when it has been ensured that the import is running, the status should change to "in progress".
The default solutions of an environment (Active, Basic, Default and CDS Default Solution) should not be proposed and selectable when adding an existing application.
Deployment details should be saved for each import action. These should document, for example, the environment variables and connection references used during delivery.
A user manuel for Power CID Portal shall be created. All import information for using the application should be descripted in way that everyone can use the Portal without additional instruction. This includes all roles (user, manager & admin).
This function is to clone an existing patch. This means that a new patch is created and all components of the original patch are moved to the new patch.
It should be possible to delete a patch. This is then removed from Power CID Portal and from the development environment. This is only possible as long as no successful import has taken place anywhere. The patch should be displayed as crossed out in the solution overview.
There should be a function to apply an upgrade only. After the import on the target system, further adjustments may be necessary (e.g. dependencies), so that import and apply must be separated.