abap2UI5

Complex

File Uploader Example with Parameters

Z2UI5_CL_SMPC_APP_246

Controls sap.ui.unified UI5 1.71

The facts

Repository
abap2UI5/samples-controls
Class
Z2UI5_CL_SMPC_APP_246
Source file
z2ui5_cl_smpc_app_246.clas.abap
Library
sap.ui.unified
UI5 entity
sap.ui.unified.FileUploader
Demo kit sample
sap.ui.unified.sample.FileUploaderComplex
SAP's own sample
running at sdk.openui5.org ↗
Minimum UI5
1.71 — the floor abap2UI5 holds its samples to
In the playground
runs in the browser, with no system and nothing installed

Keywords: fileuploader, file, uploader, sap.ui.unified, fileuploadercomplex, html, verticallayout, fileuploaderparameter, button

Controls it builds

Read out of the builder chain by the abap2UI5 linter, not from the category this sample is filed under — which is what makes “which samples build one of these” a question the catalogue can answer at all.

Libraries

Run it here

The sample running, in this page — the app on its own, with no editor over it. Switch to Playground with this code

Nothing is installed and nothing is sent anywhere: the ABAP is compiled to JavaScript in this browser and runs against abap2UI5 itself.

The ABAP

z2ui5_cl_smpc_app_246.clas.abap — 121 lines Read it on GitHub ↗
" @keywords fileuploader file uploader sap.ui.unified fileuploadercomplex html verticallayout fileuploaderparameter button
" @summary File Uploader Example with Parameters
CLASS z2ui5_cl_smpc_app_246 DEFINITION PUBLIC.

  PUBLIC SECTION.
    INTERFACES z2ui5_if_app.

    DATA file_value TYPE string.

  PROTECTED SECTION.
    DATA client TYPE REF TO z2ui5_if_client.

    METHODS view_display.
    METHODS on_event.

  PRIVATE SECTION.
ENDCLASS.


CLASS z2ui5_cl_smpc_app_246 IMPLEMENTATION.

  METHOD z2ui5_if_app~main.

    me->client = client.
    IF client->check_on_navigated( ).
      view_display( ).
    ELSEIF client->check_on_event( ).
      on_event( ).
    ENDIF.

  ENDMETHOD.


  METHOD view_display.

    DATA(view) = z2ui5_cl_ui5_view_builder=>factory( ).

    view->ele( n = `View` ns = `mvc`
        )->a( n = `xmlns:l`   v = `sap.ui.layout`
        )->a( n = `xmlns:u`   v = `sap.ui.unified`
        )->a( n = `xmlns:mvc` v = `sap.ui.core.mvc`
        )->a( n = `xmlns`     v = `sap.m`
        )->a( n = `class`     v = `viewPadding`

        )->a( n = `xmlns:core` v = `sap.ui.core`

        " the sample's own ../style.css (shared by the sap.ui.unified samples and
        " listed in this sample's manifest) - the view carries the class and the
        " rule behind it has to come with it. \{ \} escaped: the XMLView parser
        " reads an unescaped brace as a binding
        )->tag( n = `HTML` ns = `core`
            )->a( n = `content` v = `<style>.viewPadding\{padding:1rem\}` &&
                                    `.sap-phone .viewPadding\{padding:0rem\}</style>`
        )->ele( n = `VerticalLayout` ns = `l`

            )->ele( n = `FileUploader` ns = `u`
                )->a( n = `id`             v = `fileUploader`
                )->a( n = `name`           v = `myFileUpload`
                " added attr (declared): two-way value so the backend can run the
                " original's empty-value check in handleUploadPress
                )->a( n = `value`          v = client->_bind( file_value )
                )->a( n = `uploadUrl`      v = `upload/`
                )->a( n = `tooltip`        v = `Upload your file to the local server`
                )->a( n = `uploadComplete` v = client->follow_up_action( val   = client->cs_event-control_global
                                                                         t_arg = VALUE #( ( `MESSAGE_TOAST` ) ( `show` ) ( `File upload complete. Status: 200 (Upload Success)` ) ) )
                )->a( n = `change`         v = client->follow_up_action( val   = client->cs_event-control_global
                                                                         t_arg = VALUE #( ( `MESSAGE_TOAST` ) ( `show` ) ( `Press 'Upload File' to upload file '{0}'` ) ( `${$parameters>/newValue}` ) ) )
                )->a( n = `typeMissmatch`  v = client->follow_up_action( val   = client->cs_event-control_global
                                                                         t_arg = VALUE #( ( `MESSAGE_TOAST` ) ( `show` ) ( `The file type *.{0} is not supported. Choose one of the following types: txt, jpg` ) ( `${$parameters>/fileType}` ) ) )
                )->a( n = `style`          v = `Emphasized`
                )->a( n = `fileType`       v = `txt,jpg`
                )->a( n = `placeholder`    v = `Choose a file for Upload...`

                )->ele( n = `parameters` ns = `u`
                    )->tag( n = `FileUploaderParameter` ns = `u`
                        )->a( n = `name`  v = `Accept-CH`
                        )->a( n = `value` v = `Viewport-Width`
                    )->tag( n = `FileUploaderParameter` ns = `u`
                        )->a( n = `name`  v = `Accept-CH`
                        )->a( n = `value` v = `Width`
                    )->tag( n = `FileUploaderParameter` ns = `u`
                        )->a( n = `name`  v = `Accept-CH-Lifetime`
                        )->a( n = `value` v = `86400`

                )->end(
            )->end(

            )->tag( `Button`
                )->a( n = `text`  v = `Upload File`
                )->a( n = `press` v = client->_event( `UPLOAD` ) ).

    client->view_display( view->stringify( ) ).

  ENDMETHOD.


  METHOD on_event.

    IF client->get_event( ) = `UPLOAD`.
      " original handleUploadPress: no chosen file -> 'Choose a file first';
      " else upload() then clear() (checkFileReadable is a client-side File
      " API probe with no declarative equivalent - its cannot-be-read branch
      " is not reproduced, see sidecar)
      IF file_value IS INITIAL.
        client->message_toast_display( `Choose a file first` ).
      ELSE.
        client->follow_up_action( val   = client->cs_event-control_by_id
                                  t_arg = VALUE #( ( `fileUploader` ) ( `upload` ) ) ).
        " clear( ) resets the control, which is all the original does after
        " upload( ). Clearing the BOUND field here as well would be worse than
        " redundant: a changed model is pushed BEFORE the queued follow-up
        " actions run, so FileUploader.setValue('') would reset the form and
        " upload( ) would post an empty one
        client->follow_up_action( val   = client->cs_event-control_by_id
                                  t_arg = VALUE #( ( `fileUploader` ) ( `clear` ) ) ).
      ENDIF.
    ENDIF.

  ENDMETHOD.

ENDCLASS.

More in sap.ui.unified

Search every abap2UI5 sample · the full list on one page

On this page