Tag: Nintex Workflow

Nintex Workflow and Nintex Forms now available in the SharePoint Store

From Nintex: We are pleased to announce that we have updated our apps for Nintex Workflow and Forms for Office 365, now available for download from the SharePoint store. We’re focusing heavily on the great feedback being provided by our community, and we’re working on packing in as many features as we possibly can. You will continue to see us adding new, exciting features to deliver a compelling user experience and capabilities that allow our customers to be more productive on a powerful cloud platform.

Nintex Workflow for Office 365

http://office.microsoft.com/en-us/store/nintex-workflow-for-office-365-WA104114857.aspx?queryid=0712995b%2Dd4fe%2D4fee%2Da4fd%2D8b6b4c75756f&css=nintex&CTT=1
Nintex Workflow for Office 365 is available as a free, fully featured 30-day trial. Continued use requires an active subscription licence from Nintex. For more details, Nintex sales can help you make direct contact with one of our partners. Learn more at http://www.nintex.com/workflowO365

NintexWorkflowforOffice365a

Nintex Workflow for Office 365 provides a powerful and intuitive web based designer to build 2013-style workflows for Office 365.Empower business users and IT professionals alike, to quickly and easily automate business processes; from a simple leave approval request, to complex integration across external applications, cloud services and data sources. You can now integrate people, content, and applications.

With Nintex Workflow for Office 365, users can:

  • Onboard Users into Office 365 and assign licences
  • Automate provisioning of SharePoint sites, collections, and other resources
  • Assign and track IT help desk tickets and customer support cases
  • Gather content from and publish content to third-party repositories
  • Scan social media for actionable discoveries
  • Crowd-source content reviews on Yammer
  • Manage leave requests and expense claims
  • Review and edit press releases
  • Manage budget reviews and approvals.

Nintex Workflow for Office 365 includes support for in app purchases of additional actions via the Nintex Store.

Known for being a leader in SharePoint workflows, Nintex is now enabling Office 365 users to create and run workflows in the cloud, leveraging SharePoint’s native actions. Visit www.nintex.com for more information.

Nintex Workflow for Office 365 does not support Internet Explorer 8.0.

Nintex Forms for Office 365

http://office.microsoft.com/en-us/store/nintex-forms-for-office-365-WA104137886.aspx?queryid=0712995b%2Dd4fe%2D4fee%2Da4fd%2D8b6b4c75756f&css=nintex&CTT=1
Supercharged for Office 365 – Create powerful, dynamic web forms to collect data within SharePoint Online.

NintexFormsforOffice365a

With Nintex Forms for Office 365 you can quickly and easily create tailored, engaging forms using simple drag and drop capabilities with customization options. From simple approval forms to complex data capture and calculations, you can input data, update data, and trigger workflows. When combined with Nintex Workflow for Office 365, the possibilities are endless. You can create complete business applications that range from a simple leave request system to a complex order processing system connected to third party cloud or on-premises applications.

Nintex Forms for Office 365 gives you the power to design the right interface for your users.

Get started with a fully featured free 30-day trial now! For more details, contact sales@nintex.com.

Nintex is the world’s leading SharePoint workflow company, with over 5000 customers in 90 countries serviced by a global network of high quality partners and service providers. Nintex delivers innovative software and cloud services that empower organizations to automate business processes, quickly and easily.

Nintex Forms for Office 365 does not support Internet Explorer 8.0.

Resolving Nintex Feature Activation issues after migration

Issues have been reported with data migration tools used to transfer   content from a SharePoint 2010 environment to a SharePoint 2013 environment.   The tools are preventing the Nintex Workflow site collection feature from   activating in the 2013 environment.

Scenario

Site Collection A is in a SharePoint 2010 environment with the Nintex   Workflow 2010 feature activated.

Site Collection B is in a SharePoint 2013 environment without the   Nintex Workflow 2013 feature activated.

A data migration tool is used to move data from a team site in Site   Collection A to a team site in Site Collection B.

Issue

Some data migration tools detect that a site column or content type   from Site Collection A is not present in Site Collection B, and then recreate   these assets at the target team site. In this case, it will recreate a Nintex   Workflow-installed content type and site column.

Later, when a user attempts to activate the Nintex Workflow site   collection feature, it will fail. The message in the SharePoint logs will be   similar to:

The field with Id {c2dd77c1-89a4-4f1f-b037-c17407e9922c}   defined in feature {0561d315-d5db-4736-929e-26da142812c5} was found in the current site collection or in a sub site.

In other words, the data migration tool has forcibly created a column somewhere in the site collection that the feature activation cannot overwrite, preventing it from activating.

Avoiding the issue

This issue will not occur if the Nintex Workflow 2013 site collection   feature is already active on the target site collection prior to migration.

Fixing the issue

Option   1: Activate Feature with Powershell and use the Force

From an administrative SharePoint Powershell:

Put in the folder name of the feature in question in the   “identity” parameter. You can find the folders under

SharePoint   2010:
C:Program FilesCommon Filesmicrosoft sharedWeb Server   Extensions14TEMPLATEFEATURES

SharePoint   2013:
C:Program FilesCommon Filesmicrosoft sharedWeb Server   Extensions15TEMPLATEFEATURES

Example:

Enable-SPFeature –identity "NintexWorkflowInfopath" -URL <a href="https://go.mysite.com/mysitecollection/">https://go.mysite.com/mysitecollection/</a> -force

Option 2: Feature Site Column Cleanup Tool

In response to this issue, Nintex developed a utility to clean up any site columns and content types that exist in a sub site in a site collection.

This tool recursively searches every site in a site collection, checking for all Nintex Workflow content types and site columns, and optionally attempts to delete these assets.

It will print the location of any founds assets to the console window.

Once the assets have been removed, the site collection feature will activate correctly.

The tool is available from http://download.nintex.com/sl/supportfiles/support_utilities/NW2010/FeatureSiteColumnCleanup.zip

It should be downloaded to a SharePoint server and run from a command console window as an account that has access to modify all sites in the site collection.

Depending on the number of subsites in the site collection, the tool may take some time to run. The tool will print “Process complete” to the console window when it has finished processing.

Usage

FeatureSiteColumnCleanup.exe "siteCollectionUrl" [-deleteFound] [-includeRootWeb] [-searchUsage] [-skipFields] [-skipContentTypes]

siteCollectionUrl: The URL to the top level site of the site collection that requires processing.

-deleteFound: If this argument is included, any found content types of site columns will be deleted. If this argument is not included, the tool will only report the location of these fields.

-includeRootWeb: If this argument is included, the root team site will be included in the search for assets. Please note that if the Nintex Workflow feature has activated correctly, the assets will exist at the root team site and should not be deleted.

-searchUsage: Specifies whether each list on each site should be checked to see if it uses a Nintex Workflow content type

-skipFields: Specifies whether the process should not check for field assets

-skipContentTypes: Specifies whether the process should not check for content type assets

Example

FeatureSiteColumnCleanup.exe "<a href="http://sharepoint/sites/portal">http://sharepoint/sites/portal</a>" –deleteFound

From <http://connect.nintex.com/forums/thread/12937.aspx>

Option 3: SQL Method aka “Hammer of Thor”

Warning: Unsupported by Microsoft and most likely Nintex!

Identify the Nintex-related Content Type GUID’s and update their “IsFromFeature” property to 0, in the relevant content databases.

Update [dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x0101EF0201%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x010801005CC0%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x0108010064E42%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x0108010079DBDE6%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0 where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x01010024055%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0
where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x01010024055%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0
where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x010100F815D979%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0
where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x010100F8376F531%')

Update [dbo].[ContentTypes] set [IsFromFeature] = 0
where (sys.fn_varbintohexstr(ContentTypeId) LIKE '0x010100240555%')

Business Hours in Nintex Workflows

In Nintex Workflows you can define when the workflow will execute in the context of the the business entities “working hours”.

When refering to business hours, these are the hours of operation defined in Site Settings > Regional Settings of the site where the Nintex Workflow resides. You can also set your public holidays which can be included through Site Settings > Manage Holidays

Also – a special tip – (thanks Colin for clarity) –  although the Pause Workflow action can be set to 1 minute in it’s settings, it will actually never execute in less than 5 intervals as it is dependent on the SharePoint time job. Important to remember as you may be wondering why your workflow takes ages to finish if you try and insert <5 minute intervals. It is actually 5 minutes + the duration of the workflow sequence + the minute interval you selected.