# URLs and Access Parameters ## Overview of ASM Core URLs {% @arcade/embed flowId="LgXzHJKNdikIAhrTJRJR" url="" %} ASM Core URLs are used to access different interfaces, like the Self Service Portal, and also to perform complex functions such as launch searches, open incident forms, view service orders, and even to pre-populate fields on submission forms or search criteria windows, and then to submit those forms or searches. Complex functions are performed through the URL by appending http query strings to the base URL. The URL structure consists of the base URL, the interface parameter, the target page parameter, and the query parameters. URLs are made up of constant and variable parameters. Some parameters vary from system to system while others are static values. The following convention has been used to denote parameters: * Variables within URLs are denoted within angular brackets. * Constants are denoted in the regular text without brackets. ### Structure of the base URL
### Example of a http query string: {% code overflow="wrap" %} ``` http:////portal.aspx&Form=KnowledgeSearchCriteria&Search_Query=cracked laptop screen&All_Words=Y ``` {% endcode %}
When constructing URLs for use in ASM Core, note that: * All following parameters must be preceded by **&** * Parameters and their values are joined by **=** * Characters entered after **=** and before **&** are treated as a value and therefore can contain spaces Here is an example of how these are strung together based on the example URL above. ## To launch ASM Core ``` http:////Core.aspx ``` ## To launch the Self Service Portal ``` http:////Portal.aspx ``` ## To Launch Nano ``` http:////Nano.aspx ``` ## To launch the portal Knowledge Search Criteria page ``` http:////Portal.aspx&Form=KnowledgeSearchCriteria ``` ### To launch the portal Knowledge Search Criteria page with the words “cracked laptop screen” in the Search Text field, and the All Words checkbox selected {% code overflow="wrap" %} ``` http:////Portal.aspx&Form=KnowledgeSearchCriteria&Search_Query=cracked laptop screen&All_Words=Y ``` {% endcode %} ## API URLs ### Admin ``` https://{host-name}/{core-system-name}/Alemba.Web/alemba/admin ``` ### Agent/User Role ``` https://{host-name}/{core-system-name}/Alemba.Web/alemba/api-explorer-choose ``` ## URLs and Access Parameters ### Use base URLs to: * Access ASM Core * Access the Self Service Portal * Access the HTML Only Interface * Access the Catalog Portal * Access ASM Core through WSRP ### Use http query strings for the Self Service Portal to: * Automatically Log into the Self Service Portal * Retrieve a Password * Change a Password * View a specified knowledge article, or access the search page for Knowledge Bank * View a specified incident, or access the search page for Incidents * View a specified request, or access the search page for Requests * View a specified service action or service bundle, or access the search page for Browsing the Service Request Catalog * View a specified service order, or access the search page for Service Order ### Pre-populate search fields and automate searches in the Self Service Portal using http query strings for: * Knowledge Search * Incident Search * Request Search * Browse the Service Request Catalog * Service Order Search --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.alemba.com/asm-hermes/use-asm/about-the-alemba-service-manager-family/urls-and-access-parameters.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.