Manifest View - WIP

TODO - Lots of pictures.

Requirements:

• The application must use v5 game server.
• The application needs to be configured in hope.
• The users of the application need to have the correct application permissions in order to view / edit the manifest system.

Edit / View a Manifest:

• Select the app you’d like to view / edit
  • This is an autocomplete view and will filter based on your input. You are required to select a game from the provided list.
  • The list is populated from all currently setup games that the current user has permissions for.
  • If the game your looking for doesn’t show up contact Scryptkeepers or your project manager.
• Selected a platform from the dropdown list.
• Select an environment from the dropdown list.
• Select a game version
  • This is an autocomplete view and will filter based on versions that are already saved. Any value can be entered here if for instance your trying to setup a manifest for a new version.
• One all required values are set the action buttons will enable
  • View : will attempt to fetch a manifest given all the application data selected above.
  • Download : will prompt you to download the current manifest contents to disk.
  • Upload : will attempt to upload a manifest given all the aplication
  • Choose File : will let you upload a manifest from a file.
  • Toggle (TBD Name toggle) : will enable a second manifest view that can be used to view to different manifests at a time makes it easier to compare two different manifests.
• If some of the manifest selection options aren’t enabled for you see your product manager for details.

Applying / Viewing Usertypes for a Manifest:

• You can test Usertypes from the manifest view by adding specific specific Usertypes and / or a userID to the manifest request.
• Usertypes are a view only feature and will disable the upload button until you’ve disabled usertypes and re-downloaded a default manifest.
• The response you get back will try and generate a manifest using the provided information.
  • eg: You enable Usertypes and add a userID : The game server will look up the provided Usertypes for that user and return the manifest generated for them.
  • eg: You enable Usertypes and add some specific usertypes : The game server will generate a manifest using the usertypes that are set.
• Toggle : Enable / Disable the sending of usertype information in the manifest request.
• Usertypes chips autocomplete view : An autocomplete view that will let you select from a list of Usertypes setup for the current game / app / env.
• UserID : You can enter a userID which will get sent with the request. The Usertypes that are associated with that user will get used to generate the manifest.
  • The usertypes that usertypes for the user that are used to generate the manifest will be displayed in the lower section of the Usertypes view.
• Method : A dropdown that will let you select how to use the usertype information when generating the manifest for this request.
  • Override : Will override what the server has saved for this user and use the list defined in the Usertypes section.
  • Additive : Will use both the Usertypes in the request AND the usertypes saved on the server to generate the manifest for the request.

Schema validate:

• Schema can be used to help validate and identify potential issues with a manifest.
  • eg : Applying the MoreFunAdAPI schema can help identify if an ad network node is missing.
  • eg : Applying a GameServiceConfiguaration schema could help identify that configuration is set to QA when pushing to production.
• Enabling schema will apply them to the manifest json section below.
• Schema autocomplete view : Will filter all available schema based on the input
• If you apply schema to you manifest they will get saved into your manifest when you upload your manifest and will get automatically applied when you fetch the manifest again.

Manifest:

• The manifest section displays the current contents of the manifest.
• For more information about the different configurations of the manifest editor see the github source page