We have a logic block in a workflow extension on Sales Orders that is a base logic block and deprecated. I wanted to double check if these “deprecated” logic blocks are still running or not? I assume the answer is yes, but want to double check.
To my understanding, deprecated metadata continues to function normally. Some warnings at run and design time may be thrown indicating the metadata has been deprecated, but the functional aspects are otherwise unchanged. @ross does that seem right to you?
4 Likes
Yes, that’s correct. Deprecated metadata objects should be disconnected from other objects in most cases but won’t always be unhooked.
- Deprecated indicates to any downstream users (partner developers and end users) that the particular metadata object will eventually be removed, so any customizations or extensions using that object should be redesigned not to use the original object.
- All connections to deprecated logic blocks will continue to function normally.
In the case of a logic block attached to a workflow definition, for example, records in the table might share an old workflow type and will run through the associated transition that has the deprecated logic. New records will often take a new path while existing records continue using the deprecated logic and transitions until no ‘old’ records exist.
1 Like
You will get a warning that the logic block is deprecated when you open it but the logic still works. What logic block was deprecated? I can let you know what we replaced it with!
1 Like