Patch App Version
DescriptionPatch an existing application version with certain attributes of the application versionIf org is not provided, it will use the org from the authentication context.
Request
URLURL
Path Parameters
Path Parameters
App Version Id
appVersionId example
"e7421121-d052-4fd9-861f-7ce57246134e"
Query Parameters
Query Parameters
Organization ID: non-super users can only access their own organization
org_id example
"5c2409df-a307-4a04-b558-fb0693d42890"
Request Body
Schema for Appversion Patch. All fields are optional. Only the fields containing values are patched
{
"data": {
"applicationId": "da891c6b-3ac6-491b-9c79-c58788819500",
"bundleGuid": "da891c6b-3ac6-491b-9c79-c58788819500",
"deliveryFormat": "APP_VOLUMES",
"deliveryMode": "ONDEMAND",
"description": "MS Office 2013 for windows",
"lifecycleStage": "UNPACKAGED",
"name": "Office2019",
"packagerNotes": "Packaged for compatability checking",
"version": "16.0.10386.20017"
}
}
Internal Schema for Appversion Patch. All fields are optional. Only the fields containing values are patched. AppVersion is the particular version of software installed/captured in a given capture session. As part of the Cloud native capture only one AppVersion can be part of a Package. AppVersion was called in the past as “App Bundle” in the 3.x terminology. This is uniquely identified by a uuid which is generated during the capture session. With application package merge, it is possible to have the same AppVersion in multiple packages and also that single Package can have more than one AppVersion contained in it. Eg: “Microsoft Office 2013 sp1” can be the application version which can be captured under a virtual application named “Microsoft Office”, and this version can reside on a package “Microsoft_Office_2013_SP1_Clean.vhd”
Authentication
Response
Response BodyResponse Body
200 OK
{
"applicationId": "da891c6b-3ac6-491b-9c79-c58788819500",
"bundleGuid": "da891c6b-3ac6-491b-9c79-c58788819500",
"createdAt": "2022-07-11T07:44:49.619+00:00",
"deliveryFormat": "APP_VOLUMES",
"deliveryMode": "ONDEMAND",
"description": "MS Office 2013 for windows",
"id": "e7421121-d052-4fd9-861f-7ce57246134e",
"lifecycleStage": "UNPACKAGED",
"location": "US",
"markerIds": [
"CURRENT"
],
"name": "Office2019",
"orgId": "e7421121-d052-4fd9-861f-7ce57246134e",
"packagerNotes": "Packaged for compatability checking",
"updatedAt": "2022-07-11T07:44:49.619+00:00",
"version": "16.0.10386.20017"
}
Schema Representation for Application. Application is the Virtual Application container which will be created by the administrator to store the diffrent application packages captured or imported to be stored under. This will act as a grouping for different versions of the same software, so that the administrator can mark one of the application versions using a marker and that can be used in an assignment. Eg: “Microsoft Office” will be created as an application which is the virtual application container which will contain “Microsoft Office 2013 sp1” as an application version under it, “Microsoft_Office_2013_SP1_Clean.vhd” can be the application package containing the particular application version
Application Id of AppVersion
Bundle guid of AppVersion
This represents the timestamp at which the object was created
Delivery Format, APP_VOLUMES is used if this field is empty
Delivery mode of AppVersion, It can be either CLASSIC or ONDEMAND. CLASSIC is the default
Possible values are: CLASSIC , ONDEMAND
Description of AppVersion
This represents the unique Id of the Object
Stages of AppVersion, starting with UNPACKAGED which the system sets during application capture followed by NEW when capture is completed and Then TESTED,PUBLISHED and finally RETIRED when its no longer used.
Possible values are: NEW , PUBLISHED , RETIRED , TESTED , UNPACKAGED
This represents the location
Name of AppVersion
Data Structure related to OperatingSystem. OperatingSystem is the version of the Operating system on which the AppVersion is associated with which only they are captured or compatible with. Eg: AppVersion “Microsoft Office 2013 sp1” is capture on and compatible with “Windows 7 (64)”
This represents the organization Id
Notes added during the capture process or updated externally during pre-processing via metadata.
Schema for Package. Package is a physical file which might be of the format of VHD or VMDK based on the deployment platform used. This is the Physical file which will contain the AppVersion which is the Software installed/captured on a single capture session. Package file will reside on a file share when it is captured in case of Azure. With application package merge, it is possible for single Package to have more than one AppVersion contained in it. Eg: “Microsoft_Office_2013_SP1_Clean.vhd” can be an application package file which can contain the application version “Microsoft Office 2013 sp1”. Also this file will recide on a staging file share coressponding to the node/pod where it is captured.
Schema for Program. Program is the software component installed part of the capture session and which is detected by the App volumes capture agent as a seperate program based on variuos criteria predefined. Each program will have its own icon.Eg: “Microsoft Excel” can be a program isntalled as part of the application software version “Microsoft Office 2013 sp1”
Possible values are: DELETE_FAILED , PENDING_DELETE
This represents the latest timestamp at which the object was updated
Custom version of AppVersion
Errors
Unauthorized
Forbidden
Not Found
Code Samples
cURL Command
Vendor Extensions
x-codegen-request-body-name: packageMoveRequestDto
