Step 1. Open the Aspire Admin UI.

Browse to the Aspire Admin UI. It is typically located at http://localhost:50505.

Step 2. Select the Seed option from the left-hand menu.

The "Seed" “Seed” option, identified by a "seed" by a “seed” image , is located on the left side of the application, just above the "Workflows" “Workflows” option. Click on it to navigate to the "Seed" “Seed” page.

Step 3. Specify Connection Description and Type.

Once on the "Seed" “Seed” page, click on the "“+New" New” option to create a new Seed or select an existing one to modify it.

• Description: specify a description for the Seed. It is advised for it to be concise and meaningful.
  
• Type: select "ServiceNow" “ServiceNow” as the type for the Seed.

Step 4. Specify the Articles and Attachments configuration (Optional).

Once the type has been selected, you will be presented with the "Articles “Articles and Attachments" Attachments” section of the "Seed" “Seed” page. Here you need to set the following options for this section of the Seed. If no options are modified, default values are used:

• Include Articles and Attachments : if enabled, knowledge articles will be crawled and, optionally, attachments for those articles can be crawled too.
  
  • Articles Display Base URL: the base display URL for articles.
  • Security: Choose what type types of Acls ACLs would have the Knowledge Articles. 
    

    • Public: Only public items will be crawlcrawled. Articles with Public Knowledge Base, and if Can Read or Can Contribute fields are set, should be only public User Criteria values. If Cannot Read is set, the item will not be crawled.

    • Knowledge Base: Acls ACLs for articles and attachments will be the sys_id of the Knowled Knowledge Base  (requires server configuration).

    • User Criteria: Acls ACLs for articles and attachments will be the sys_id of the Can Read, Cannot Read or Can Contribute  (requires server configuration)

  • Use custom search query: If checked, include a ServiceNow compliance valid query string. The connector will send it to ServiceNow as it is, and the result depends on the glide.invalid_query.returns_no_rows property on your ServiceNow server. Check with your administrator. This would replace the default 'sysparm_query=workflow_state=published^active=true'.
  • Use custom metadata field list: If true, Include include metadata fields for the Knowledge Article table, instead . Instead of querying all the available metadata fields on the table, you can set a list of metadata fields, for . For instance, : short_description,sys_updated_on,number,sys_id,sys_updated_by,sys_created_by,text,kb_knowledge_base.
  • Use User Criteria table: If true, the crawl will query User Criteria table , in order to get the sys_id and description for every active User criteria. Please noticed, if If the security option is Use User Criteria, this option is overridden to true..
  • Use Parallel Processing: If true, the scan will query the minimum amount number of fields to start processing in parallel, then . Then the populate will complete the item's metadata. In the other case, the scan queries for all the metadata and create creates the items and the populate only is going to add the acl ACL section. This reduce reduces the number of calls to Servicenow the ServiceNow server, but it's slower, very heavy on the scan stage.
  • Choose Pattern Field: the field to be used when including/excluding articles.
  • Include Patterns: the patterns to be used to include articles for the crawl.
    
  • Exclude Patterns: the patterns to be used to exclude articles from the crawl. 
  • Include Knowledge Article Attachments: if enabled, knowledge articles' attachments will be crawled.
    • Include or Exclude Attachments Using Patterns: enable to allow filtering by using include/exclude patterns for articles' attachments.
      • Use Mime Type for Patterns: if enabled, the connector will match the patterns using the mime type  of the attachment instead of the file name.
      • Include Patterns: the patterns to be used to include attachments for the crawl.
        
      • Exclude Patterns: the patterns to be used to exclude attachments from the crawl. 

Step 5. Specify the Catalog Items and Attachments configuration (Optional)

The "Catalog “Catalog Items and Attachments" Attachments” section is located between the "Articles “Articles and Attachment" and "Connector" Attachment” and “Connector” sections of the "Seed" “Seed” page. Here you need to set the following options for this section of the Seed. If no options are modified, default values are used:

• Include Catalog Items : if enabled, catalog items will be crawled.
  
• Include Catalog Model Fields: if enabled, includes the key fields of the model associated to the catalog item.
• Use empty Roles: If true, the crawl will use Roles=Null as a filter for the documents. The query would be 'sysparm_query=roles=NULL^active=true' otherwise . Otherwise, it will be active=true.
• Use User Criteria table: If true, the crawl will query the User Criteria table, in order to . To get the sys_id and description for every active User criteria, also as part of the Public security, the connector would use Available For and No Available For user criteria fields to make sure the Catalog Items are public. Please noticed, if If the security option is Use User Criteria, this option is overridden to true..
• Use Parallel Processing: If true, the scan will query the minimum amount number of fields to start processing in parallel, then . Then the populate will complete the item's metadata. In the other case, the scan queries for all the metadata and create creates the items and the populate only is going to add the acl ACL section. This reduce reduces the number of calls to Servicenow the ServiceNow server, but it's slower, very heavy on the scan stage.
• Security: Choose what type types of Acls ACLs would have the Catalog Items Items:
  

  • Public: Only public items will be

    crawl

    crawled (roles=null). If possible, the connector will verify if the Available field is set

    ,

    . It should

    be

    have only public User Criteria values. If No Available For field is set, the item will not be crawled.

  • User Criteria:

    Acls

    ACLs for Catalog items and attachments will be the sys_id of the Available For and No Available For fields (requires server configuration)

• Choose Pattern Field: the field to be used when including/excluding catalog items.
• Include Patterns: the patterns to be used to include catalog items for the crawl.
  
• Exclude Patterns: the patterns to be used to exclude catalog items from the crawl. 
• Include Catalog Item Attachments: if enabled, catalog items' attachments will be crawled.
• Include or Exclude Attachments Using Patterns: enable to allow filtering by using include/exclude patterns for catalog items' attachments.
• Use Mime Type for Patterns: if enabled, the connector will match the patterns using the mime type  type of the attachment instead of the file name.
• Include Patterns: the patterns to be used to include attachments for the crawl.
  
• Exclude Patterns: the patterns to be used to exclude attachments from the crawl. 

Step 6. Specify a Connector.

The "Connector" “Connector” section is located between the "Catalog “Catalog Items and Attachments" Attachments” section and the "Connection" “Connection” section of the "Seeds" “Seeds” page. Here you must select a previously created ServiceNow Connector for the Seed, from the Connector combo box.

Step 7. Specify a Connection.

The "Connection" “Connection” section is located between the "Connector" “Connector” section and the "Workflows" “Workflows” section of the "Seeds" “Seeds” page. Here you must select a previously created ServiceNow Connection for the Seed, from the Connection combo box.

Step 8. Specify Workflows (Optional).

The "Workflows" “Workflows” section is located between the "Connection" “Connection” section and the "Tag" “Tag” section of the "Seeds" “Seeds” page. Here, you can select previously created Workflows that apply to the seed. If no workflow is specified, a default workflow is assigned.

Step 9. Specify a Tag (Optional).

The "Tag" “Tag” section is located between the "Workflows" “Workflows” section and the "Policies" “Policies” section of the "Seeds" “Seeds” page. Here you can, if desired, specify a tag for seeds filtering.

Step 10. Specify Policies (Optional).

The "Policies" “Policies” section is the last section, located right below the "Tag" “Tag” section of the "Seeds" “Seeds” page:

• Throttle Policy: here, you can select a previously created Throttling Policy from the Throttle Policy combo box.
• Route Policy: here you can select a previously created Routing Policy from the Route Policy combo box.

Step 11. Save the Seed.

Click on the "Complete" “Complete” button to save the new Seed (when updating, the button option will read "Save" “Save” instead of "Complete"“Complete”).

Step 12. Running the crawl.

To run a crawl for a ServiceNow Seed, click on the button for the seed you want to run and select Full, Incremental or Identity Crawl. This will start the chosen crawl for your seed.