The mechanism to identify a set of components that make up a playbook, would be the same mechanism you could use to identify a smaller subset of components, even individual ones. We would not propose having one mechanism for individual component export and a different one for exporting multiple components.

I don't understand why the idea I uploaded merged into this? Doesn't this mean complete export function of whole components up there? What I wrote was a component of those components to be able to be exported. (ex. a single workflow from Workflows to be exported)

We currently have designs under way and hope to get them scheduled in the roadmap soon. Our Apps and App Host deliverable built out much of infrastructure needed to solve this problem so we will continue to build on top of that to deliver selective exporting this year.

What is the status of this idea? The last admin post is nearly a year old. And this is the far most expected functionality.

Incredibly useful functionality

Agree with the overall idea, want to extend it as following:

- Export files from Resilient

- Have it edited from scripts / manually

- Import to have changes implemented

Could be very useful for overall name changes, broader changes of core things (e.g. several field names has changed, so do a search & replace on the export instead of the slow and tedious web GUI).

This i needed. If I want to devleop my worklows as CODE and strore in version control I cant at this point.

Hi folks,

We wanted to give a general update on this Idea which is far and away our most popular one based on votes.

How we handle playbooks is of strategic importance to our product roadmap.

Our current priority in this respect is;
- Playbook UI Refresh where we look to improve the UX of working with the various components of a playbook.
- Extensions, where we look to improve the UX of installing apps and their associated configs (which are themselves components of a playbook)
- Tagging all components of a playbook
- Export/Import leveraging tagging.

The UI refresh and extensions are currently in progress and we hope to move to the other items including this Idea as per the above priority.

We hope you appreciate there are logical dependencies between the above items that are driving this sequence and thank you for your patience while we work on this area.

Please feel free to contact any of the product management team for more details or clarification on our plans in this respect.

On behalf of the Resilient PM team,

Martin

Could be used in export TAG related objetcs in order to allow export of all objects using the same TAG

Feature really useful for compliance needs, in order to give evidenceof processes and playbooks with auditors

We have compliance requirements to share our processes and playbooks with our auditors.  Not having this feature has kept us from using "Tasks" within Resilient.  Right now each incident that's created gets task with a link to a Word document playbook on our SharePoint site for the applicable incident category .  Talk about not using the product to its potential...

For this feature I'd like to also emphasize the importing and exporting of Wiki Pages from Organizations, or just the ability to do so in general. While Organizations can be separate, similar functions can exist across these silo'd instances. The ability to export into a .res or .xml/.csv, etc., would be helpful.

Related Idea: https://2e4ccba981d63ef83a875dad7396c9a0.ideas.aha.io/ideas/R-I-270

 I vote for this enhancement

Feature really missing