Scenario
How to upgrade a Nintex for Office 365 workflow to Nintex Workflow Cloud that uses the action, Office 365 Check In Items.
After Upgrade
- Your start event Connection property will need to be updated with an existing connection to SharePoint in your Nintex Workflow Cloud environment.
- The Check In Item action will become SharePoint Online - Check in files in Nintex Workflow Cloud.
- The new action will need to be completely reconfigured including pointing it to your SharePoint site, specific document library, and specific document(s).
Differences
- The action, SharePoint Online - Check in files, in Nintex Workflow Cloud, works by allowing you to selectively check in one or more files in a library by using conditions.
- You can now configure conditions using the condition builder to point to the specific document or multiple documents you would like to check in.
- The check in file limit property allows you to set the maximum number of files the workflow action can check in at once when it executes. Note, 5000 files is the system maximum.
- You can select to include files in subfolders if you would like to recursively check in files.
- The Check in version property allows for Major, Minor, and Overwrite only.
- You can store the result of the action in an object variable that contains boolean values indicating whether your files were successfully checked in.
- CAML queries are no longer supported.
Configuration
- Reset the Connection property in your start event to point to an existing SharePoint connection. By doing this first, other SharePoint related actions may automatically use this connection later in the workflow when you reconfigure them.
- Under the Source files section, copy and paste a link to the SharePoint site where your document library lives inside the SharePoint site URL property. Then click the Retrieve libraries button to populate the Document library lookup list property. Notice upon first selecting this action on the design canvas, the connection property automatically sets itself to the same connection from the Start Event.
- Under the Conditions section, select Add conditions to open the Conditions builder. In this example, we use the LeaseNumber variable passed into the workflow that points to all documents that have that value in the Lease Number column in the SharePoint library. This tells the action to only check in the SharePoint documents using that Lease Number value in the library.
- Configure the options Include files in subfolders, Check in file limit, Version, Comments, and the output result variable based on your needs. Note, you can insert variables in place of specific text in these properties for more dynamic capability.
- You can access the contents of the result variable later on in other actions of the workflow. In this example, we can use the action, Log to instance details, to show the value for the boolean status variable to ensure it successfully checked in all our files.
