Aller au contenu principal

Get editorId via script

Commentaires

3 commentaires

  • Zendesk API User
    Author: StefanSchulz - 7/23/2020 12:27

    Hi Andres,

    I am not sure about the "one JSON per project" approach, but I assume that's a requirement. FirstSpirit offers many ways to create JSON instead of HTML, which may help for a better solution.

    But to your problem:

    Programmatically, you can use the RenderingAgent to render content of FirstSpirit elements. If the template contains an editorId() call, this should get you to a solution. Depending on where you start the script, you will have access to a context or a broker providing this agent on request.

    Here you will find the API of the agent and an example on how to use it:

    RenderingAgent (FirstSpirit Developer-API)

    Hope this helps. More questions welcome.

    Best regards

    Stefan

    0
  • Zendesk API User
    Author: agarcia - 7/23/2020 14:14

    Hi Stefan,

    I think RenderingAgent is not available in my version.

    I'm not finding anything when searching for it in my server help page.

    Sorry I forgot to mention that I'm running FS 5.2.905.76007.

    Could you point me to those ways of working with JSON?

    Thank you!

    PS: I guess update to a newer FS version is the right way to go for this issue but unfortunately not in my hands :smileysad:

    0
  • Zendesk API User
    Author: StefanSchulz - 7/24/2020 9:11

    Hi Andres,

    Version 905? Ugh. Over 3 years old stuff.

    Sorry, but that's to old to remember features. And, of course, it's not supported by our technical staff.

    What is always possible is to have a dedicated channel that produces JSON instead of HTML. The output, of course, would have the same file structure as the HTML-Version. Maybe you could run some script afterwards to collect the results and generate your project-JSON.

    Best regards

    Stefan

    0

Vous devez vous connecter pour laisser un commentaire.