Export Engagement Contents From PX

It would be great if we could export a PDF of the engagement content. This would make it easier for my team to send their content to the editors. 

@mmarques and @Brianna Goodrum we are thinking about this. It would be helpful if you could share more on the questions below:

1. Would you want downloadable PDF or it should auto create an Email with the attached PDF to be shared across internally?
2. If the Engagement is localised - you would prefer only English PDF or PDF for each version separately?
3. Is it only the content that needs to be verified? Or a video recording of how the engagement appears on the end application is important for review?
   1. Eg: steps could be tooltips and how they are positioned etc is also needed for review?
4. How would you like users to share comments or feedback? Would it be done offline and then updated to the Engagement?

Thanks,

Abhilash

@aharkut - I would love to see an export option also.   I think this could help cover the gap in another idea asking to be able to non-destructively update templates (below).  If I could export the “code” behind the engagement (as JSON or XML), I would hope I could do find/replace operations to update colors, padding, button radius, verbiage, etc.   The flip side is that I would also need a way to Import the updated “code” of the engagement back in to overwrite the existing engagement content.   I would also think this might be something that could be added to the API library and possibly automated.

Adding some followers:   @jmobley @Hlovett 

@aharkut - Sorry, but I just noticed your questions now. 

1. My team would want to download the PDF. However, if this is a batch job with the resulting PDF emailed to the requester, that is also acceptable.
2. We are not currently localizing engagements. If we did localize engagements, exporting a PDF of the localized engagement would be a good option.
3. For engagements with tooltips, we need to show the tooltip in context. However, because this is a review by editors who leave comments, we still need a PDF. Could this be an option from preview mode? 
4. Feedback is offline (in the PDF), and it is up to the content developer to apply feedback. If this were for localized engagements, the translator would update the localization to import.

@aharkut - #3 on my above point is now optional, because reviewers can look at the engagement within the product and leave feedback in the PDF