SMLets Exchange Connector v5.0.4

SMLets Exchange Connector v5.0.4

General
The Management Pack (5.0.4.5) introduces support for plus addressing in multi-mailbox configuration.

• Diff from v5.0.3

Enhancements

• Multi-Mailbox supports the use of "+" within email addresses
• Introduce more logging events and error handling when using KA/RO suggestion features

Bugs

• If suggest KA/RO is enabled and inline images (e.g. signature graphics) have an Alt Text property defined. The connector will fail to suggest relevant KA/ROs

Miscellaneous

• When reactivating an Incident/Problem the Resolved By User relationship should be cleared

SMLets Exchange Connector v5.0.3

SMLets Exchange Connector v5.0.3

General
The changes in this release are PowerShell in nature alone addressing bugs and an enhancement when using Merge Replies.

• Diff from v5.0.2

Enhancements

• When using Merge Replies, mail clients may use the currently signed in user's locale to determine the Subject Reply Prefix instead of using RE:. This extends functionality to twelve additional language patterns (AW, SV, Antw, REF, RIF, SV, BLS, Atb., RES, Odp, YNT, ATB) so as to continue to merge threaded replies into a single Work Item

Bugs

• Fixes an issue when creating new Work Items based on Templates that contain nested Activities (e.g. a Service Request Template that contains a Sequential/Parallel Activity that contains other Activities)
• Fixes an issue when leaving a comment that is greater than 4,000 characters
• Fixes an issue wherein Custom Events requires verbose logging to properly load

SMLets Exchange Connector v5.0.2

SMLets Exchange Connector v5.0.2

General
Contains single bug fix for those utilizing Templates that contain one or many Activities

• Diff from v5.0.1

Bugs

• Fixes an issue when the Template used for the connector features one or many Activities

SMLets Exchange Connector v5.0.1

SMLets Exchange Connector v5.0.1

General
The changes in this release are PowerShell in nature alone with a single bug fix and total adherence to PSScriptAnalyzer with no changes to the Management Pack.

• Diff from v5.0

Bugs

• Fixes an issue with "Create Work Item when Closed" when multiple emails with the same Conversation ID are found across multiple Work Items

Enhancements

• Logging on Review Activities when a user attempts to vote on a Review Activity that they are not a Reviewer on
• Logging on Review Activities when voting on behalf of AD group
• Logging if [take] fails

Miscellaneous

• The SMLets Exchange Connector comprehensively follows PowerShell best practice as defined by PSScriptAnalyzer
• Standardize all functions throughout the connector:
  • Properly formatted param blocks
  • Inline notes for every function and their parameters usage
  • Functions whose verbs change system state should support "ShouldProcess". As such, several functions throughout the connector now support PowerShell's "-WhatIf" parameter
• Indented a block of code (i.e. Review Activity section) within Update-WorkItem for improved readability
• Added comments to explain a section of Exchange code that is responsible for initial filtering of the Inbox

SMLets Exchange Connector v5.0

SMLets Exchange Connector v5.0

General
The Management Pack (5.0.0.29) introduces support for configuring multiple keywords per keyword configuration. This gives rise to new process and automation scenarios based on keyword usage.

• Diff from v4.1.1

New Features
The Management Pack (5.0.0.29) and the Parsing Keywords configuration pane within the Settings UI can now support one or many comma separated keywords. For example:

• the [acknowledge] keyword could now be set to "acknowledge,ack,affirmative"
• the [watch] keyword could now be set to "watch,oversee"
• the [reactivate] keyword could now be set to "reactivate,reopen,open"
• the [take] keyword could now be set to "take,took,mine"
• the [scom] keyword could now be "health,check,alerts"

In doing so:

• Enables multiple languages per keyword
• Gives rise to keywords only known to select individuals or made available on Notification Templates. Thus introducing new automation opportunities based on specific uses of the keyword. For example:
  • the [approved] keywords could be set to "approved,expedite" to extend current functionality with Custom Events and Invoke-AfterApproved. So that when [expedite] is used, not only is the Review Activity vote counted as Approved, but the Priority of a subsequent Activity would be raised to Immediate.

Bugs

• Update-WorkItem was only adding the email as an attachment as opposed to individual attachments on the email
• Get-SCSMUserByEmailAddress would break if the user's email address featured PowerShell comparison operators e.g. -Le, -Ge, -And, etc.
• Connecting to Exchange Online and supplying credentials to the connector by ANY OTHER means that using the SCSM Workflow engine would always fail to connect

Miscellaneous

• Continued adherence to best practices as defined by PSScriptAnalyzer. The following two changes are potentially breaking if you have modified the connector or are using functions contained within the connector for your Custom Events.
  • Two unused variables have been commented out. They are:

  #$userClass = get-scsmclass -name "System.User$"
  #$sysUserHasPrefRelClass = Get-SCSMRelationshipClass -name "System.UserHasPreference$"

  • Function names should use singular nouns instead of plural nouns

    Old Name	Updated Name
    Get-TierMembers	Get-TierMember
    Get-CiresonPortalAnnouncements	Get-CiresonPortalAnnouncement
    Search-AvailableCiresonPortalOfferings	Search-AvailableCiresonPortalOffering
    Get-AzureEmailKeywords	Get-AzureEmailKeyword
    Get-SCSMWorkItemSettings	Get-SCSMWorkItemSetting

• Several functions have been refactored for performance and improve how they pass parameters between themselves
  • Get-TierMembership (used when verifying who is allowed to use [take])
  • Set-SCSMTemplate and Update-SCSMPropertyCollection (used when setting a Template on a New Work Item)
  • Get-SCOMDistributedAppHealth (used when retrieving a SCOM Distributed Application's health)
• The selected AD Group to retrieve SCOM Distributed Application Health and/or an AD Group to make SCSM Announcements no longer uses a Label to show its Display Name
• Iconography has been updated for the Templates and Logging configuration panes in the management pack
• Logging is more representative of start, process, and finish stages of the connector
• More logging is provided around retrieving OAuth tokens when using 365
• The DisplayName property for Incidents, Service Requests, Problems, and Change Requests are now set as though the Work Item was created in the SCSM console

SMLets Exchange Connector v5.0 RC1

SMLets Exchange Connector v5.0-RC1

Summary
Release Candidate 1 for v5.0 of the connector that introduces support for multiple keywords for a single keyword action.

General
Barring significant issues as it pertains to using any given number of configured keywords for a specific action, this version is the most representative in terms of functionality to the final v5 release.

• Diff from v4.1.1

New Features
The Management Pack (5.0.0.3) introduces support for entering one or many comma separated keywords per keyword configuration. For example, the [approved] keyword could now be set to "yes,affirmative,approved,approve,expedite". The [reactivate] keyword could now be set to "reactivate,reopen", etc. In doing so:

• Enables multiple languages per keyword
• Gives rise to keywords only known to select individuals or made available on Notification Templates. Thus introducing new automation opportunities based on specific uses of the keyword. For example, [approved] may complete a Review Activity but using Custom Events and Invoke-AfterApproved. If the keyword used was [expedite], the Review Activity would be completed and the Priority of a subsequent Activity would be raised to Immediate.

Bugs

• When updating a Work Item, individual attachments from an email are not added but the email that contains all of the attachments is added
• When an email address contains a PowerShell comparison operation such as -Le, -Ge, -And, etc. Then the Get-SCSMUserByEmailAddress function fails to correctly identify the user
• Retrieving a user's email address for SCOM actions uses the wrong property
• In some environments SMLets isn't imported correctly when the PowerShell starts so that section has been moved further up in the connector's execution

Miscellaneous
Several functions have been renamed to use singular nouns instead of plural to follow PowerShell best practices. As such, if you are using any of these in your own Custom Events they will need to be updated.

Old Name	Updated Name
Get-TierMembers	Get-TierMember
Get-CiresonPortalAnnouncements	Get-CiresonPortalAnnouncement
Search-AvailableCiresonPortalOfferings	Search-AvailableCiresonPortalOffering
Get-AzureEmailKeywords	Get-AzureEmailKeyword
Get-SCSMWorkItemSettings	Get-SCSMWorkItemSetting

CHANGES FROM ALPHA1, ALPHA2, & BETA1

• Two unused variables have been commented out. They are:
  • #$userClass = get-scsmclass -name "System.User$"
    #$sysUserHasPrefRelClass = Get-SCSMRelationshipClass -name "System.UserHasPreference$"
• Several functions have been refactored for performance and improve how they pass parameters between themselves
  • Get-TierMembership (used when verifying who is allowed to use [take])
  • Set-SCSMTemplate and Update-SCSMPropertyCollection (used when setting a Template on a New Work Item)
  • Get-SCOMDistributedAppHealth (used when retrieving a SCOM Distributed Application's health)
• The selected AD Group to retrieve SCOM Distributed Application Health and/or an AD Group to make SCSM Announcements no longer uses a Label to show its Display Name
• Iconography has been updated for the Templates and Logging configuration panes in the management pack
• Logging is more representative of start, process, and finish stages of the connector
• More logging is provided around retrieving OAuth tokens when using 365
• The DisplayName property for Incidents, Service Requests, Problems, and Change Requests are now set as though the Work Item was created in the SCSM console

SMLets Exchange Connector v5.0-Beta1

SMLets Exchange Connector v5.0-Beta1

Summary
First beta release for v5.0 of the connector that introduces support for multiple keywords.

New Features
The Management Pack (5.0.0.2) introduces support for entering one or many comma separated keywords per keyword configuration. For example, the [approved] keyword could now be set to "yes,affirmative,approved,approve,expedite". The [reactivate] keyword could now be set to "reactivate,reopen", etc. In doing so:

• Enables multiple languages per keyword
• Gives rise to keywords only known to select individuals or made available on Notification Templates. Thus introducing new automation opportunities based on specific uses of the keyword. For example, [approved] may complete a Review Activity but using Custom Events and Invoke-AfterApproved. If the keyword used was [expedite], the Review Activity would be completed and the Priority of a subsequent Activity would be raised to Immediate.

Bugs

• When updating a Work Item, individual attachments from an email are not added but the email that contains all of the attachments is added
• When an email address contains a PowerShell comparison operation such as -Le, -Ge, -And, etc. Then the Get-SCSMUserByEmailAddress function fails to correctly identify the user

Miscellaneous
Several functions have been renamed to use singular nouns instead of plural to follow PowerShell best practices. As such, if you are using any of these in your own Custom Events they will need to be updated.

Old Name	Updated Name
Get-TierMembers	Get-TierMember
Get-CiresonPortalAnnouncements	Get-CiresonPortalAnnouncement
Search-AvailableCiresonPortalOfferings	Search-AvailableCiresonPortalOffering
Get-AzureEmailKeywords	Get-AzureEmailKeyword
Get-SCSMWorkItemSettings	Get-SCSMWorkItemSetting

CHANGES FROM ALPHA1 & ALPHA2

• Two unused variables have been commented out. They are:
  • #$userClass = get-scsmclass -name "System.User$"
    #$sysUserHasPrefRelClass = Get-SCSMRelationshipClass -name "System.UserHasPreference$"
• Several functions have been refactored for performance and improve how they pass parameters between themselves
  • Get-TierMembership (used when verifying who is allowed to use [take])
  • Set-SCSMTemplate and Update-SCSMPropertyCollection (used when setting a Template on a New Work Item)
  • Get-SCOMDistributedAppHealth (used when retrieving a SCOM Distributed Application's health)
• The selected AD Group to retrieve SCOM Distributed Application Health and/or an AD Group to make SCSM Announcements no longer uses a Label to show its Display Name
• Iconography has been updated for the Templates and Logging configuration panes in the management pack
• In some environments SMLets isn't imported correctly when the PowerShell starts so that section has been moved further up in the connector's execution.
• Logging is more representative of start, process, and finish stages of the connector

SMLets Exchange Connector v5.0-Alpha2

SMLets Exchange Connector v5.0-Alpha2

Summary
Second alpha release for v5.0 of the connector that introduces support for multiple keywords.

New Features
The Management Pack (5.0.0.1) introduces support for entering one or many comma separated keywords per keyword configuration. For example, the [approved] keyword could now be set to "yes,affirmative,approved,approve,expedite". The [reactivate] keyword could now be set to "reactivate,reopen", etc. In doing so:

• Enables multiple languages per keyword
• Gives rise to keywords only known to select individuals and thus introduces new automation opportunities based on specific uses of the keyword. For example, [approved] may complete a Review Activity but using Custom Events and Invoke-AfterApproved. If the keyword used was [expedite], the Review Activity would be completed and the Priority of a subsequent Activity would be raised to Immediate.

Bugs

• When updating a Work Item, individual attachments from an email are not added but the email that contains all of the attachments is added
• When an email address contains a PowerShell comparison operation such as -Le, -Ge, -And, etc. Then the Get-SCSMUserByEmailAddress function fails to correctly identify the user

Miscellaneous
Several functions have been renamed to use singular nouns instead of plural to follow PowerShell best practices. As such, if you are using any of these in your own Custom Events they will need to be updated.

Old Name	Updated Name
Get-TierMembers	Get-TierMember
Get-CiresonPortalAnnouncements	Get-CiresonPortalAnnouncement
Search-AvailableCiresonPortalOfferings	Search-AvailableCiresonPortalOffering
Get-AzureEmailKeywords	Get-AzureEmailKeyword
Get-SCSMWorkItemSettings	Get-SCSMWorkItemSetting

CHANGES FROM ALPHA1

• Two unused variables have been commented out. They are:
  • #$userClass = get-scsmclass -name "System.User$"
    #$sysUserHasPrefRelClass = Get-SCSMRelationshipClass -name "System.UserHasPreference$"
• Several functions have been refactored for performance and improve how they pass parameters between themselves
  • Get-TierMembership (used when verifying who is allowed to use [take])
  • Set-SCSMTemplate and Update-SCSMPropertyCollection (used when setting a Template on a New Work Item)
  • Get-SCOMDistributedAppHealth (used when retrieving a SCOM Distributed Application's health)
• The selected AD Group to retrieve SCOM Distributed Application Health and/or an AD Group to make SCSM Announcements no longer uses a Label to show its Display Name

SMLets Exchange Connector v5.0-Alpha1

SMLets Exchange Connector v5.0-Alpha1

Summary
First alpha release for v5.0 of the connector that introduces support for multiple keywords.

New Features
The Management Pack (5.0.0.0) introduces support for entering one or many comma separated keywords per keyword configuration. For example, the [approved] keyword could now be set to "yes,affirmative,approved,approve,expedite". The [reactivate] keyword could now be set to "reactivate,reopen", etc. In doing so:

• Enables multiple languages per keyword
• Gives rise to keywords only known to select individuals and thus introduces new automation opportunities based on specific uses of the keyword. For example, [approved] may complete a Review Activity but using Custom Events and [expedite] could complete a Review Activity and raise the Priority of a subsequent Manual Activity to Immediate.

Miscellaneous
Several functions have been renamed to use singular nouns instead of plural to follow PowerShell best practices. As such, if you are using any of these in your own Custom Events they will need to be updated.

Old Name	Updated Name
Get-TierMembers	Get-TierMember
Get-CiresonPortalAnnouncements	Get-CiresonPortalAnnouncement
Search-AvailableCiresonPortalOfferings	Search-AvailableCiresonPortalOffering
Get-AzureEmailKeywords	Get-AzureEmailKeyword
Get-SCSMWorkItemSettings	Get-SCSMWorkItemSetting

SMLets Exchange Connector v4.1.1

SMLets Exchange Connector v4.1.1

General
The changes in this release are PowerShell in nature (bug fixes and continued adherence to best practices as defined by PSScriptAnalyzer) with no changes to the Management Pack.

• Diff from v4.1

Bugs

• Azure Cloud Instance picker returned a string instead of an enum
• The Assigned User of a Closed Incident cannot reactivate it which would result in a New and Related Incident

Enhancements

• All catch statements now contain relevant logging events

Miscellaneous

• The Get-CiresonPortalAPIToken function no longer makes use of ConvertTo-SecureString
• Removed all trailing whitespace