Delta Activation during Assembly
The Assembly process consists of two major steps – Activation and Assembly. Activation of the solution activates the design time code to generate run time artifacts.
It was observed that the activation of a solution took considerable time if the solution was large in size (had huge content files). To improve the performance and reduce the activation time, further analysis revealed the following content types took major time during activation
a) Process Integration
b) WSID
c) Web service
d) Multi-Step Approval
e) Data Source
f) BO
g) XBO
The above-listed content types were activated during assembly even though they were active or were not changed in the patch.
To overcome this challenge a new feature - Delta Activation during Assembly is introduced with 1908. With this feature turned on, activation for the above-listed content types would be skipped if no changes are made to these content types or the underlying referenced objects.
The Delta Activation feature is released GA with 1911 release.
- Patch creation of old solutions would implicitly migrate the solution to support the Delta Activation feature.
- All new solutions created in after 1908 will support the Delta Activation feature and no migration would be required for the same.
- The feature is only available for C4C solutions.
- All solution types - MCS, Customer Specific and solution templates support the Delta Activation feature.
