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]

This is very interesting as I have never seen this behaviour. I have never synced the pattern after moving from one instance to another but it doesn't mean it wasn't happening. What version are you on as I'll look out for it next time I am migrating them. Either way thankfully it's a pretty easy process to do (you could probably event use a business rule to trigger the re-sync code so that is essentially automated). 

[Chris M3]

First noticed in Istanbul, and still occurring in Kingston.

[robertgeen]

Very interesting. The code is actually pretty easy so you could definitely do a business rule which forces it to re-sync. You would need to figure out how to differentiate a normal save vs from an update set but the code looks roughly like this to do it:

// Forcing synchronization of this specific pattern
current.setValue('sys_updated_on', new GlideDateTime().getValue());
current.setWorkflow(false);
current.update();

var ptl = new PatternLibrary();
ptl.notifyMIDs(current.name,'manual');

Check out the UI action for it that is on the pattern table and see if it can help you auto-sync it with a business rule. Hope this helps you automate it :).

[Chris M3]

The thing is, there is a Business Rule to do it.

Notify MID server on NDL change

I don't believe business rules run on a table when a record is updated from an update set.