Skip to main content

ServiceNow Robust Transformer Engine (RTE) changes - Tokyo

ServiceNow Robust Transformer Engine (RTE) changes - Tokyo 


see:

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/import-sets/concept/etl-definition-overview.html


note that you now have to dotWalk for reference fields, which is a change from San Diego:



note also the following:


There is a new UI policy introduced "require path when table is defined" in Tokyo version , which Path will be mandatory when table name is not empty.
On San Diego: Specify the table name for an import entity because there is no UI policy to make Path field as mandatory.

On Tokyo: Don't need to specify both the table name and Path name for an import entity because that UI policy is introduced, system will automatically create the import set table for import entity.

you can clear the table's cache by running the below script from Scripts -Background.

GlideTableManager.invalidateTable("x_cls_clear_skye_i_account");


From ServiceNow:
- under "Target entities" in the documentation below the reference field needs to use the dot walked path. The example used in this case is computer.id 

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/import-sets/concept/etl-definition-overview.html


This behavior changed in Tokyo 
Based on the documentation in step (7) above the customer needs to explicitly specify the dot walk in the "Field/Path" in the record in step (10) above. 


Comments

Popular posts from this blog

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }

ServiceNow - script include: build up the results as a JSON object (array) - example 2

function call var sCurrentGroupMembers = new <script_include> (). getGroupMembers ( group_sysid ); gs . print ( 'sCurrentGroupMembers:' + sCurrentGroupMembers ); var oGroupMembers = JSON . parse ( sCurrentGroupMembers ); gs . print ( JSON . stringify ( oGroupMembers . users )); oNewGroupMember = JSON . parse ( group_members ); var oGroupConfig = getGroupDeltas ( oGroupMembers . users , oNewGroupMember ); gs . print ( JSON . stringify ( oGroupConfig . remove )); gs . print ( JSON . stringify ( oGroupConfig . add )) output : *** Script: sCurrentGroupMembers: {"manager":"3b2649efdb0f8c10cc0652f3f39xxxxx", "email":"", "type":"33a2226edb99c340edfc7cbdae96xxxx", "description":"Created for xyz", "users":[{"user":"3b2649efdb0f8c10cc0652f3f396xxxx"},{"user":"856a8f71db3d73041b4ffc45ae96196a"},{"user":"3752771