This operation saves the name of the deployment group that will be migrated. It doesn't contact the server at all. It can be run on any endpoint, whether the FlexDeploy local server endpoint, an Informatica server, or any other working endpoint. Pass in at least one of the two Deployment Group Name options either Project Property or Plugin Input.

This provides you with two possible options for Project Setup.

1. Project by Deployment Group
   • Configure Deployment Group Name on Project Properties.
   • Do not use anything for Plugin Input for Deployment Group Name. i.e. workflow does not assign anything to Plugin Input for deployment group name.
   • It is advisable to keep Project Name same as Deployment Group Name for clarity.
   • This option works well with Release Snapshot and Pipeline based execution and helps with continue delivery.
   • You will also be able to see reports very clearly by deployment group name as that is same as project name.
   • Downside of this approach is that you will end up creating many projects and possibly inactivate them once not being used.
2. Ad-hoc Project to perform Build and Deploy using Input for Deployment Group name.
   1. Do not use anything for Deployment Group Name on Project Properties.
   2. Configure Workflow Input to be passed in to Plugin Input for Deployment Group Name.
   3. This option works for Ad-hoc deployments but it will not fit in Release and Pipelines.
   4. Reports will also not be very useful with this approach.

Environment/Instance Properties

Project Properties

Inputs

Outputs

Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.