Converse agora com nosso suporte
Chat com o suporte

Essentials for Office 365 2.14 - User Guide

Product Activation Tool Overview
General Tool Configuration Profile Manager Proxy Mode Azure Turbo and CSOM Creating User Mapping Creating User and Template Reports Support and Troubleshooting Modes of Migration
Home Tab Migration Analysis Tab Migrator Tab
Interface Connect to Resources Copy Sites Live Compare Hyper Mode Classic Mode Copy Alerts Orphaned Users Copy In-Place Tagging of SharePoint Items Incremental/Delta Copy Forms Migration Workflow Migration Save Site to XML
File Manager Tab Drives Tab
Interface Overview Migration Job Structure Connecting to Resources Copy Google Drive Copy File Share Copy My Sites to OneDrive for Business Copy Tenant Copy Box Copy Dropbox Nintex Deployment
Post Migration Compare Security Manager Tab Term Store Manager Tab Administrator Tab Backup Tab
Interface Overview Backup Job Structure Advanced Search Retention Policies Storage for Backup Import/Export Backup Archives Connecting to SharePoint and OneDrive for Business Connecting to Cloud Storage Hyper vs Classic Backup Setup Hyper SharePoint Online Backup Hyper OneDrive Backup Hyper Office 365 Groups Backup Smart Backup Classic SharePoint Online Backup Classic OneDrive Backup Classic Office365 Groups Backup Classic Mailbox Backup Change Properties for Backup Admin Management Scheduling Backup Jobs Backup Project Conversion
Help Tab View Tab Scripts Troubleshooting Appendix About

Wait for Item Update

During migration to SharePoint Online, the on-premises Nintex Workflow action "Wait for item update" will be transformed into the Nintex Online Workflow action "Wait for Field Change in Current Item".

The following differences related to parameters and configuration should be noted:

On-premises Parameter


"Wait for" references

An equivalent parameter for "User profiles" and "Workflow constants" is not available and therefore this configuration will be lost.

Comparison Operator

Only the "to equal" operator is available in the online equivalent action.  All other operators will be lost.

For additional possible differences, please refer to the General Workflow Objects section.

Save Site to XML

When a site or site collection is loaded into Essentials, a great deal of information is cached by the product. Occasionally users need to re-purpose that information for other needs. The "Save Site to XML" functionality provides a facility for exporting this information into a commonly used format.

1.Right-click on the site you wish to save and select the Save Site to XML option from the provided menu.
save site to xml

2.Enter a location to store the file in the provided field. Secelt Finish to complete the operation.
save site to xml 2

File Manager Tab

Essentials File Manager is designed to enhance and simplify the interaction between SharePoint and File Systems. SharePoint already provides basic functionality to load a single or multiple files. However, there are many gaps in that functionality that Essentials File Manager fulfills including the ability to Load and Download (off board) content with metadata. Here is a sampling of these features:

·Uploading Content

oAbility to set metadata as part of the loading process.

oAbility to extract metadata from file system folders and assign them to SharePoint metadata.

oAbility to retain or unwind the folder structure in SharePoint.

oAbility to retain the core properties such as created/modified by and created/modified at.

oLoad files and metadata using a spreadsheet (CSV).

oAuto-creation of CSV for loading based on content in the file systems.

oAbility to load files with pseudo-versioning to SharePoint versions.

·Downloading Content (Off boarding)

oAbility to download content from sites, sub-sites and libraries into the File System with metadata stored in CSV files.

oAbility to Load downloaded content back into SharePoint.

oAbility to retain pseudo-versions in File Systems.

oAbility to remove downloaded content.

oAbility to copy NTFS file system folder permissions.

Interface Overview

The application consists of two primary panes and one optional pane: (1) Navigator, (2) Contents/Objects Area, (3) Connections area. A set of windows is automatically generated when a Loading or Downloading operation is performed.
file manager Interface 1

The picture above represents the default arrangement for these panes.


NOTE: We have found this to be the ideal configuration, but the individual panes may be rearranged, minimized or maximized.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação