Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More reporting flexibility for AML #128

Merged
merged 3 commits into from Jul 2, 2019
Merged

More reporting flexibility for AML #128

merged 3 commits into from Jul 2, 2019

Conversation

AdhocAdam
Copy link
Owner

Further breaking out AML returned values to support custom org processes and reporting

Further breaking out AML returned values to support custom org processes and reporting
Accidentally tab the version number in
@AdhocAdam AdhocAdam added this to the v1.5.1 milestone May 18, 2019
Further breaking out extension support for AML
@AdhocAdam AdhocAdam merged commit 3d087d9 into dev Jul 2, 2019
AdhocAdam added a commit that referenced this pull request Sep 29, 2019
* Include Whole Email notes (#133)

Per @moverton28, the notes on how to use the $includeWholeEmail variable are incorrect which leads to confusion on this particular setting's use.

* Fixing Type Projection issue (#137)

This is to address #130

* More reporting flexibility for AML (#128)

* More reporting flexibility for AML

Further breaking out AML returned values to support custom org processes and reporting

* Removing a tab

Accidentally tab the version number in

* More extensions

Further breaking out extension support for AML

* Azure Translation integration (#143)

* Azure Translate #3

Incorrect diff again.

* Azure Translate graphic

Uploading to update readme around the feature

* placeholder for translate

Creating entry on readme for translation feature

* Update README.md

* Dynamic Analyst Assignment fix (#139)

* Dynamic Analyst Assignment fix

Incorrect variable is used

* Removing property

Property doesn't exist as incoming value is a string/guid not an object

* Modifying Set-AssignedToPerSupportGroup design

Investigating the Set-AssignedToPerSupportGroup functions reveals a flaw within how the switch was leveraged.

* Updating select

When using volume based criteria, the selection needs to be expanded to discard the count property.

* Updating variable (#148)

Original calls were heavily based on prior example calls.

* Sanitizing language input (#149)

* Sanitizing languages

If a language is used with certain types of characters, it's possible that the translate functions break when they encounter the character.

* update API call

Update the Azure Translate API calls with UTF-8

* Updating notes

Adding change log notes
@AdhocAdam AdhocAdam deleted the AdhocAdam-AMLReporting branch September 29, 2019 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant