Azure Connectors Node.js SDK
    Preparing search index...

    Interface InPersonFieldResponse

    Definition: InPersonFieldResponse

    interface InPersonFieldResponse {
        authentication?: FieldAuthentication;
        dimensions?: FieldDimenssionResponse;
        display?: string;
        display_order: number;
        embedded: boolean;
        field_name?: string;
        level_of_assurance?: string[];
        order: number;
        page_no: number;
        placeholder?: string;
        process_status?: string;
        processed_as?: string;
        processed_by?: string;
        processed_on?: string;
        signature_sub_type?: string;
        type?: string;
        verification?: VerificationResponse;
    }
    Index
    authentication?: FieldAuthentication
    display?: string

    Returns the visibility value of the inperson field, possible values are "VISIBLE" and "INVISIBLE".

    display_order: number

    Display order according to the SigningHub viewer.

    embedded: boolean

    True, if field is part of the PDF document.

    field_name?: string

    Unique identifier of the field.

    level_of_assurance?: string[]

    In Person selected level of assurances

    order: number

    Order of the recipient to whom this field is assigned. If the field is not assigned to anyone, value will be null.

    page_no: number

    Page number of the document on which the field exists.

    placeholder?: string

    Name of the in-person signer or placeholder e.g., Customer, Sales Representative etc.

    process_status?: string

    Whether the field is processed or not. Possible values are UN_PROCESSED, PROCESSED.

    processed_as?: string

    User who processed the field as COLLABORATOR,DELEGATEE,GROUP_MEMBER or OWNER.

    processed_by?: string

    Email address of the user who processed the field.

    processed_on?: string

    Date time on which the document is processed.

    signature_sub_type?: string

    The signature sub-type for in-person signatures can be a WITNESS signature. If witness signatures are enabled in service plan, In-person fields are signed with a common certificate shared by all the users in the service plan. Possible values are WITNESS or NONE.

    type?: string
    verification?: VerificationResponse