{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":51425,"path":"telecom-network-inventory/telecommunications-network-inventory/path-compute-action.md","title":"Path Search function","bundle":null,"doc_type":null,"release":"australia","body":"\n# Path Search function\n\nThe Path Search function enables you to execute the path computation function between the starting and ending sites in the Telecommunications Network Inventory application. You can use this function for the path computation when you process the network inventory design and assign.\n\nYou can use the Path Search function to identify the possible paths between your network sites.\n\nIf no path is found, the Path Search function uses the available input to create a logical connection without adding any connection elements. If you don’t enter the end equipment, it selects any equipment that matches the Type attribute that belongs to the end site. The function uses the start and end interfaces in the input to set the Port A and Port Z of the logical connections. Otherwise, it selects any interface in the Availability field, which is marked as Available.\n\nYou can use this function as a Workflow Studio action in the Telecommunications Network Inventory workflow.\n\n## Roles and availability\n\nUsers with the admin role can add an action to a flow and define the configuration details of the flow. This function is available as a Workflow Studio action in the Telecommunications Network Inventory application so that you can perform inventory-related data operations.\n\n## Input fields\n\nThe following table lists the input fields in the Path Search function and their description.\n\n<table id=\"table_w3g_2fm_1vb\"><thead><tr><th>\n\nName\n\n</th><th>\n\nDescription\n\n</th><th>\n\nData Type\n\n</th></tr></thead><tbody><tr><td>\n\nStart Site\n\n</td><td>\n\nsys\\_id of the starting network site where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nEnd Site\n\n</td><td>\n\nsys\\_id of the ending network site where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nStart Equipment\n\n</td><td>\n\nsys\\_id of the starting network equipment where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nEnd Equipment\n\n</td><td>\n\nsys\\_id of the ending network equipment where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nStart Interface\n\n</td><td>\n\nsys\\_id of the starting network interface where this connection is configured.**Note:** If this field is left empty, it automatically selects the interface by using the path computation to create a logical connection.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nEnd Interface\n\n</td><td>\n\nsys\\_id of the ending network interface where this connection is configured.**Note:** If this field is left empty, it automatically selects the interface by using the path computation to create a logical connection.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nEnd Equipment Type\n\n</td><td>\n\nsys\\_id of the ending network equipment type where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nLogical Connection Model\n\n</td><td>\n\nsys\\_id of the logical connection model where this connection is configured.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nBandwidth\n\n</td><td>\n\nsys\\_id of the bandwidth of the connection.\n\n</td><td>\n\nString\n\n</td></tr><tr><td>\n\nAllowed Logical Connection Model\n\n</td><td>\n\nsys\\_id of the supported models for the logical connection. Click the add icon \\(\\[Omitted image \"add-icon-1.png\"\\] Alt text: Add icon.\\) to add a logical connection model.\n\n</td><td>\n\nArray.String\n\n</td></tr><tr><td>\n\nAllowed Physical Connection Model\n\n</td><td>\n\nsys\\_id of the supported models for the physical connection. Click the add icon \\(\\[Omitted image \"add-icon-1.png\"\\] Alt text: Add icon.\\) to add a physical connection model.\n\n</td><td>\n\nArray.String\n\n</td></tr><tr><td>\n\nFail Action\n\n</td><td>\n\nOption to select the action when the function fails. You can select an action from the list. By default, the **Create logical connection without path elements** is selected.\n\n</td><td>\n\nChoice\n\n</td></tr></tbody>\n</table>To learn more about the variable data types, see [Flow Designer input and output data variables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/action-inputs-outputs.md).\n\n## Output\n\nThe following table lists the information about the function's output.\n\n|Name|Description|Data Type|\n|----|-----------|---------|\n|Connection id|Returns the sys\\_id of the logical connection record.|String|\n\n**Parent Topic:**[Telecommunications Network Inventory function catalog](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/tni-flow-action.md)\n\n**Related topics**  \n\n\n[Allocate Free Number function]()\n\n[Create CI From Template function]()\n\n[Cascade Update function]()\n\n[Create and Assign Range/Single Number function]()\n\n[Create Logical Interface function]()\n\n[Create Logical Connection function]()\n\n[Create Physical Connection function]()\n\n[Create IP subnetwork function]()\n\n[CIDR to IP range function]()\n\n[Get Interface Summary function]()\n\n[Lookup Next Hub function]()\n\n"}}