Connect OutSystems apps to the Amazon Transcribe service to add speech-to-text capabilities to any application. Amazon Transcribe allows you to ingest audio input, produce easy-to-read transcripts, improve accuracy with language customization, and filter content to ensure customer privacy. You will be able, for example, to transcribe and analyze customer-agent calls and also create closed captions for videos.
The connector uses the AWS SDK (check the documentation on how to set up the connector). Once connected, you can easily take advantage of Amazon Transcribe’s capabilities. The following picture shows the Amazon Transcribe connector in Service Studio:
By downloading this component you acknowledge and agree to the collection of usage data (which may include, but is not limited to, method name, size of the files, operation type or region) by OutSystems and Amazon Web Services. Usage data does not include personal data. If you do not agree with such collection, please do not download this component.
In this version:
19 new static entities to manage static data sent and returned from the service. Bellow is the list with the name of static entities created:
TranscribeParticipantRole
TranscribeTranscriptFilterType
TranscribeSentiment
TranscribeBaseModelName
TranscribeLanguage
TranscribeModelStatus
TranscribeVocabularyState
TranscribeJobStatus
TranscribeMediaFormat
TranscribeVocabularyFilterMethod
TranscribePiiEntityType
TranscribeRedactionOutput
TranscribeRedactionType
TranscribeIdentificationType
TranscribeSpecialty
TranscribeJobType
TranscribeSubtitleFormat
TranscribeOutputLocationType
TranscribeResourceType
A new BuildTagARN action to help on Tagging Resources methods which needs the ARN from a resource to manage tags.
Validation was added to all public methods inside the connector, instead of transparently sending everything to the AWS service.
There is a new TranscribeRequestValidation exception to manage the validation output
this validation acts on:
mandatory fields
integer ranges
string lengths
<breaking change> Updated all structures to use the created static entities identifier, instead of returning a text value. Below is the list with the name of updated structures:
CreateLanguageModel_Request
CreateLanguageModel_Response
ListLanguageModels_Request
MedicalTranscriptionJobSummaryItem
Response_ListMedicalTranscriptionJobs
Request_StartMedicalTranscriptionJob
Request_ListMedicalVocabularies
Response_ListMedicalVocabularies
Request_CreateMedicalVocabulary
Response_CreateMedicalVocabulary
Response_GetMedicalVocabulary
Request_UpdateMedicalVocabulary
Response_UpdateMedicalVocabulary
CallAnalyticsJob
CallAnalyticsJobSettings
CallAnalyticsJobSummary
ChannelDefinition
ContentRedaction
InterruptionFilter
LanguageModel
MedicalTranscriptionJob
RedactionOutput
RedactionType
SentimentFilter
Setting
Subtitle
SubtitleOutput
TranscriptFilter
TranscriptionJob
TranscriptionJobSummaryItem
VocabularyFilterItem
VocabularyItem
Request_ListTranscriptionJobs
Response_ListTranscriptionJobs
Request_StartTranscriptionJob
Request_ListVocabularies
Response_ListVocabularies
Request_CreateVocabulary
Response_CreateVocabulary
Request_CreateVocabularyFilter
Response_CreateVocabularyFilter
Response_GetVocabularyFilter
Response_UpdateVocabularyFilter
Response_GetVocabulary
Request_UpdateVocabulary
Response_UpdateVocabulary
<breaking change> Created the following structures to use the static entity identifier as value:
Key_BaseModelName
Key_JobStatus
Key_JobType
Key_Language
Key_MediaFormat
Key_ModelStatus
Key_OutputLocation
Key_ParticipantRole
Key_Specialty
Key_TranscriptFilterType
Key_VocabularyFilterMethod
Key_VocabularyState
<breaking change> The Key structure was removed due to no longer being used.