Updating Solution Set

The Solution Set update would take place through a sales process. Once the commercial discussions are completed, the customer is able to update the Solution Set via a Build Place.

If there are changes to the applied solution set in the IFS Internal System, User Administrators can update the solution set from the IFS Internal System. Click on the Update Solution Set button in the Build Place.

Next, you will see the Update Solution Set Form displays the list of the modified components. Click on the Apply Update button to update the solution set.

This will fetch the new solution set from the IFS Internal System and it will be committed to the Customer Baseline Repository. Then, it creates a branch in the Customer Solution Repository, merges the solution set with the existing solution set, and creates a pull request.

A user having repository access (e.g.: Technician, Customer Solution Developer) should approve that pull request to merge the changes to the master branch. To approve the pull request, the user should find the pull request with the title "Merge Updated Solution Set", once the Update Solution Set pipeline completes.

The progress of the updating solution set can be viewed from the pipeline URL (Go to Jobs in Lifecycle Experience portal. Find the relevant job for the updating solution set request from the jobs table and click the pipeline URL).

Once you click on the pipeline URL, it can be seen in the Azure DevOps Project.

Check the updated solution set by viewing it in the Customer Solution Repository after the Pull Request Merge is Completed.

Once the solution set is updated and the pull request is approved, run a Sanity Build for the Build Place and order an Environment. Once this task is completed, users can include this component in the planned delivery to the Use Place. To learn the process of delivery planning, please refer to Build Place Deliveries.

Note

The generally practiced communication method should be followed between customer and implementation teams when following the above process as the activities involve multiple teams.