EngageOne

 View Only
  • 1.  Improving performance when publishing Designer resources to EngageOne Admin

    Employee
    Posted 02-14-2019 12:07

    Are you suffering from poor performance when publishing resources from Designer to EngageOne Admin?

    Consider the following options to speed things up.

     

    Option #1 –Designer Device Publish, "Enable as EngageOne" Output  Device option

    DO use when:

    • New Publication / Active content requires publishing all resources to specific device

     

    • Publication / Active content has significant design resource updates – many new fonts/ images

     

    Do NOT use when:

    • NO Design font / image resource has changed as you will see a large performance overhead for no gain in both Designer Publish and EngageOne Admin Templace/AC ingestion

     

    Option #2 – Designer "Tasks / Publish resources for EngageOne" using EngageOne Admin exported Delivery management resource list

    DO use when:

    • A single or a very small number of resources have been added to Design Publication (Template) or Active content

     

    • A resource is missing for all required devices

     

    • All resources are missing for a specific device

     

    Do NOT use when:

    • Publishing all Publication resources to all devices

     

    Best practice:

    1. Use the Designer Device "Enable as EngageOne Device" (Option #1) to populate your Devices when you FIRST publish to EngageOne Admin.

     

    1. Having verified successful EngageOne Admin Template / Device import, Delivery Channel, Option configuration and successful document delivery, then turn this Designer Device option OFF.

     

    1. For subsequent Design Publication / Active Content font / image additions, enable the specific Device(s) required as "Enable as EngageOne Device" and use the Designer Tasks / Publish resources to EngageOne (Option #2) using the EngageOne Admin exported Delivery Management resource list to publish specific resources to specific device(s).

     

    Using this approach will allow a faster publish from Designer to EngageOne Admin, particularly when there are no or very few additional font / image resources

     

    Tip:

    If your Designer Device settings e.g Font / Image Embed, etc – OR - Resource Map settings have been updated, you MUST Clear the "Publish for EngageOne" Printer cache i.e Tools \ Resource Cache management,  before the updated Device settings will be republished and hence applied to the EngageOne Admin Device / Channel / Option.

     



    ------------------------------
    Paul Barron
    Principal QA
    EngageOne Compose (Designer / Generate)
    Watford, United Kingdom
    ------------------------------


  • 2.  RE: Improving performance when publishing Designer resources to EngageOne Admin

    Posted 05-17-2021 08:03
    Hi Paul,

    Thank you for sharing this in the community. Could you confirm if the Export Resource List could also be generated using a webservice as PromotionService or another tip, not using the EngageOne Admin console directly.

    Thank you in advance for your time.
    Marta Haro

    ------------------------------
    Marta Haro Honrubia
    Tessi Iberia
    Madrid
    ------------------------------



  • 3.  RE: Improving performance when publishing Designer resources to EngageOne Admin

    Employee
    Posted 06-01-2021 04:56
    Hi Marta.

    The EngageOne Server Admin -> Export Resource List functionality is not currently available as a REST Web service call in EngageOne Server Admin 4.4.x.

    This feature is on the list of functions to be included in a future EngageOne Server release.


    ------------------------------
    Paul Barron
    Principal QA
    EngageOne Compose (Designer / Generate)
    ------------------------------