Manually Assigning Target Group Workflows and Plugins

Before version FlexDeploy 6.5, users were required to associate Workflows and plugins with Target Groups.

Automated

Since FlexDeploy 6.5, the process of connecting is fully automated, and it is not expected that users will need to do anything manually. However, a screen was created to do it in unusual cases. The automation links properties to targets when the active workflow version contains an operation and a project has the workflow and target group configured. If you are creating new target groups, you can connect them to a project and then come back to topology, or you can associate them manually.

How to do it manually

To manually associate a workflow or plugin operation to a target group, which will allow the target properties to show and be set, go to the targets page. Then click the … button and then Manage Property Sets.

A popup will display that shows the workflows and plugin operations that are associated to the target group.

Workflows and plugin operations that were added manually will have a trash can by them, and can be removed.

Automatically associated ones will not. They cannot be removed.

What Happens

If you add an existing Workflow, the operations and properties that are defined in the currently active version are associated.

If you remove an existing Workflow, any operations and properties that are not otherwise connected will also be removed.

When you initially upgrade to 6.5, all the assignments will be marked as manually assigned. These will not be removed by the automated system ever. If you would like to see less properties, you can come to this popup and delete all of the associated workflows and plugin operations. If you do, the ones that are in use will be added back after you could save. After that, the trash can icon won’t show up.

Having trouble?

In the event that a required property was missed on a plugin operation, you can add additional plugin operations that you don’t plan to use. For instance, if you get a message that a property is required when you build, but you can’t find a place to enter it, add other operations from the same plugin to the target group and/or open a support ticket.

 

The following macros are not currently supported in the footer:
  • style