Hello Pires,
Now I will explain one by one here,
1. Can I merge update sets that are not on a "in progress" state.
Ans : Reason for merging the update sets, when two developers are working on same requirement at the same time, after implementation very simple you will have to select your update sets in status "In Progress" then just click to merge them.
Once it is done you will have a single update set with all the updates of those captured in it.
2. Can i choose what configurations I want to merge with specific update set? I mean, if I have configurations from incident table and problem table in the same update set but I only want to merge the incident configurations with another update set, is it possible?
Ans : configurations from incident table and problem table in the same update set not possible to merge selected configurations with another update set but you can move updates from one update set to another update set, update sets must be
'in progress'.
Merge Update Sets
You can merge multiple update sets into a single update set to simplify the transfer process. You cannot "unmerge" update sets once they have been merged.
- Navigate to . By default, the list is filtered to only show update sets that are In progress.Alternatively, navigate to . By default, the list is filtered to only show update sets that are in the Complete state. For example, you may want to use this filter after pushing changes or transferring update set from a development to a test instance.
- Filter the list to show only the update set that you want to merge.Merge update sets
- Enter a Name for the new update set. Updates are added to this set when the original sets are merged.
- (Optional) Enter a Description for the update set.
- Click Merge.
- In the confirmation dialog box, click OK.
- The new update set is created.
- The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.
- [Recommended] Verify that the correct changes were moved to the new set by scrolling down to the Merged Update Setsrelated list and opening the old update set records.
- [Recommended] Delete or empty the original update sets to avoid committing an older change by mistake. The system does not remove updates that were not merged into the new set.
I hope now you got some clarity on your queries, or else let me know if you need more help.....
Hello Pires,
Now I will explain one by one here,
1. Can I merge update sets that are not on a "in progress" state.
Ans : Reason for merging the update sets, when two developers are working on same requirement at the same time, after implementation very simple you will have to select your update sets in status "In Progress" then just click to merge them.
Once it is done you will have a single update set with all the updates of those captured in it.
2. Can i choose what configurations I want to merge with specific update set? I mean, if I have configurations from incident table and problem table in the same update set but I only want to merge the incident configurations with another update set, is it possible?
Ans : configurations from incident table and problem table in the same update set not possible to merge selected configurations with another update set but you can move updates from one update set to another update set, update sets must be
'in progress'.
Merge Update Sets
You can merge multiple update sets into a single update set to simplify the transfer process. You cannot "unmerge" update sets once they have been merged.
- Navigate to . By default, the list is filtered to only show update sets that are In progress.Alternatively, navigate to . By default, the list is filtered to only show update sets that are in the Complete state. For example, you may want to use this filter after pushing changes or transferring update set from a development to a test instance.
- Filter the list to show only the update set that you want to merge.Merge update sets
- Enter a Name for the new update set. Updates are added to this set when the original sets are merged.
- (Optional) Enter a Description for the update set.
- Click Merge.
- In the confirmation dialog box, click OK.
- The new update set is created.
- The most recent change for each object is moved from the original sets to the new set. Only changes that are not merged into the new set remain in the original sets. A message indicates how many updates were moved and how many were skipped. For example, if both update sets modify the Incident form, only the most recent change is moved to the new update set. The other modification remains in its original update set to provide a record of the changes that were not moved.
- [Recommended] Verify that the correct changes were moved to the new set by scrolling down to the Merged Update Setsrelated list and opening the old update set records.
- [Recommended] Delete or empty the original update sets to avoid committing an older change by mistake. The system does not remove updates that were not merged into the new set.
I hope now you got some clarity on your queries, or else let me know if you need more help.....
