Using Mft Component
Add component tag of the component you want to use to your .html page. The inputs are bind using attribute binding. You can find all the inputs of each component in below sections. Below is a sample of the mft component in a html page.
CODE<mft-send-to #mft [attr.auth-service-url]="http://authservice/" [attr.auth-redirect-url]="http://mp/" [attr.auth-service-client-id]="implicit" [attr.header-text]="MFT Dialog" [attr.auth-service-scope]="openid profile api1" [attr.auth-logout-url]="http://mp/" [attr.auth-silent-refresh-url]="http://mp/refresh" [attr.mft-send-to-url]="http://mftproxy" [attr.item-id]="VX-1" (mftWorkflowTriggered)="handleWorkflowTriggeredEvent($event.detail)" > </mft-send-to>
“workflowObjects“ input is needed for MFT component but because this input is a complex object, the input need to be pass in from javascript/typescript. In .ts file
CODE// reference the mft component @ViewChild(‘mft’) mft: ElementRef; .... // create workflowo bjects input to be send to mft component const workflowObjects = [{ ObjectId: 'pf://abcvpms3/item/VX-594', Title: 'Batch Upload Test', ContextType: 'Platform', RenamedTitle: 'Batch Upload Test', TimeCodeIn: '900000@25:1', RelativeFramecountIn: '0@25:1', Duration: '186@25:1' }]; // pass the workflow object as input to mft component this.mft.nativeElement.workflowObjects = workflowObjects
below is the list of MFT component input and output parameters.
Inputs | Description | Example |
---|---|---|
auth-service-url | The url to the identity server authentication service | |
auth-redirect-url | When the authentication service authenticated the user, the auth service will redirect to this url. Note: this url must be configured as “redirect url” of auth service | |
auth-service-client-id | The client id to use for this authentication | implicit |
auth-service-scope | The scope for this client id | openid profile api1 |
auth-logout-url | The url to redirect to when logging out | |
auth-silent-refresh-url | The silent refresh html that oidc client use to refresh the auth token | |
mft-send-to-url | Mft component do not directly access vidispine, config portal or get MFT target directly. Instead request are made to a proxy “mft service” which then routed to Vidispine or config portal api. So this is the url of that proxy service. | http://host.docker.internal/Platform.Mft/Proxy/Platform.Mft/Proxy |
header-text | Header text on the MFT component | MFT Dialog |
item-id | Vidispine Item id of the workflow object | ITEM-VX-2 |
4. Output of MFT component
Output | Description | Sample |
---|---|---|
mftWorkflowTriggered | Triggered when user click on send and a workflow is triggered. |
CODE
|