ASM
ASM HERMES
ASM
ASM HERMES
  • Welcome to ASM HERMES!
    • HERMES 10.6.8 Release Notes
      • 10.6.8.14379 AUG 24 MR Release Notes
      • 10.6.8.14627 SEPT 24 MR Release Notes
      • 10.6.8.14701 OCT 24 MR Release Notes
      • 10.6.8.14800 OCT 24 2 MR Release Notes
      • 10.6.8.14879 NOV 24 MR Release Notes
      • 10.6.8.14901 N0V 24 2 MR Release Notes
      • 10.6.8.15038 DEC 24 MR Release Notes
      • 10.6.8.15097 JAN 25 MR Release Notes
      • 10.6.8.15121 JAN 2 25 MR Release Notes
      • 10.6.8.15289 FEB 25 MR Release Notes
      • 10.6.8.15348 FEB 2 25 MR Release Notes
      • 10.6.8.15509 MAR 25 MR Release Notes
      • 10.6.8.15572 APRIL 25 MR Release Notes
    • HERMES 10.6.9 RC Release Notes
      • 10.6.9.14735 OCT 24 RC Release Notes
    • ASM Video Library
  • ITSM Solutions
    • Example Solutions - Best Practices for a Successful Outcome
      • Managing Changes to your ASM Application
      • Business Continuity Planning
      • Capacity Planning
      • Change Management
        • Planning Change Management
        • Build Your Workflow
      • Dynamic Ticket Routing
      • Environmental Impact Analysis (for TBL Accounting)
      • Knowledge Management
        • Planning Knowledge Management
      • Major Incident Management
        • Configure Major Incident Management
        • Allow Users to Subscribe to MI
      • Project Management
        • ASM Project Management How-To Videos
      • Service Validation and Testing
        • Example Configuration
      • User Survey Systems
        • Planning and Implementing Surveys
        • Survey Fields and Configuration
      • Workforce and Talent Management
        • Example Configuration
      • 2-Part Call Close Process
      • Incident Management
        • Planning Your Incident Management Implementation
        • Setup IPK Management
        • Build Screens to Support IPK
  • Use ASM
    • About the Alemba Service Manager Family
      • URLs and Access Parameters
        • System Access URLs
        • ASM Self Service Portal URLs
        • Pre-Populating Search Fields
    • Using the Self Service Portal
      • Logging on to Self Service Portal
        • Forgotten User ID and Password (Self Service Portal)
        • Password Expiry
      • Self Service Portal Home Page
      • Self Administration in Self Service Portal
        • Updating Your Contact Details
        • Changing Your Password
        • Delegating Work
      • Logging and Reviewing Tickets and Tasks/Approvals
        • Using the Logging Forms in Self Service Portal
        • Suggested Knowledge in the Self Service Portal
        • Reviewing Your Tickets in the Self Service Portal
          • Cloning Tickets in Portal
          • Chasing Ticket or Request
        • Off-Line Conversations with Support
        • Closing Your Tickets
        • Reopening Your Tickets
        • Cloning Your Tickets
      • Following Tickets
      • Self-Help/Self-Diagnosis in Portal: Scripts
      • Searching the Knowledge Bank in Self Service Portal
      • Chat
        • Alembot - Chatbot
      • Service Request Catalog
      • Your Surveys
    • Using Nano
      • Nano Feature List
      • NANO Video Tutorial - Quick Start
      • Nano Application
        • Viewing Your Workload in NANO
        • Viewing Bulletins
        • Nano Matching Panel
        • Using the Call, Request, and Task Details window
        • Working with Entities in Nano
          • Followers
        • Using Resource Manager in NANO
        • Viewing Your Outstanding Tasks
        • Keyboard Shortcuts
    • Using ASM Core
      • Getting Started
        • The ASM Core Window
          • The Information Panel
          • The View Option
          • The New Option
          • Configuring search results
        • Changing your Password
        • Generating an ASM statistics report
        • Printable Reports from within Core
        • Searching for Items
          • Using Wildcards in Search
          • Outstanding Item Searches
          • Saved searches
          • Viewing Search Results in Graphs
          • Creating Reporting Views from Search Results
        • Indicators - Icons
      • View Your Consolidated Workload
      • Viewing Daily Stats
      • Chat
      • Managing Followers
      • Managing Your Tickets - Calls and IPK
        • Working with Calls
          • About the Call Details Window
          • Cloning Option
          • Log New Request from Call
          • Watch Call
          • Change a Call from an Incident to a Problem, Known Error, Major Incident, or Service Request
          • About the Service Window
          • About the Call Information Panel
          • About the Matching Panel
          • Add Notes - Updating Your Tickets
            • Notes: Offline Conversations with the User
          • Managing and Using Call Activities
          • Assigning Work Based on Skills
        • Call Details Explorer Options
          • Call Activities Explorer Option
          • Linking Explorer Option
          • Forum Analysts Explorer Option
          • AI Ops Explorer Option
          • Viewing Event Transactions from a Call or Request
          • Email All Explorer Option
        • Overview of CTI in Alemba Service Manager
          • Storing Telephone Numbers for CTI
        • Logging a Call
        • Using Quick Solutions
        • Using Quick Forms
        • Deferring a Call
        • Reassigning/Forwarding a Call(s) Internally
        • Forwarding a Call Externally
        • Creating an Outage from a Call
        • Closing a Call
        • Global Updates
        • User Chased Tickets
        • Escalating Tickets
      • Sending Ad-Hoc Surveys
      • Requests and Tasks
        • Viewing your Request Workload
          • Viewing Outstanding Requests
          • Searching for Requests
        • Submit a New Request
        • Escalate a Request
        • Searching for Tasks
        • Suspending a Task
        • Completing a Task
        • Sending email from a task
        • Forwarding a Task Internally - Reassignment
        • Completing an Approval
        • Managing Change Calendars
        • Managing Resources
          • Preparing to Use Resource Manager
          • Using Resource Manager
          • Allocating Tasks in Resource Manager
      • Ordering Service Actions within ASM Core
      • Adding Attachments
      • Managing your CMDB
        • Managing CMDB Items
          • Cloning CMDB Items
          • Completing CMDB Item Details
          • CMDB Linking Diagram
          • Freezing CMDB Items
          • Linking CMDB Items
        • Managing Your Assets
          • Managing Inventory Items
          • Managing Software Products
          • Thresholds Explorer Option
          • Managing Transactions
            • Purchasing Items
            • Reserving Items
            • Allocating Items
            • Transferring Ownership of Items
            • Retiring Items
            • Changing Availability Status of Items
            • Adding an order from a search field
          • Specifying Usage Criteria
        • Managing your Service Portfolio
          • Managing Services
          • Managing Service Actions
            • Defining the Outcome of Selecting a Service Action
          • Managing Service Bundles
        • Managing Organizations
        • Managing Locations
        • Managing Cost Centers
        • Managing Jurisdictions
        • Managing Subscriber Groups
        • Managing Stakeholders
        • Options in the CMDB Items Explorer Pane
        • Allocating Change Windows to CMDB Items
        • Managing People
        • Managing Contracts
        • Managing Availability
          • Managing Outages
          • Impact Criteria
          • Displaying Outages
        • SLM - Managing Agreements
          • Defining Agreement Thresholds
          • Linking Service Items to an Agreement
          • Attaching Selection Criteria to Agreements
          • Agreement Measurements
      • Configuring AI Ops
        • Using the AI Ops Wizard
        • Managing AI Ops Rules
      • Knowledge Management
        • Managing Knowledge Entries
        • The Knowledge Bank Explorer
        • Viewing Knowledge Entries
        • Knowledge Administration
      • Configuring Reminders
      • Using IPK Workflow Rules
        • Part 1 - Building the Workflows
        • Part 2 - Defining Workflow Criteria Rules
          • Defining Call Fields for IPK Rules
        • Part 3 - Assigning Workflows to Rules
        • Configuring Call Auto Close Rules
        • Running Multiple Workflow Types on a Call
      • The Bulletin Board
        • Viewing Bulletins
        • Managing Bulletins
      • Using Timesheets
      • Scheduling Calls and Requests
      • Using Quick Forms
      • Using Call Scripts in Core
      • Instant Messaging/Internal Messages
      • Sending an Email
        • Finding Recipients
      • Delegation Setup
      • Purging Data
  • SetUp & Configure ASM
    • Licensing
      • Licensing model
      • ASM Person Licenses
    • Installation and Patching
      • Alemba Service Manager On-Premise Architecture
      • HERMES Installation Guide
        • HERMES Prerequisites
        • Upgrading/Installing ASM to HERMES Step by Step Guide
      • Installation PowerShell Parameters
        • Administration Using PowerShell Scripts
      • Installation Guide for Syncfusion Dashboards
        • Part 1-Syncfusion Dashboard Server Installation
        • Part 2-Syncfusion Server Check HTTPS Binding has been Configured
        • Part 3-Syncfusion Server User Management Server (UMS) Configuration
        • Part 4-Syncfusion Server Configure the Dashboard Server
        • Part 5-Syncfusion Server Patching the Scheduler Service
      • Upgrading from vFire 9.2 or Below
      • Installing and upgrading on Multiple Web Servers
      • Patching where downloading files is not possible
        • Installation Using Setup.exe
      • Configuring external network access to ASM
      • About the Polling Services
      • Uninstalling ASM Core
    • Setting Up your System
      • On-Premise: System Console Configuration Settings
      • Logging in as Administrator
      • ASM Nano
        • Enabling Nano
        • Request Phases
      • Setup IM (Internal Messaging)
      • Setup Email
        • Setting Up Incoming and Outgoing Email
          • Email Server Configuration
          • Methods of Authentication for Mail Servers
          • Incoming Email
            • Recognized Incoming Email Subject Headings
            • Incoming POP3, and IMAP Email Server Settings
            • Incoming Email via API
            • How the Logging Analyst is Determined on an Incoming Email
          • Outgoing SMTP Email Server Settings
          • Outgoing Email via Webhooks
          • Configure Azure MS Graph API
          • Configuring Exchange Web Services (EWS)
            • Prerequisites
              • Web Redirect URL Configuration
              • Creating an Azure Client Secret
            • EWS - Configure Outgoing Email
            • EWS - Configure Incoming Email
            • EWS - Authorize the Connection
            • EWS - Troubleshooting
        • Mail Message Access (MMA)
      • Setup Chat
    • Configuring your System
      • Accessibility Features
      • ASM Solutions
      • Call Template Administration
      • Configuration Post Go-Live
        • Preparing Production for Sys Admins and Developers
        • ASM Application Configuration Change Management
          • ASM Application Configuration Change Screens
          • ASM Application Change Workflow Template
      • Configuration Post Go-Live using SDLC
      • Configuring Escalations and Chase
      • Configuring the Data Purge Service
      • Configuring Screens
        • Creating New Screen Sets
        • Screens Available for Configuration using ASM Designer
        • Building Screens in ASM Designer
          • Configuring Fields
          • Creating a Custom Field
          • Deleting & Unlinking Fields
            • ASM System Fields for Call Screens
            • ASM System Fields for Request Screens
            • ASM System Fields for Task Screens
            • ASM System Fields for Approval Screens
            • ASM System Fields for CMDB Item Screens
          • Screen Widgets
            • Data-Grid Widgets
            • Self Service Portal System Widgets
          • Knowledge Article Screens
          • Configuring Message Templates
          • Importing/Exporting Screens
          • Troubleshooting Screens: The Screen's Dead Zone
        • Dynamic Screens
          • Deep Linking Field Data Across Screen Sets
          • Field Calculations
          • Using Rules
          • Adding Images and Progress Indicators to your screens
        • Deleting a Custom Screen
        • Configuring Button Labels
      • Conversation History Widget For Nano
      • Customizing Options for the Self Service Portal
        • Add Me: Set up "Add-Me" for Subscribing to or Following Issues
        • Styling the Self Service Portal
        • Enable Request Correction and Resubmission
      • System Administration Settings
        • Custom Global Profile Fields
        • System Settings Menu
          • Your Organization
          • Partitioning
            • Configuring Partitions
            • Partition Settings
          • System Settings
          • Security Profiles
          • Server Time Zone
            • Storing Time Zone Information
            • Time Zone Settings
          • Defining Working Hours
          • Defining public holidays
          • Reset References
          • System Source Titles
          • Browse Limits
          • Messaging
          • Message Types
            • Message Type Definitions
          • Pager Settings
          • Pager Types
          • Activity Log
          • Stored Procedures
          • System Titles
          • Quick Launch
          • Quick Notes
          • Auditing
            • Administration Audit Trail
          • User and Analyst Search Field Settings
          • Email Header and Footer
        • Security
          • Security Settings
          • Security Settings (Partitioned)
          • IPK Groups
          • Workflow Management Groups
          • Controlling log in
          • Email and Pager Options for IPK and Workflow Groups
        • Security Roles
          • General Access Security Role
            • Admin Tab
            • Timesheets Tab
          • IPK Management Security Roles
            • IPK Management Role: Options Tab
            • IPK Management Security Role: Groups Tab
            • IPK Management Security Role: IPK Streams Tab
            • IPK Management Security Role: IPK Statuses Tab
            • IPK Management Security Role: Forms Tab
            • IPK Management Security Role: Quick Launch Tab
            • IPK Management Security Role: Fwd Groups Tab
          • Workflow Management Security Roles
            • Workflow Management Security Role: Shared Tab
            • Workflow Management Security Role: Requests Tab
            • Workflow Management Security Role: Tasks Tab
            • Workflow Management Security Role: Processes Tab
            • Workflow Management Security Role: Groups Tab
            • Workflow Management Security Role: Request Screen Sets Tab
            • Workflow Management Security Role: Task Screen Sets Tab
            • Workflow Management Security Role: Appr. Screen Sets Tab
            • Workflow Management Security Role: User Approval Screen Sets Tab
            • Workflow Management Security Role: External Supplier Screen Sets Tab
            • Workflow Management Security Role: Closure Task Screen Sets Tab
            • Workflow Management Security Role: Forms Tab
            • Workflow Management Security Role: Template Tab
            • Workflow Management Security Role: Request Quick Launch Tab
            • Workflow Management Security Role: Task Quick Launch Tab
          • Configuration Management Security Roles
            • Configuration Management Security Role: CMDB Items Tab
            • Configuration Management Security Role: People Tab
            • Configuration Management Security Roles: Organizations Tab
            • Configuration Management Security Role: Locations Tab
            • Configuration Management Security Role: Contracts Tab
            • Configuration Management Security Role: Subscriber Groups Tab
            • Configuration Management Security Role: Cost Centers Tab
            • Configuration Management Security Role: Jurisdictions Tab
            • Configuration Management Security Role: Forms Tab
          • Service Level Management Security Roles
            • Service Level Management Security Role: Options Tab
            • Service Level Management Security Role: Forms Tab
          • Availability Management Security Roles
          • Knowledge Management Security Roles
            • Knowledge Management Security Role: Options Tab
            • Knowledge Management Security Role: Content Access Tab
            • Knowledge Management Security Role: Statuses Tab
          • Bulletin Board Security Roles
          • Dashboard Management Security Role
          • Integration Security Role
        • IPK and Workflow
          • Incident, Problem & Known Error (IPK) Management
            • Configuring IPK Settings
            • IPK Settings (Partitioned)
            • Action Type
            • Call Attributes
            • Call History Types
            • Call Impact
            • Call Physical Statuses
            • Call Priority
            • Call Screen Sets
            • Stakeholder Roles
            • Call States
            • Call Status Titles
            • Call Urgency
            • Closure Groups
            • Custom Call Profiles
            • User Survey
            • User Survey Screen Set
            • IPK classes
            • IPK Streams
            • IPK Statuses
            • Link Stream/Status to Call Screen Set
            • Link Type/Stream/Status to Call Screen Set
            • Link Screen Set to Reasons
            • Link Type to Reason
            • Limit Type by IPK Status
            • Link Type to Call Screen Set
            • Priority Matrix
            • Quick Forms
            • Quick Solutions
            • Reasons
            • Call Scripts: Scripting
            • Type Tiers
          • Workflow Management
            • Workflow Management Settings
            • Workflow Attributes
            • Approval Types
            • Request Action Types
            • Request Implementation Profiles
            • Request Implementation States
            • Request Link Types
            • Request Physical Statuses
            • Request Phases (Nano)
            • Request Priority
            • Request Risks
              • Request Risk Assessment
              • Request Impact
              • Request Complexity
              • Request Risk Assessment Matrix
            • Screen Sets for Requests, Tasks and Approvals
            • Request Stakeholder Roles
            • Request Completion Statuses
            • Request Types
            • Task Action Types
            • Task Phases
            • Task Physical Statuses
            • Task Priority
            • Task Status Titles
            • Task Types
            • Workflow Management History Types
            • Request History Filters
            • Workflow Processes
            • Workflow Export and Import - Workflow Porting
            • Linking Approval Screens to Partitions
        • Service Level Management
          • SLM Settings
          • Agreement Attributes
          • Agreement Selection Priority
          • CMDB Selection Priority
          • Agreement Stakeholder Roles
          • Agreement Statuses
          • Exclusion Reasons
          • Agreement Types
          • Event Activity Types
          • Agreement Matrices
          • Measurement Types
          • Payment Types
        • CMDB (Configuration Management Database)
          • CMDB Settings
          • CMDB Service Levels
          • CMDB Item Classes
          • CMDB Item Criticality
          • CMDB Item Physical Statuses
          • CMDB Item Types
          • CMDB Link Status
          • CMDB Link Types
          • Contract Support Type
          • Contract Types
          • Cost Center Category
          • Custom CMDB Profiles
          • Person Profile
          • External Contact Type
          • User VIP Statuses
          • Disposal Methods
          • Financial Statuses
          • Financial Category
          • Freeze Statuses
          • Link Manufacturer to Model Type
          • Manufacturers
          • Model Types
          • Organization Profiles
          • External Supplier Statuses
          • Purchase Method
          • Service Link Types
          • Service Portfolio Statuses
          • Service Cost Types
          • Service Periods
          • Asset Management - Asset Lifecycle Status
          • Asset Management - License Type
          • Asset Management - Transaction Status
          • Self Service Portal Display Categories
          • Stakeholder Roles
          • Auditing Configuration Items
        • Availability
          • Configuring Availability Management
          • Outage Types
          • Schedule Definition
        • Depreciation
          • Batch Run Parameters
          • Depreciation by CMDB Item Type
          • Depreciation Methods
          • Depreciation Schedules
        • Knowledge Bank
          • Knowledge Bank Settings
          • Knowledge Base Types
          • Knowledge Entry Types
          • Knowledge Profiles
          • Knowledge Ratings
          • Knowledge Statuses
          • Knowledge Document Import
        • Bulletin Board
          • Configuring the Bulletin Board
          • Bulletin Board Priorities
          • Bulletin Stakeholder Roles
        • Text Retrieval
          • Common Words
          • Keywords
          • Synonyms
        • Analytics
          • Analytics Settings
          • Classic Syncfusion Dashboard Server Configuration
        • Self Service Portal
          • Self Service Portal Settings
          • Self Service Portal Settings (Partitioned)
          • Self Service Portal Roles
            • Options Tab
            • CMDB Tab
            • Content Access Tab
            • Workflow Templates Tab
            • Call Templates Tab
            • IPK Status Tab
            • Dashboard Management Tab
          • Self Service Portal Systems
          • Self Service Portal My Options
          • Self Service Portal Tables
          • Service Order Status Titles
          • Question Mappings
          • Catalog Promoted Items
          • Suggested Knowledge in the Self Service Portal
          • Creating Custom Pages
          • Link Organization to Portal Key
        • Nano
        • Preview Features/Advanced Options
          • Settings
            • Multi Language
              • Languages
                • Portal Label Language Updates
                • Service Title Language Updates
            • Call Activities
            • Enable Active Directory Mappings to Sub Groups
            • CTI
              • Setting up the Alemba Service Manager CTI
            • SignalR Scale Out Options
            • External Chat tool Integrations
          • Portal Settings
          • Global Search
          • Chat Bot
      • Workflow Template Administration
        • Basic Process for Building a Workflow
          • Task List for Workflow (Request Template) Creation
            • Create a Service Action and Attach a Workflow to it
        • Managing Tasks - Adding Tasks to the Dependency Diagram
          • About Tasks - General
          • Task Types in the Task Palette
            • Defining Request Start Details
            • Creating a Standard Task
            • Create Request Task
            • Creating an Approval Task
            • Creating a User Approval Task
            • Conditional Branching Tasks
              • Defining a Dependency Rule
              • Defining Dependency Actions
            • Creating a Messaging Task
            • Creating a Delay Task
            • Creating a Manage CMDB Task
              • Recursive CMDB Task
              • Adding Transactions to a Manage CMDB task
              • Asset Management Transactions in a Manage CMDB Task
              • Mapping Fields to be Updated by a Transaction
            • Creating an Outbound Action Task
            • Creating an SLM Start Clock/Stop Clock Task
            • Creating an External Supplier Task
            • Creating a Run External Procedure Tasks
            • Creating a Change Window Task
            • Creating a Closure Task
            • Creating an Activation Task
        • Component Workflows
        • Setting Up Amendable Requests
        • Troubleshooting Workflow and Service Action Linking
        • Sharing Parent Request Items with Child Requests
    • Dashboards and Reporting
      • Dashboard Configuration and User Learning Guide
      • Descriptions of Default Reports and Dashboards (SDI Classifications)
        • 8.3 Number of Incidents and Service Requests
        • 8.4 Average Time to Respond
        • 8.6 Average time to resolve incidents or fulfill service requests
        • 8.7 First Contact Incident Resolution and Request Fulfilment Rate
        • 8.8 First Level Incident Resolution and Request Fulfillment Rate
        • 8.9 Reopned Incident Rate
        • 8.10 Backlog Management
        • 8.11 Percentage of hierarchic escalations
        • 8.21 Percentage of Functional Escalations copy
        • 8.23 Average incident resolution time by priority
        • 8.24 Average request fulfilment time by priority
        • 8.25 Average resolution time by incident category
        • 8.26 Average fulfilment time by service request type
        • 8.27 Comparison of service level targets to performance
        • 8.28 Service Desk Knowledge Usage
        • 8.29 Customer Facing Knowledge Usage
        • 8.30 Service Desk Knowledge Quality and effectiveness
        • 8.31 Customer facing knowledge quality and effectiveness
        • 8.33 Monitoring Incidents caused by changes measured against target
        • 8.34 Total cost of service delivery
        • 8.35 Average cost per incident by channel
        • 8.36 Average cost per service request by channel
        • 8.43 Problem records created through proactive problem management
        • 8.44 Incident reduction through problem management
      • Install SDI Reporting Pack
      • Dashboards and Reports (.sydx Files)
      • Connecting to Other Data Sources
      • Sample SQL Queries
      • Migrating your Syncfusion Dashboards to a New Server
    • FAQ
      • Limited Support/End of Life Capabilities
        • Configuration Portability
          • Overview & Best Practices
          • Porting Configuration Data
          • Viewing the Export and Import Logs
        • Server Console
          • Accessing the Server Console
          • Creating a New ASM System
          • Server Console system tasks
          • Customization nodes
          • SQL Server and Table Ownership
          • Updating Scripts
          • ASM Core Registry Keys
        • Concurrent Licensing
          • License Corrals
        • Alemba Classic API
          • Programming with the Classic API
            • WCF Client
          • Code Examples
          • Return Values
          • API Message Types
          • API Lookups
          • API Transactions
            • Availability Transactions
            • Call Transactions
            • CMDB Item Transactions
            • Contract Transactions
            • Cost Center Transactions
            • Jurisdiction Transactions
            • Location Transactions
            • Organization Transactions
            • Person Transactions
            • Subscriber Group Transactions
            • Knowledge Transactions
            • Bulletin Transactions
            • System Transactions
              • Session Transactions
              • Add Note Transactions
              • Attribute Transactions
              • Development Transactions
              • Message Transactions
              • Object Transactions
              • Stakeholder Transactions
            • Workflow Transactions
              • Workflow (Request) Transactions
              • Task Transactions
          • API Classes
          • API WSTester Application
      • Configuration or Customization
  • Integrate
    • Integration Overview
    • Managing Integration
      • Setting Up the Integration Platform
        • Defining Connectors
        • Defining Sources
        • Configuring an Integration Source
        • Resource Mapping
        • Defining Property Transforms
        • Defining Profile Maps
        • Defining Resolution Rules
        • Defining Link Type Mapping
      • Single Sign-On using SAML
        • Integrated Security vs. Single Sign On
        • Technical and Access Requirements
        • Configuring ASM for Single Sign-On
        • Importing Identity Provider Metadata
        • Service Provider Signing Certificate
        • Configuring the Service Provider
        • Exporting Service Provider Metadata
        • Importing Service Provider metadata into the Identity Provider
        • SSO Troubleshooting
        • SSL Binding
        • Creating a Self Signed Certificate
        • Extending the Single Sign-On Connector
      • Configuring Azure Active Directory discovery
      • Azure Multi-factor Authentication
      • Viewing Integration Activity
        • Viewing Integration Log
      • Connectors to ASM Core
        • Connector Matrix
        • Installing Connectors
        • CMDB Connectors
          • Altiris Network Discovery Connector
          • CA Cohesion Connector
          • Centennial Discovery/FrontRange Connector
          • EMC Smarts NCM Connector
            • Service Assurance Manager Connector
          • LANDESK Connector
          • Microsoft Azure Connector
          • Microsoft SCOM Connector
          • Microsoft SMS and SCCM Connector
          • Snow Connector
          • SolarWinds Connector
          • VMware Application Discovery Manager Connector
          • VMware vCenter Configuration Manager Connector
          • VMware vCloud Director Connector
          • vRealize Orchestrator Connector
        • LDAP Connectors to ASM Core
          • Microsoft Active Directory Server Connector
          • Novell eDirectory Server Connector
        • Generic Connectors to ASM Core
          • Email Event Connector
          • External Process Connector
          • Stored Procedure Connector
          • ASM to ASM Connector
          • Jira Connector
            • Developer Notes for the Jira ICNF
          • CSV File Connector
          • MS Azure DevOps Connector
          • Connector Suite for MS SQL Server Tables
          • Resource Databases Connector
            • Tutorial for Configuring the Database Resources Connector
        • Microsoft Alemba ITSM Connector
      • Build your Own Connector
        • Microsoft Entra ID (Azure Active Directory) - Connector Builder
        • Microsoft Intune - Connector Builder
      • Managing the Federated CMDB
        • Managing Scheduled Integration Scans
        • Auditing Configuration Items
      • Managing External Resources
      • Selecting Fields for Mapping
      • Managing Inbound and Outbound Actions
        • Configuring Inbound and Outbound Actions
          • Configuring Outbound Actions
            • Using Outbound Actions
          • Configuring Inbound Actions
        • Inbound or Outbound Action Source Parameters
      • Managing Events
        • Configuring Event Management
          • Event Management Source Parameters
          • Viewing Event Types
          • Managing Event Type Mappings
        • Using Events
      • Webhooks
        • Webhook Payloads
      • Canvas App Widgets
      • Microsoft Teams Chat Integration
      • Microsoft Project Integration
      • Connector Diagnostics
    • API's
      • Alemba RestFul API
        • Alemba API Architecture
        • Installing the Alemba API
        • Logging In to the Alemba API Explorer
        • Navigating the Alemba API Explorer
        • Alemba API Programmers’ Guide
        • Alemba API Programmers' Cookbook
          • Recipes
        • Alemba API Related Database Tables
        • Using API Reporting Views
        • Authentication
          • Configuring Authentication for the Alemba API
          • Configuring Windows Authentication for the Alemba API
          • Configuring Single Sign On using SAML for the Alemba API
      • Azure/ Web API/Logic Apps
      • ASM API Quick Reference Guide
        • Getting Started: The ClientId
        • Postman for Testing
        • Search for Existing Calls
        • Locking and Updating Calls
        • Creating New Calls
  • Earlier Versions of ASM
Powered by GitBook
On this page

Was this helpful?

  1. SetUp & Configure ASM
  2. Setting Up your System
  3. Setup Email
  4. Setting Up Incoming and Outgoing Email

Incoming Email

The ASM Core Incoming Email module provides great flexibility for a support desk or workflow management system.

Last updated 2 months ago

Was this helpful?

The ASM Core Incoming Email module provides great flexibility for a support desk or workflow management system. Any person with access to email can, for example, log calls and action tasks by way of a specific email address. The mail server holding this address will routinely check for these messages and log or update calls and tasks accordingly. This functionality is especially useful for analysts who are out fixing problems in the field or people who are traveling or using hand-held devices and have limited Internet access.

ASM Core has a polling service which can be configured to check a number of incoming mail accounts for any received email messages. If the polling service picks up an email, it can take the appropriate course of action, whether it is to log or close a call, approve or reject tasks, or simply update an existing call, request or task.

The action to be taken is dependent on:

  • the subject line of the email. Refer to for details.

  • the settings configured for the incoming email account in in System Administration.


The following actions can be taken as a result of an incoming email:

  • log calls

  • update calls

  • return a summary of calls

  • close calls

  • reopen closed calls

  • approve an Approval Task or User Approval Task

  • reject an Approval Task or User Approval Task

  • update a task or approval

  • update a request

  • return a summary of requests

  • return a summary of tasks and approvals

Once the polling service has processed an incoming email, the email is deleted from the mailbox. This is to prevent ASM Core from logging new calls from the same email. If you want to keep a copy of these emails, it is recommended that you set up your mail server such that it sends a copy of every email received by the mailbox used for ASM Core incoming email to another email account.

ASM Core considers SMTP error numbers 501, 503, 550 and 553 to be permanent and fatal errors.

If ASM Core receives an incoming email with any of these errors, it will immediately delete this message and the message cannot be recovered.

Alemba® recommends that if any incoming emails show these error numbers, the mail administrator should review the mail infrastructure to determine the origin of these errors

Logging a Call with Email

Subject Line/Email Subject

  1. A System String Field Called "Call Title" exists for Calls created from Email.

  2. ASM will input the Email Subject Line into this field automatically when creating a New Call from email.

  3. To see this information on the Call, you will need to add the "Call Title" field in Screen Designer to any screen set used to create a call from email

Note: You can discover what these screens are by viewing the call template linked to your incoming email configuration(s).

A New Call is Logged When:

  1. Unrecognized Subject Line - If the messaging service picks up an incoming email but does not recognize the email’s subject line, ASM Core will log a call based on the details of that email.

  2. Invalid Call Numbers - A call will also be logged if the email matches a recognized subject line but has an invalid call number and the Log New Call on Invalid Number option is selected on the incoming email server. If Log New Call on Invalid Number is not selected, the email will be discarded and the person who sent the email will not be notified.

  3. Invalid Request or Task Number - If the email matches a recognized subject line but has an invalid request or task number, a call is always logged (whether Log New Call on Invalid Number is selected or not in System Administration).

Who is the User and Logging Analyst?

  1. When a call is logged by incoming email, ASM Core looks in the CMDB for a User or analyst with an email address matching the address used to send the email.

  2. Based on these findings and the settings for the incoming email account used, ASM Core will allocate a User and logging analyst for the new call:

Create New Calls Anonymously: The email address is not defined for an existing User or Analyst in ASM Core.

  • If an email is sent from an address which does not correspond to any existing ASM Core User or analyst, and Create New Calls Anonymously is selected for the incoming email account, a new User record is created (that is, a new person record flagged as a User) and the call is logged with this User specified in the User field.

  • The logging analyst is set to the analyst specified in the Default Logging Analyst field on the incoming email account.

  • If the Create New Calls Anonymously option is not selected for the incoming email account, a call is not created.

Analyst Only: The email address is defined for an existing Analyst (who is not also flagged as a User).

  • If an email is sent from an address which corresponds to an existing analyst in the ASM database and this analyst is flagged as an analyst only (not as a User), the call is logged with this person specified in the User field.

  • The logging analyst is set as follows:

    • If the Use Linked Analyst option is not selected for the incoming email account, the logging analyst is set to the analyst specified in the Default Logging Analyst field for the incoming email server.

    • If the Use Linked Analyst option is selected for the incoming email account, the logging analyst is set to the person who sent the email.

    • If an analyst logs a call by incoming email and he is not already a User, the User flag will be selected on the analyst’s person record

Person is an Analyst and a User: The email address is defined for an existing person who is flagged as both an Analyst and a User.

  • If an email is sent from an address which corresponds to an existing person record in the ASM database and this person is flagged as both an Analyst and a User, the call is logged with the person specified in the User field.

  • The logging analyst is set as follows

    • If the Use Linked Analyst option is not selected for the incoming email account, the logging analyst is set to the analyst specified in the Default Logging Analyst field for the incoming email server.

    • If the Use Linked Analyst option is selected for the incoming email account, the logging analyst is set to the person who sent the email.

Other Actions

  1. The next available number is assigned to that call and the body of the email is automatically entered as the description.

  2. The other fields are left blank, with the exception of the User field, which is filled in depending on who logged the call (see above).

  3. If there are any attachments to the email, they are added as objects attached to the call.

  4. The call will use the call template specified for the mail server that picked up the incoming email.

  5. The call template will determine the call properties such as the partition, call screen set, IPK status and stream, assigned analyst and group, and so on.

  6. Any objects attached to an incoming email will use the Unspecified security profile when added as an object on the logged call.

  7. The history entry that is recorded about attaching this object will also use the Unspecified security profile.

  8. If you have renamed the Unspecified profile, that name will be reflected instead.

Call Title

Populate Call Title from Email Subject

Available as of 10.6.8.14253

To have the call title reflect the subject of the email that was sent to ASM, you will need to add the "Call Title" field to the target screen in ASM Screen Designer.

Please note, "Populate Call Title from Email Subject" must be enabled in the Incoming Email Server Details located in: System Administration>System>Email Settings>Incoming Email Server.

Subsequent Emails processed for the Call will not update the Call Title field. The Call Title Field can still be manually updated by an Analyst or entered by the Analyst during the lifecycle of the call.

Updating a Call with Email
  1. The body of the incoming email is added to the history of the specified call.

  2. Update Closed Calls via email must be enabled in the Incoming email server settings or closed calls will not be updated.

  3. If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the call.

  4. If there are any attachments to the email, they are attached to the call as objects and can be accessed from the Object Explorer option on the Call Details window.

  5. Finally, a note icon is added to the specified call in the Calls Outstanding window to indicate to the handling analyst that the call has been updated.

When ASM Core has updated the call, a return email message is sent with the subject “Call <Call Number> has been updated”, where <Call Number> is the reference number of the call, if auto-reply has been enabled for that incoming email server in Email Settings.

What happens if the Call is Closed?

If the incoming email matches a recognized subject heading for updating a call, but the call is closed:

  1. If Update Closed Calls is selected on the incoming email server, the call remains closed but a note is added to the call with the details of the email. The sender of the email also receives the following message: “Call No xyz has been updated by ASM Core.

  2. If Update Closed Calls is not selected, the call remains closed and the following message is sent back to the sender of the email: “Call No xyz is already closed and has not been updated.”

What Happens if the Call Number or Email address is not recognized?

  1. A New Call is Logged - If ASM Core receives an incoming email with a subject heading used to update a call, but it does not recognize the call number specified in the subject line, it logs a new call if the incoming email account has the Log New Call on Invalid Number option.

  2. The Email is Ignored - If Log New Call on Invalid Number is not selected, ASM Core ignores the email and the person who sent the incoming email is not notified.

  3. Invalid or Unknown Email - If ASM Core receives an incoming email with a subject heading used to update a call, but it does not recognize the sender's email address, it ignores the email.

    • However, if the Update Calls Anonymously option is selected for the incoming email account, the call is updated.

Ensure updates made via email notify the Assigned Analyst

To have email notifications sent to the assigned analyst or group when a call is updated by incoming email, ensure that the Email at Update via Email In option is selected under IPK Management on the Messaging administration window.

Viewing a Call Summary with Email

A support analyst can check a summary of their calls by sending an email to a ASM Core incoming email account with the following subject:

[MyCalls]
Closing a Call with Email
  1. Rules

    • What happens if the email comes from an Unrecognized Email Address? If the Close Calls Anonymously option is not selected in the incoming email account, a call cannot be closed by an email sent from an unrecognized address (that is, an email address that does not correspond to a ASM Core analyst or User).

    • If the sender is flagged as a User only, the call will only be closed if the same User is specified in the User field of the call.

    • If the sender is a ASM Core analyst, the call will be closed if they own the call or have Take Over rights as part of their IPK Management security role. Otherwise, a return email with the following message will be sent: “Reason: Insufficient Permission”.

  1. To close a call through Email

  1. Send an email to a ASM Core incoming email account with the subject: [CLOSE#xyz] , where xyz represents the call number of the call you want to close. The square brackets are required and It must be a valid open call number.

  2. The call you specified will be closed and a return email will be sent to you to confirm the closure.

Reopening a Closed Call with Email

You must also have reopen closed calls enabled on the Analysts security role and the User security role.

The Self Service Portal must also have Reopen Closed Calls enabled in the Self Service Portal Administrative settings.

If you send an email with all the following conditions met, ASM will reopen the call in ASM Core and add the details of the email as a note to the call (the analyst or group assigned to the call depends on the settings chosen in the Email Settings):

  1. The call number is in the subject line

  2. The Subject is in a recognized format

  3. The specified call is closed

  4. And the Reopen Closed Calls option is selected on the incoming email server

Approving Tasks with Email

To approve an Approval Task through an email, you can:

  1. Send an email to the ASM Core incoming email account with the following subject:

[APPROVE#xyz]

xyz represents the number of the Approval Task you want to approve.

The square brackets are required. For example: [APPROVE#5837]

This includes standard Approval Tasks as well as User Approval Tasks.

  1. Click the Green Approve Button on the email message.

    • When you click the Approve button, a new email will be launched, correctly formatted.

    • Enter your comments, if there are any, and send.

    • Do not change the Subject line

If a task has been successfully approved through incoming email, a return email with the subject “Task <Task Number> has been successfully approved” is sent (where <Task Number> is the reference number of the Approval Task).

The workflow in that request will then proceed as designed based on the approval or rejection of the approval task.

What if the email address in not recognized? If the email address is not recognized, the Approval Task is not approved and a return email is sent, stating that the sender has not been identified.

What if the Email address comes from an analyst or user who is not authorized to do Approvals? If the sender lacks approval rights as part of their Workflow Management security role or does not have Take Over Approvals, a return email with the following message will be sent: “Reason: Insufficient Permission”.

Rejecting an Approval Task with Email

To reject an Approval Task through an email, you can:

  1. Send an email to the ASM Core incoming email account with the following subject:

[REJECT#xyz]

xyz represents the number of the Approval Task you want to reject.

The square brackets are required. For example: [REJECT#5837]

This includes standard Approval Tasks as well as User Approval Tasks.

  1. Click the Red Reject Button on the email message.

    • When you click the Reject button, a new email will be launched, correctly formatted.

    • Enter your comments, if there are any, and send.

    • Do not change the Subject line

If an Approval task has been successfully rejected through incoming email, a return email with the subject “Task <Approval Task Number> has been successfully rejected” is sent.

What if the email address in not recognized? If the email address is not recognized, the Approval Task is not rejected and a return email is sent, stating that the sender has not been identified.

What if the Email address comes from an analyst or user who is not authorized to do Approvals? If the sender lacks approval rights as part of their Workflow Management security role or does not have Take Over Approvals, a return email with the following message will be sent: “Reason: Insufficient Permission”.

Update Tasks with Email
  1. The body of the incoming email is added to the history of the specified task or approval.

  2. If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the task or approval.

  3. If there are any attachments to the email, they are attached to the task or approval as objects and can be accessed from the Object Explorer option on the Task or Approval Details window.

  4. Finally, a note icon is added to the specified task or approval in the Tasks Outstanding window to indicate to the handling analyst that the task has been updated.

  5. When ASM Core has updated the task or approval, a return email message is sent with the subject “Task/Approval <Task/Approval Number> has been updated”, where <Task/Approval Number> is the reference number of the task or approval.

Updating a Request with Email
  1. The body of the incoming email is added to the history of the specified request.

  2. If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the request.

  3. If there are any attachments to the email, they are attached to the request as objects and can be accessed from the Object Explorer option on the Request Details window.

  4. Finally, a note icon is added to the specified request in the Requests Outstanding window to indicate to the handling analyst that the request has been updated.

  5. When ASM Core has updated the request, a return email message is sent with the subject “Request <Request Number> has been updated”, where <Request Number> is the reference number of the request.

If ASM receives an incoming email with a subject heading used to update a request, but it does not recognize the request number specified in the subject line, it will log a new call.

Viewing a Request Summary with Email

A support analyst can check a summary of their requests by sending an email to a ASM Core incoming email account with the following subject:

[MyRequests]

A return email is sent to that support analyst with a summary of all the requests they are working on, have forwarded, or have been forwarded.

Viewing a Task and Approval Summary with Email

A support analyst can check a summary of their tasks and approvals by sending an email to a ASM Core incoming email account with the following subject:

[MyTasks]

[MyApprovals]

A return email is sent to that support analyst with a summary of all the tasks and approvals they are working on, have forwarded, or have been forwarded.

To update an existing call by email, send an email to a ASM Core incoming email account with a and the call number.

To update an existing task by email, send an email with one of the .

A request can be updated by incoming email. To update an existing request by email, send an email with one of the lines.

Recognized Incoming Subject Headings
Email Settings
recognized subject heading
recognized subject lines
recognized subject