Set Up an Operator Form

  1. Create a new entity for applications, for example, FTOS_Test_Operator_Applicant. Add the attributes needed for your journey. Picture OCR and Selfie are usually displayed on the Operator page, so they are recommended. (For details on how to create an entity, see Business Entities; for details on how to add attributes, see Add Attributes).

  2. Create a new entity, FTOS_Test_Operator, and add the following attributes: videoCallResult, applicandId, and operatorType.

  3. Extend entity and add virtual attributes (for details, see Extend platform data entities with transient data entities).

  4. Create FTOS_Test_Operator_Client form driven flow on the FTOS_Test_Operator entity which will collect the relevant data. For details on how to create a form driven flow, see Form Driven Flows). For the video step, add the following code in the After Section Save section.

    Copy
    // For Ecosystem SysPack 2.5.0 and later, use:
    var dfpHelper = ebs.importClientScript('FTOS.ECOS.Utils');

    // Prior to Ecosystem SysPack 2.5.0, use:
    // var dfpHelper = ebs.importClientScript('FTOS.DFP');

    ebs.removeFormEditButton('ebsContainerContent');

    context.stopNextNavigation = true;
    var componentName = 'FTOS_DFP_VideoStreaming'

    var params = {};
    params.flowSettingsName = formData.FlowSettings;
    params.processorSettingsType = 'VideoStreaming';
    params.processorSettingsName = 'FTOS_Test_Operator_VideoComponent';

    ebs.callActionByNameAsync("FTOS_DFP_FlowProcessorSettingsByType", params).then(function(f)
    {
        console.log(f);
        var processorSettingsId = f.UIResult.Data.ProcessorSettingsId;
        dfpHelper.loadComponent(componentName, processorSettingsId, formData.id, false);
    });
  5. Flow settings will be set on the form driven flow's Before Events section: formData.FlowSettings = "FTOS_Test_Operator";. Example of Flow settings:

    Copy
    {
        "DestinationEntityName": "FTOS_Test_Operator_Applicant",
        "SourceEntityName": "FTOS_Test_Operator",
        "SourceLookupDestinationName": "applicantId",
        "maskNextStepURLSuccess": { "entity":"FTOS_Test_Operator", "form": "FTOS_Test_Operator_Client", "section": "Finished" },
        "maskNextStepURLFail": { "entity":"FTOS_Test_Operator", "form": "FTOS_Test_Operator_Client", "section": "Finished" },
        "ContextForm" : "FTOS_Test_Operator",
        "QueueParameters":
        [
            {
                "ParamName": "Name",
                "ParamValue": "QueueOperator"
            }
        ]
    }
  6. Add QueueOperator to your queues list, then add the new queue to all operators that have access to this queue:

  7. Create the FTOS_Test_Operator form driven flow on the FTOS_Test_Operator entity and set it as default and default for edit.