In your release notes you reference copied and customized logic blocks. When stating “copied”, do you mean “owned” logic blocks? OR does the definition of copy mean something else?
The reason for asking is that some NW logic blocks changed its inputs/outputs and I would like to understand that if we use those NW logic blocks in our code, does that fall under the category of “copied”?
Can you share a specific release note that’s written this way for better context? Copied logic blocks being called out in a release note doesn’t make much sense to me.
Hey Ian, go look at RN-25.2-[Sales Management]-5159. You will see that there’s a section called Action Required Details where you will find it.
It is an odd callout for a release note, but it is technically correct to refer to copied logic blocks - just not common.
A logic block metadata object can be copied. If this is done, the object will take on an ownership of Owned, the name will be namespaced, and it can be renamed . This object is now decoupled from the base (delivered) logic block and will never accept changes from the delivered object going forward, hence the release note calling out “if logic block a, b, or c is copied, uptake certain changes.”
Customizing the logic block is different because customizations will automatically accept most changes as they are delivered, so it’s the preferred method.
When using a delivered logic block in owned code, that does not count as copying the logic block if you’re only calling it and have not manually copied the object to change its ownership. Having said that, custom logic calling that block could need to change its inputs and outputs to/from the call if the underlying logic has a new shape.
Yes, and to be explicit - copying a Logic Block (or any metadata object) means that you have executed the “Copy” row action on a particular Logic Block Definition.
I find the release note confusing. I don’t immediately understand the use case for why a customer or SD partner would be copying a logic block and, furthermore, subsequently be having to uptake changes to their copy of it. To me, the main effect of these changes is going to be where other logic blocks interface to (i.e. call or extend) these logic blocks because their signature has changed and how they get called or extended may have to change
I’ve reached out to stakeholders internally on this to see about a possible clarification and updated verbiage.
All other posts are correct. The release note is mentioning that you if you copied any of those logics using the row action and then they are now owned. But you are also correct in the fact that you should look at any other owned logic blocks that are calling the changed logic blocks to see if they are impacted. We will update the release note template to be worded better. Thanks for pointing that out.
