Forced to re-train and publish in each instance

[Kim Sullivan]

We have fully built out our Virtual Agent with NLU.  However, the training and publishing are not being captured in an update set.  We have to manually re-train in each instance.

Anyone else run into this?

[Willem]

Hi Kim,

So you set the state of a topic to Active and publish the topic and it is not captured in an update set?

Reference:

https://docs.servicenow.com/bundle/orlando-performance-analytics-and-reporting/page/administer/natur...

[Kim Sullivan]

That’s correct.

[nilimadesai]

Kim, 

With VA/NLU there are 2 separate Publish that occurs:

1) VA Topic Publish - these get captured in update sets, however, I have found that in case you try to Publish a VA topic without making any changes to the topic since the last time the topic was saved and published, it does not get recorded in the current update set. I would try making a small change to the VA topic property such as the Description field and then Save/Publish the VA topic. 

2) NLU Model Train/Publish - refer to my previous response. 

If I have answered your question, please mark my response as correct and/or helpful.

Cheers,

Nilima

[nilimadesai]

Hi Kim,

Looks like you are referring to NLU Model Training and Publishing. Since NLU Training/Publishing happens on a separate NLU server, it cannot be captured in an update set and NLU Model Training/Publishing does need to occur on each instance after the update set is moved. 

Having said that, you may submit an enhancement idea on the SN Idea portal to automate this process in a configurable way if an update set containing NLU Model changes is committed on an instance. 

If I have answered your question, please mark my response as correct and/or helpful.

Regards,

Nilima