Forum Replies Created

  • Nina Schmidt
    Moderator
    • Topics: 0
    • Replies: 5
    # 8 months ago
    Up
    0
    Down
    ::

    Hi Nicole,

     

    you can do this, by using mostly SQL statements.

     

    Before I tell you how I just want to mention that this isn’t the best practice in SQL Database design. When you create one table for each user, you can end up with a large number of tables, depending on how many users use your application. Typically, we would suggest to have one table for all users and a second table with the detailed information of the users. They would be linked via a foreign key, so you know which detailed information belongs to which user.

     

    Since I don’t know your use case in detail, maybe separate tables are an effective way of handling your use case. So here is how you would create a table for each user:

     

    You can create new tables directly from the running app with a connector call or a business object function.

    As attachment you can find an example how a connector call could look like.

    As you can see in the picture, the create statement uses CREATE TABLE IF NOT EXISTS. So, it will only create a table if no table with this name exists.

     

    The table name would be variable and be given to the connector call via the input parameters. The name should be created for each user by the same pattern. When creating the pattern you should take in consideration, that German Names have often characters which are not supported in table names. Since you don’t want your pattern to be visible in the client, I would suggest to implement this logic of creating the name in a serverside business object.

     

    To get some user information you can use Simplifier.User.getCurrentUser(). With this you get Information from the logged in user, like the email address. Here you find the documentation of this method.

    After you created a table name you can trigger the connector call with this name directly inside the business object.

     

    This business object should be triggered after the user has finished the login into your application.

    Attachments:
    You must be logged in to view attached files.
    Nina Schmidt
    Moderator
    • Topics: 0
    • Replies: 5
    # 10 months ago
    Up
    0
    Down
    ::

    Hello together,

     

    As we now have a marketplace you can find a PDF generation example to download at any time. Also, you can find articles on how to generate PDFs and to create a PDF template in our Knowledge Base.

     

    In general, we still recommend to use the “PDFViewer_PDFJS” widget instead of the PDFViewer widget.

     

    For me, these are the two main reasons:

    1) The PDFViewer doesn’t display PDFs on mobile devices, but instead shows only the toolbar with a download button is visible. This limitation is still persistent in the current openui5 version 1.92, as you can see in the official documentation: sap.m.PDFViewer

     

    2) If you want to use base64 as a source you have to use a data URI like “data:application/pdf;base64,<your-base64-encoded-pdf>”. Additionally, you have to whitelist this URI in advance. Example: “jQuery.sap.addUrlWhitelist(undefined, <your-dataURI>);”. For more information about whitelisting in openui5, have a look in the official documentation: URL Whitelist Filtering

     

    I hope this clears up some questions.

     

    Best,
    Nina

    Nina Schmidt
    Moderator
    • Topics: 0
    • Replies: 5
    # 1 year ago
    Up
    0
    Down
    ::

    Hi Christopher,

    the 6.0 release on Docker Hub is a stable release.

    You can find links to the release notes and change log below.

    Release notes: https://community.simplifier.io/doc/current-release/getting-started/simplifier-release-notes-6-0/

    Change log: https://community.simplifier.io/changelog/

    Cheers,
    Nina

    in reply to: Simplifier Release 6.0
    Nina Schmidt
    Moderator
    • Topics: 0
    • Replies: 5
    # 1 year ago
    Up
    1
    Down
    ::

    Hi JMH,

    you can use the html <pre> element. With it you can display formatted text exactly as you define it in your html document. You can read more about it here.

    I tried this in a small example and got the following result:

    Picture final PDF: See Attachment “PDF_withLinebreaks”

    Picture text field: See Attachment “textField”

    Code in the PDF Plugin  template:

    <h2>Welcome to the PDF Generator</h2>
    <p>Content of text field saved as String</p>
    <pre>{{textfield1}}</pre>
    

    Is this the format you are looking for?

    Best regards,

    Nina

    Attachments:
    You must be logged in to view attached files.
    in reply to: Linebreaks in PDF
    Nina Schmidt
    Moderator
    • Topics: 0
    • Replies: 5
    # 1 year ago
    Up
    2
    Down
    ::

    Hi Klaus,

    in your Simplifier instance you can specify the lifetime of the user’s authentication token.

    As soon as the token is expired the user will get a 401 error when he triggers any action where he needs to interact with the server. Hence, he is not authenticated anymore.

     

    We created a Business Object (BO) which can help you to notify the user when his authentication is expired and tells him to reload the application.

    You can find a detailed description how to use it and where to download the BO in the knowledge base article below:

    https://community.simplifier.io/knowledge/how-to-check-simplifier-token-validity/

    On the end of the article, you will also find some information on the Simplifier token in general.

    Best regards,
    Nina

Viewing 5 posts - 1 through 5 (of 5 total)