This is the documentation for an older version of Scroll PDF Exporter. Here you can view the most up-to-date version of the Scroll PDF Exporter documentation.

Using Page Properties as placeholder

It's possible to use the Page Properties Macro to define customized placeholders in your exports.

Info

Currently it's only possible to use text as placeholder in the page properties macro. The requirement to also display images is already tracked in our JIRA system: EXP-924 - jiraissue.placeholder.waiting.to.load jiraissue.placeholder.status

Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, comment on or vote for this issue. You'll then get a notification for every status update on the issue.

To use page properties as placeholders:

  1. Open the root page of your exports.
  2. Insert a page properties macro to your page and a two-column key-value table.
    (info) The first column of the table will be the keys and the second one will be the corresponding values
    (info) The two-row table set up is not supported
  3. Save the page.
  4. Open your template and insert the placeholder in the following pattern:$pageProperty.from("User")
    (info) Please note that the placeholders are case-sensitive.
    This placeholder will be replaced with the corresponding value stored in the content properties macro for the key with name "User".

  5. If you have multiple page property macros on your root page, you have to assign an ID to the macros and refer to this ID in your template.
    For example:$pageProperty.from("User", "123")
    This placeholder will be replaced with the corresponding value stored in the content properties macro with ID 123.

When exporting Scroll Translations-managed pages that contain page properties macros, sometimes the value from a table within a Page Properties macro can be taken from the wrong language. There is an simple way of fixing this issue.