EspoCRM v7.4.0 released

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • murugappan
    commented on 's reply
    I have transferred this most to another discussion. This post is closed.

  • murugappan
    commented on 's reply
    yuri, my apologies. Will do that.
    Last edited by murugappan; 05-10-2023, 01:21 PM.

  • yuri
    commented on 's reply
    > Any help would be helpful.

    It's better to start another topic.

  • rabii
    commented on 's reply
    in order to control who access / retrieve data from the old instance. i think a manual workflow would work perfectly as it would enable you to have such functionality on certain entities and even you can control how the data is retrieved and if it should be persisted in db.

  • murugappan
    replied
    Thank you so much Yuri.

    I am now testing version 7.4 with extensions from Eblasoft, osom crm and devcrm.it. Fantastic extensions which answered many of my questions. Just built a system for Clinic Management which incorporate EMR (Electronic Medical Records), Clinic Visits (inc. review, assessment, treatment, prescription and diagnostics) and Wellness programmes.Currently being tested by users.

    Currently, reworking our existing CRM (version 7.3) using version 7.4. Our plan is not to migrate but to archive the existing instance and create a totally new instance. The only problem which we are cracking on is this:

    (1) New entries will all go to the new instance.
    (2) Frequently, the users would have to log into the old instance and refer to previous data such as emails and cases.
    (3) This has to be done manually which is not palatable to the users.

    The solution would be to provide the ability in the new instance to connect to the old and retrieve the info. I am not sure how it could be done. Any help would be helpful.

    Leave a comment:


  • MikeDunlap
    replied
    Thanks Yuri

    Leave a comment:


  • esforim
    commented on 's reply
    Thank you for the insight yuri! I'll start playing with it and hopefully bring back good news.

    That unfortunately regarding FPDF, it was reference a few times in the domPDF Github, same is true for the SVG. I guess it either outdated documents information or it in 'testing' phase.

    Anyway, upgraded to 7.4.3, time to slowly test it. Hope you had a good Easter holiday if there is one for your country... then work on v7.5 milestone

  • yuri
    commented on 's reply
    FPDF does not convert HTML to PDF. It's the lib for programmers who will write code to generate PDF they need.

  • yuri
    commented on 's reply
    Barcodes are rendered as SVG https://github.com/espocrm/espocrm/b...poser.php#L283. It can render SVG.

  • esforim
    commented on 's reply
    rabii I'm testing a bit on the demo of EspoCRM and reading domPDF discussion and documents. It seem that domPDF still have it weaknesses sadly. Some of which I found out is that it can't do SVG yet, and it can't do Fillable-form-field, where something like FPDF can do Form field: http://fpdf.org/en/script/script93.php

    But if I look more into FPDF I'm sure I can find weakness of it when comparing to TCPDF and domPDF... it is a pick your poison issue at the moment still. I'll slowly test it and see, the demo page of domPDF seem to offer lots of information and it got a Discussion board.

  • rabii
    commented on 's reply
    not yet. did you try it?

  • esforim
    replied
    Anyone started using the domPDF/v7.4 yet? What your impression?

    Leave a comment:


  • yuri
    replied
    Added 2FA support in portals in v7.4.1.

    Leave a comment:


  • Firyo
    replied
    Originally posted by yuri

    Partially. Minor adjustments might be needed to fix some style issues.
    Ok, thanks for the quick answer.

    Leave a comment:


  • yuri
    replied
    Originally posted by Firyo
    I was wondering if the old Tcpdf engine templates would be compatible with the new Dompdf one ?
    Partially. Minor adjustments might be needed to fix some style issues.

    Leave a comment:

Working...