TABLE OF CONTENTS
Introduction
Some projects may have information about applications that are not captured by the main inventory source used by ManagementStudio. E.g. Web Apps, in house built apps. In this case, project administrators can use an Excel source to manually import the information into ManagementStudio. This article describes the fields that can be used.
For further information on data imports, please refer to this article.
Available Application Fields
| Field Name | Description | Required? |
| App ID | The App ID is a unique reference created by ManagementStudio when an application is imported into the ManagementStudio database. The use of this field will vary depending on the reason for the import:
| Yes, when updating existing applications. |
| App Vendor | The application vendor's name For example, Symantec | Yes, when importing new applications |
| App Name | The name of the application. For example Excel. | Yes, when importing new applications |
| App Version | The version of the application. For example, 15.0 | Yes, when importing new applications |
| Start Date | The deployment Unit start date | No |
| Process Status | This is the internal Process status of the process the application is in. | No |
| Process | The application's process can be set during the import process. For example, if the application is already in UAT, this could be added to the import file to enable ManagementStudio to change the Process from the default value of 1. Identified to the current status of 5. UAT. | No |
| Sub Process | The application's sub-process can be set during the import process. This should be used in conjunction with the Process section above to ensure the correct sub-category is selected. For example, if 5. UAT is selected as the Process, the Sub-Process should be set to UAT Queue, UAT in Progress or On Hold. | No |
| Also Known As | Alternative names that the application might also be known by. For example Office Word. | No |
| Superseded To (AppId) | This is the App Id, the application has been superseded to. | No |
| Superseded To (Name) | This is the App name, the application has been superseded to. | No |
| Is Archived | Any applications that have been rationalised will be marked as archived and moved from the primary application view. When archived, the Is Archived checkbox will be ticked. | No |
| Priority | The priority of the application can be recorded using the Priority field. Out of the box, an administrator can choose from Low, Medium and High. This field is often used to record the importance of an application during packaging. | No |
| Package Type | This is the packaging technology used when deploying applications to users. This field allows administrators to specify a particular packaging or delivery format. For example App-V, MSI,Citrix | No |
| Assigned To | When an application moves through the workflow, the individual that is working on the software should be recorded using the Assigned To field. | No |
| Localisation | If the application is available in a specific language, this should be recorded using the Location field. For example, United Kingdom. | No |
| Date Required | The Date Required field records the date that an application is required to be ready for production. | No |
| Description | Enter a description of the application that is being imported. For example, Word, part of the Microsoft Office suite. | No |
| Complexity | The complexity of an application can be recorded at any point during the packaging process. Defining the difficulty of the packaging work is useful to understand the level of resources that might be required to complete the packaging. Out of the box, an administrator can choose from Basic, Normal, Medium or Complex. | No |
| CustomProperty (1-10) | These are Custom fields which can be utilised to hold more information about an application. | No |
| CustomList (1-5) | These are internal CustomList fields | No |
| CustomDate (1-4) | These are internal CustomDate fields | No |
| CustomInt (1& 2) | There are Custom Integer fields used to hold more information about an application. | No |
| CustomFlag (1-3) | Checkboxes. Use the following text: Yes/No or True/False or 1/0 | No |
| This is the field used to store the primary contact email address. For example An app owner's email address | No | |
| CoreApp | Applications that are core to the Windows build and should be delivered to all users are recorded using the Is Core App field. | No |
| Architecture | Applications might have a different architecture for different systems or legacy platforms. This should be recorded using the Architecture field. For example, x84 or 64-bit. | No |
How to Bulk Import new Applications
This process assumes the Application spreadsheet to be imported has been prepared with the relevant fields and populated.
- To start importing applications, click Import Data (1)
- Select Applications (2)
- Browse to the location where the excel file is saved and select file
- Click Try to Auto Match (3) from the toolbar to allow ManagementStudio to automatically attempt to map the appropriate fields if similar names are used within the Details column (4)
- In this example, we are importing new applications, so the Create if not found (5) is ticked. If you are updating an existing record, ensure the Update if found is ticked
- Ensure the checkbox Move to Process (6) is ticked and select the relevant process you want these new applications to be imported to
- Click Preview Import to preview and then Import Data (7) to begin the import process
- Click Import to confirm
- There should be a import report log displaying the results, click OK to exit
- Switch back to the Applications module, the imported applications should now be displayed within the grid
- This completes the application import process
Further Support
If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.