Extraction
  
Extraction
The extract functionality currently supports two scenarios described below.
 
Extract surface
As the name implies, you are here able to extract individual surfaces into a reusable surface component which will be located under your Sharebox 2.0 area, when ready.
 
Simply select the surface by pressing Export next to it.
 
 
 
A dialog will appear, and you need to, at least, give the surface a name:
 
 
 
Field
Description
Save as package name
The name you want the surface to have in the listings.
Package owner
Your name or similar
Description
What will be shown on the listing page
Long description
Text that will be shown in the detail view of the item
Package intro
Text that will be shown as instructions when beginning to deploy the package
Package icon
Attach if you want a unique image in the listings
Assets
Attach word/pdf/other if you want users to see them on the detail page.
Artifacts
Any widgets / utt’s etc that the surface needs to work. We cannot currently extract such things.
Make dynamic (images)
Check this if you do not want images to be extracted and included, but rather want to have to upload those on deployment.
 
 
 
Extract full configuration
Similar to the previous one, this also extracts, but in this case the entire Orchestra configuration. You start by seeing the existing configuration of the connected Orchestra summarized:
 
 
When you press extract you are also presented with a dialog:
 
 
 
 
Field
Description
Save as package name
The name you want the surface to have in the listings.
Package owner
Your name or similar
Description
What will be shown on the listing page
Long description
Text that will be shown in the detail view of the item
Package intro
Text that will be shown as instructions when beginning to deploy the package
Package icon
Attach if you want a unique image in the listings
Assets
Attach word/pdf/other if you want users to see them on the detail page.
Artifacts
Any widgets / utt’s etc that the surface needs to work. We cannot extract such things currently.
Make dynamic
If you want to make some or all entities dynamic (ie name on them) you check those boxes. For example, checking “Service names” will make them so that you need to enter service names every time you deploy that package. Not checking that box will keep the service name from the configuration.
 
When extracted, these packages will end up under your local / personal area under Packaged offerings.