Skip to content

SMLets Exchange Connector v5.0 RC1

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 01 Dec 16:28
· 11 commits to dev since this release
v5.0-rc.1
09eb86b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

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
Assets 3