I am using an address block that is a composer address block. I would like to create my own address block from this address block and save it as a custom type in my organisation. Then I want to update all the addresses in all my forms to my new custom block. So I need to understand the impact analysis of the Composer block so that I know how many addresses I need to update.
Is there a way to do this?
While Nirmal is correct, using an alias should only be considered when the internal structures match as any existing overrides on children that do not exist in the aliased type will create new fields.
Composer does have Impact Analysis for an organisation. Go to the organisation level in the workspace tree, then the Administration tab and at the bottom is Impact Analysis where you can select your tyoe and click Analysis and it will show where it is used is this organisation.
Alternatively you can right click on the widget in the palette while editiing a form and select impact analysis which will do the same thing but has to have the form open.
Thanks both! Glenn - this has worked brilliantly and is exactly what I needed.
You can use aliases in composer. In your org stylesheet, you can replace the default address block with your custom address block. By using alias, Composer will use your defined custom block wherever you have references to the default address block.
In the example below "Block-address" is the default address block which is replaced by custom block called "Block-custom-addressblock"
<alias type="Block-address" replacedby="Block-custom-addressblock"/>