- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2018 03:29 AM
Variables from the identification section can be referenced by $parent. during connection building. Is the same also possible with variables set in the extension section?
Using $parent doesn't show up any of the variables I defined in the extension section nor do I find another way to reference them. Do I miss something here or is the extension section only good for populating attributes of the CI type?
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2018 10:09 AM
I raised a HI ticket and got an answer:
- Variables from Extension Section are not available in Connection Section because Extension Section is run after Connection Section. The run order by the plattform is as follows: Identification Section, Connection Section, Extension Section
- BP for new connections: New connections should be done in the Connection Section
My take away from this is:
- ServiceNow recommends: Don't use the Extension Section for creating new connections. Use Connection Section instead
- To gather information for the Connection Section
- the Extension Section is useless because you cant reference information gathered in the Extension Section in the Connection Section (Reason: the plattform runs the Extension Section after the Connection Section).
- I've to modify the Identification Section to gather information for the Connection Section (which means the pattern will get flagged)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2018 11:07 AM
I understand the point concerning the flag. But what speaks up against using the extension section also to create connections? In my case the patten IIS Virtual Directory doesn't get the neccessary connetion details to the SQL DB because of a customer specific configuration. I use the extension section to gahter the customer specific SQL configuration details. Would you build the connection to the DB in the extension section or in the connection section?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-16-2018 11:14 AM
You can create it right in the Extension Section. I haven't played with it much but this is the general reason for having them is so they can be used across multiple patterns and also not flag it. If the create operation is available then go for it my friend :). I haven't heard anything official but I am pretty sure this is the way they want to push us in the future (and I suspect we will see connection sections go away at some point and just be extension sections). Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2018 08:45 AM
I've raised a question in HI to get an offical answer to my question. As soon as I have a final statement I'll update the post
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-15-2018 05:33 AM
Extension section should be done before connection section during runtime:
https://docs.servicenow.com/bundle/london-it-operations-management/page/product/service-mapping/task/modify-pattern-using-extensions.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2018 10:09 AM
I raised a HI ticket and got an answer:
- Variables from Extension Section are not available in Connection Section because Extension Section is run after Connection Section. The run order by the plattform is as follows: Identification Section, Connection Section, Extension Section
- BP for new connections: New connections should be done in the Connection Section
My take away from this is:
- ServiceNow recommends: Don't use the Extension Section for creating new connections. Use Connection Section instead
- To gather information for the Connection Section
- the Extension Section is useless because you cant reference information gathered in the Extension Section in the Connection Section (Reason: the plattform runs the Extension Section after the Connection Section).
- I've to modify the Identification Section to gather information for the Connection Section (which means the pattern will get flagged)