Migrating Discovery Patterns in Update Sets

[Chris M3]

Just wondering if anyone else has run into this.  I don't like the answer I got from HI Support.

When migrating new or updated patterns from one instance to another in an update set, the pattern does not get synchronized automatically with the midserver.  This has added additional steps into our release process where the engineer now has to go synchronize those patterns.  Its easy to do, but its a one-off manual step added to our release process.

When we first realized this was occurring, I opened a ticket with HI Support, and the response was basically that it was working as designed.  I did get an enhancement task submitted, even though I've never seen one go beyond submitted status.

[robertgeen]

Yeah that makes sense but you could always have one that triggers on the versioning table if types is for a pattern so that it essentially forces it even if it is from a business rule. Either way I feel your pain with this issue and it's obvious that it's just a downfall of having to use an update set.

You could technically also have a business rule that checks when an update set goes to committed and does a search for all the items and looks for any change where class is a pattern and then triggers it at that point. That would actually probably work pretty well if you are looking to automate this somehow.