Package Automation Options / Automation Workflows
AdminStudio 2024 R2 | 28.0 | Application Manager | Options Dialog Box
Edition:Application Manager is included with AdminStudio Professional and Enterprise Editions.
The following properties are listed on the Configure Workflow dialog box.
|
Properties |
Description |
|||||||||||||||||||||
|
Workflow Name |
Enter the valid name of the workflow. |
|||||||||||||||||||||
|
Set as default automation workflow for all new package requests added to the Backlog. The default workflow is marked with an asterisk(*) |
Select this check box to set the workflow as a default automation workflow for all new package requests added to the Backlog. By default, this option will be unchecked. |
|||||||||||||||||||||
|
Configure Workflow Steps |
In Configuring Workflow step, Import action will be selected by default. To configure other workflow steps, click + icon and proceed with respective configuration details. To delete any workflow step, click x icon beside the workflow steps. Configure the following Workflow steps:
For more information, see Configuring Automation Workflows for Package Automation. |
|||||||||||||||||||||
|
Destination Group (Import Action) |
By default, Applications\[Vendor]\[Product Name]\[Version] placeholders will be selected in the Destination Group field. To change the Destination Group, click the browse button (...). The Select Destination Group dialog box opens. Click the New Group button, in the New Group popup, enter name of the group, and then click OK button. Note:Nested groups can be created. Click the Create subgroup based on source folder structure check box, if you want to create subgroups in the folder structure. Click OK button to exit the dialog box. The possible placeholders are: [ProductName]\[Version]\[Vendor]\[Platform]\[SetupType]\[Language]. This order can be rearranged. Based on the details provided, the package will go to the destination group in the Application Manager Catalog. |
|||||||||||||||||||||
|
Automatically create a custom transform file (Import Action) |
Selecting Automatically create a custom transform file check box will automatically create a transform (.mst) file based on the selections made in the customization wizard of the subscribed packages and imported into the catalog along with the MSI package into the catalog. This check box will be selected by default. |
|||||||||||||||||||||
|
Customized Switches to new version (Import Action) |
By selecting Customized Switches to new version check box, any additional customizations specified in the installation command property of the older version application will be retained and applied to the newer version application. By default, this option will be deselected. |
|||||||||||||||||||||
|
Select Wrapper (Wrap Action) |
Select the required wrapper format:
Note:Make sure that the WiseScriptPackageEditor (.exe) is installed to wrap the package in WiseScript. |
|||||||||||||||||||||
|
Target package format (Convert Action) |
Select one of the following target package formats:
By default, the Microsoft MSIX type will be selected. |
|||||||||||||||||||||
|
Distribution System (Publish Action) |
Select one of the following distribution systems:
These are the four Distribution Systems supported in the Publish action. |
|||||||||||||||||||||
|
Destination Group (Publish Action) |
Enter the destination group in the Destination Group text box. By default, Applications\[Vendor]\[ProductName]\[Version] value will be specified. You can also specify the desired Group name for the Destination Group. Example: ConfigMgr Destination Group - Applications\Distribute. Where Applications is the primary node in ConfigMgr and Distribute is a folder under that. |
|||||||||||||||||||||
|
Publish Package Type (Publish Action) |
Select the following package type to publish:
|
|||||||||||||||||||||
|
Save Workflow |
Click on the Save Workflow button to validate and save the configured workflow action details. |
See Also