spsprinkles / app-catalog-dashboard Goto Github PK

Add a new configuration option to create the test site on approval.

We need to enhance the solution to allow for a redeployment of the application. This will be needed as part of the upgrade flow.

The test site created for the app will need to break inheritance and add the developers to the web as owners. We will need to create a custom permission level to ensure the approver has rights to manage the sub-webs.

Update the solution to dynamically set the actions displayed, based on the status. This will need to be done in the configuration file.

I've just noticed while testing the modern "add an app" experience in a commercial tenant, if you set the "Video URL" property of an app in the actual "Apps for SharePoint" library, that when clicking on an app to view it's details a blank screen will appear due to a script error thrown in the console. As such we should be preventing setting of this field until this issue is resolved and confirmed to be resolved in the AF tenant.

Add support for a classic Add-in .app package. Consider filtering the file browser to only show supported app extension upon app upload dialog show.

The default security groups will need to be looked at for the solution. Deployed to a client environment and the users wasn't able to view the dashboard.

Update the Actions menu on the App view to more consistent with the look of the app. Suggest using tooltip icons or a dropdown menu.

The deployment error message must be displayed for the user. This will be done for the test site collection only.

Hide the "Default Metadata Language" field in the ItemForm

Check to see if the user has permission to click the deploy to site and/or deploy to tenant app catalog buttons. Disable if no permission.

The app will need to be checked if it already exists in the app catalog. This will cause a duplicate app to be installed w/ an error.

When uploading an app, compare the product id and app version to ensure the exact same app is not being uploaded. Discard the app package if the app is the same product & version. Update the app if this is a new version and rename the old app package file to include the old version in the name.

When upgrading an app to a new version, the previous version is moved to the archive folder. The name of the archived sppkg file is having the version number set correctly, but the file basename is incorrect, using the display name of the app and not the original file name. The archived app file name should match the previous sppkg file name like:

app-catalog-mgr.sppkg --> app-catalog-mgr-v0.0.2.7.sppkg

A notification button should be created to allow the developer to send an email to the approvers. The "approvers" will be determined by the configuration file. This will help the developer to be able to communicate with the current approver(s). This will be needed for upgrading/updating the test site collection after uploading a newer package.

MVP solution to display a dashboard and have deployment options to a tenant or site collection app catalog.

Only display the URL field in the ItemForm. Hide the description field for each URL field and set description to match URL value.

The footer and sub-nav components (when the width of the screen shrinks) is showing a waffle icon instead of the options like the main nav.

Create and set permissions for a Sponsor's SharePoint group. Auto add a Sponsor to this group once selected in Properties.

When rendering the Developer Agreement using a Classic page, the agree is shown. When rendering inside a modern page, the agreement is missing from the config.json. Possible issue with path inside the modern webpart.

The configuration file isn't loading in a classic page.

Add some verbiage when 'Submitting app for review' like, "Did you complete the necessary steps/high-level output document?"

The test case and tech review forms don't make sense.

Need to split out to have web url and file url as separate inputs.

On upload, parse the app manifest for unique app API permissions, like requiring the Graph API and/or Tenant level app permissions.

The dev agreement should be displayed when adding a new package.

Ensure metadata updates (app description, screenshot image URLs, etc.) get copied over to the tenant app catalog after the app is approved and deployed to the site collection.

Enhance the Owners field on the main Dashboard to show a brief shortened displayName, which adding a popover with more details about the user. Email button? Teams chat button?

After testing with the Category field, I found it's not even displayed on the "initial" page listing the apps and it's only shown under the "Details & Support" tab after clicking on an app. Unfortunately, it shows as a link that when clicked opens the public SharePoint App Store which doesn't do anything for us. As such it seems kind of pointless to have this field be populated.

Disable the edit button once an app is submitted. Changes should not be permitted unless the app is rejected.

The rejection comments are not visible to the user.

Need to ensure the order of installation is clear. Security groups should not be installed until the lists exist.

Enhance the approval button to automatically set the status based on the current status value. The status field will determine the workflow order.

Move the user agreement to be in the configuration file.

Settings menu in the main navbar should only render for Site Owner, not App Approvers group.

Check/test the "Rejected" status that goes back to Developer(s); make sure to notify and share why. Include a "rejection reason" in email.

"Owners" fields pre-populate with current user once new app is uploaded

The documentation will need to be updated, based on all of the changes.

The developer who uploads the package will need the rights to redeploy the solution. I'm not sure if we'll want to have the approver/sponsor do this or not.

Once an initial app assessment is created, the Review should be complete. Remove the extra step to complete the assessment.

Hide the "Enabled" field on the all views of the ItemForm. Set Enabled to true (always).

The templates url exists must exist in the configuration and have a value that doesn't point to a valid folder for the documents component to not render.

Rename the "Title" field to "Description" in Documents properties pane

The security group (Sponsor) logic in the installed required is not correct causing the solution to not render and the install dialog to not be displayed if the sponsor group isn't there.

In the filter CanvasForm, rename "Event Status" to "App Status"

Add the Sponsor person field to the App Details page

Extract the app icons(s) from the app package and upload them as documents to the DocSet. Update the metadata to automatically point to the file location int he main dashboard table.

Have the ability to check if the user is a SCA and have approval/submission buttons available.

When creating a new app assessment, fields should not default to any value. User must select Yes or No. Also rename Create button Submit and add a Cancel button.

In the display name of the Image URL(s), rename them to Screenshot URL(s). Keep internal name the same.