Releases: AdhocAdam/smletsexchangeconnector
Releases · AdhocAdam/smletsexchangeconnector
SMLets Exchange Connector v2.0-Alpha2
SMLets Exchange Connector v2.0-Alpha2
Summary
Second alpha release of the connector that is based off of v1.5 that shifts configuration from the script to a central Management Pack.
New Features
- Introduction of a Settings based Management Pack to persist values between upgrades
WARNING
At this time I believe that four variables/settings remain that all revolve around AI functionality through ACS or AML. However I'm still checking and again advise against use of this in a production environment. The variables in question are as follows:
- $acsSentimentScoreClassExtensionName
- $amlWITypeScoreClassExtensionName
- $amlWIClassificationScoreClassExtensionName
- $amlWISupportGroupClassExtensionName
GENERAL FIXES
- Per issue and pull in #131 and #132, the verbiage in the tooltip has been updated accordingly
- The keywords pane is more verbose in how keywords should be set and how they are referenced
- The Additional Mailbox class now uses the Exchange Mailbox Icon
FIXED ISSUES FROM ALPHA1
- Settings MP: Some WPF controls appear cut off
- Settings MP: The title of the Settings window reads "beta 3"
- Settings MP: The Private keyword can't be defined
- PowerShell: SCOM AD Group doesn't pull from the MP
KNOWN ISSUES
- Settings MP: Decimal values on text boxes requires some finesse in that if you want to enter 25.4, you must type 254, and then place the decimal
- Settings MP: ACS Priority Scoring feature still requires editing of Get-ACSWorkItemPriority
- Settings MP: Some fields lack validation for text patterns (comma separated, ends with "/", prevent special characters)
- Settings MP: To enable ACS keywords for Cireson RO/KA you need to turn the Cireson feature on, save, re-open and then check off ACS features.
- Settings MP: Multiple mailboxes can only be deleted one at a time e.g. remove, save, open, remove, save, and so on and so on.
- Settings MP: Problem Support Group can't be set. This is intentional and will remain until Cireson releases their own support for the feature
- Settings MP: Primary Work Item Template and Multi-Mailbox Template require all Templates to be defined to pass validation
SMLets Exchange Connector v2.0-Alpha1
SMLets Exchange Connector v2.0-Alpha1
Summary
First alpha release of the connector that is based off of v1.5 that shifts configuration from the script to a central Management Pack.
New Features
- Introduction of a Settings based Management Pack to persist values between upgrades
WARNING
While a majority of settings have made the transition, I have yet to fully account for every single one. I strongly advise against use of this release in a production environment but as always welcome feedback for those willing to test.
KNOWN ISSUES
- Settings MP: Decimal values on text boxes requires some finesse in that if you want to enter 25.4, you must type 254, and then place the decimal
- Settings MP: ACS Priority Scoring feature still requires editing of Get-ACSWorkItemPriority
- Settings MP: Some fields lack validation for text patterns (comma separated, ends with "/", prevent special characters)
- Settings MP: To enable ACS keywords for Cireson RO/KA you need to turn the Cireson feature on, save, re-open and then check off ACS features.
- Settings MP: Multiple mailboxes can only be deleted one at a time e.g. remove, save, open, remove, save, and so on and so on.
- Settings MP: The Private keyword can't be defined
- Settings MP: The title of the Settings window reads "beta 3"
- Settings MP: Problem Support Group can't be set. This is intentional and will remain until Cireson releases their own support for the feature
- Settings MP: Some WPF controls appear cut off
- Settings MP: Primary Work Item Template and Multi-Mailbox Template require all Templates to be defined to pass validation
- PowerShell: SCOM AD Group doesn't pull from the MP
SMLets Exchange Connector v1.5
SMLets Exchange Connector v1.5
New Features
- Support for Custom Work Item Prefixes as configured through the SCSM console
- Ability to write Azure Artificial Intelligence scores directly into New Incident or Service Requests through org defined decimal based class extensions
- Ability to Assign New Work Items out to Analysts defined in the Template's Support Group through either entirely random, least assigned volume, or in conjunction with the Out of Office management pack
- Azure Machine Learning integration so as to train the connector (Azure) how to determine Work Item Type (Incident or Service Request), Classification, and Support Group unique to every organization that deploys it
Enhancements
- Control visibility and type of Comments left by third parties (i.e. Related Users) in the configuration of the connector as opposed to modifying within the core functions
Bugs
- If using the feature that creates New Work Items if the one the user is replying to is Closed. It's possible the connector can get stuck in an infinite loop
- If the Template being used to create brand New Work Items was an Incident that featured Activities, those Activities did not have a prefix (i.e. Manual and Runbook Activities)
- If using the feature to change Incident Status based on who replied was enabled, users could move Incidents out of Closed status
- Attaching Files (not the email) sometimes fails on New Work Items
SMLets Exchange Connector v1.4.7-Alpha1
SMLets Exchange Connector v1.4.7-Alpha1
Summary
First alpha release of the connector that is based off of v1.4.6 with the single change of introducing support for Custom Work Item Prefixes
New Features
- Support for Custom Work Item Prefixes
WARNING
This particular release/feature is still undergoing testing to ensure stability across all of the SMLets Exchange Connector feature sets as the nature of this change is the crux for how New Work Items are Created and Updated in Service Manager. As such, we strongly advise against deploying this to a production Service Manager environment without first thoroughly testing in a development capacity. It is for this reason this has been tagged as alpha/pre-release.
KNOWN BUGS
- Alpha1 exposed issue with Incidents that feature Activities. Addressed in Pull #119 for next release.
Raising Issues
If you are available for testing, raising Github Issues on the repo as always are welcome and will be logged against the March 2019 release.
SMLets Exchange Connector v1.4.6
SMLets Exchange Connector v1.4.6
General
Decided to remove screenshots, docs folder, and other GitHub specific folders from the Release *.zip seen below as they aren't all that intuitive and/or relevant to view locally once downloaded. Going to try to stick to this process going forward. This doesn't impact the actual SMLets Exchange Connector blog, it just no longer is included in the release download
New Features
- Leverage a list of configurable words instead of relying on Azure Cognitive Services sentiment analysis to trigger the creation of an Incident or Service Request as the default New Work Item
- Change the Status of an Incident based on who replied. As such, this can be configured so the Affected User sets it to Active, but the Assigned To flips it to Pending. This helps better reflect an Incident's time in a respective status thereby enhancing data warehouse reporting metrics
Enhancements/Optimizations
- Converted all uses of Invoke-WebRequest to Invoke-RestMethod when interacting with the Cireson SCSM Portal
- Any cases where a user needed to be retrieved via their email address have been updated to leverage a function created several versions ago (i.e Get-SCSMUserByEmailAddress)
- The custom functions of Get-SCSMAttachmentSettings and Get-SCSMObjectPrefix were arguably two sides of the same coin. These have been combined to form the new Get-SCSMWorkItemSettings which retrieves things like prefixes, attachment limits, and most importantly provides the ability for growth should future functionality demand it
- Moved the New Work Item Suggestion functionality into it's own dedicated function. This removes half of that specific code as it was simply duplicated in previous versions across IR and SR
- Multiple mailbox routing supports parsing BCC via the email's original header
Bugs
- Unlike the CreatedDate property which is defined on the fly through SCSM, dates related to Keyword actions (Resolved, Closed, Completed) were not being set simply by invoking their respective Status change.
- Depending on the version of SMLets that was being used and where it was being used from (remote or local) Get-SCSMClassProperty produces varying results. This smlet was dropped in favor of a more native SDK style call in order to retrieve class extensions for MA and CR classes
SMLets Exchange Connector v1.4.5
SMLets Exchange Connector v1.4.5
New Features
- Continuing on the use of Azure Cognitive Services, you can now optionally use the returned Sentiment Analysis score (perceived user attitude) to change the Priority (e.g. the enums responsible for the final calculation) on new Incidents or Service Requests. These ranges are editable through the new Get-ACSWorkItemPriority function.
- You can now control the email styling (HTML/CSS) on emails that go out for Suggested Knowledge Articles and/or Request Offering via the new HTML templates. These templates will be preserved throughout future upgrades of the connector.
- You can't control what the Affected User will type in an email, but now with a custom regex file you can control what actually makes its way into SCSM, the SCSM DW, or Cireson's databases as regex patterns you specify will now replace Work Item Descriptions and Comments with [redacted].
Enhancements/Optimizations
- Suggested Knowledge Articles and/or Request Offering emails will now sort based on the most matched words as opposed to the rather random previous nature
SMLets Exchange Connector v1.4.4
SMLets Exchange Connector v1.4.4
New Features
- Added the ability to set First Response Date on IR/SR when suggested Request Offerings or Knowledge Articles are made to the Affected User. #48
- Introduce [take] keyword on Manual Activities and Change Request with optional [take] Support Group enforcement #56 and #59
- The #private keyword is now configurable #63
- The [resolved] keyword should trigger a Record Resolved and add the Comment as a Resolution Description instead of just leaving an Analyst Comment. This was extend to support similar functionality on Service Requests and Problems. #60
- The [reactivated] keyword should trigger a Record Reopened on the Action Log instead of leaving an Analyst Comment. #61
Bug Fixes
- Cancelling a meeting request missing the [Work Item] in the subject should null the values of Scheduled Start and End Times instead of creating a brand new work item. Performed by introducing new logic on Verify-WorkItem. #51
- When the Assigned To User and the Affected User are the same person, the connector leaves an End User and Analyst Comment on the Action Log. This has been updated to match the OOB Exchange Connector functionality whereby the comment is marked as a Public End User Comment. #58
- Suggesting Request Offerings from the Cireson Portal returns no results #67
- When the [skip] keyword is used, the Cireson Portal doesn't correctly render the MA as skipped #64
Enhancements/Optimizations