A history of the various workflows ran on an item are kept. I want to achieve it using Nintex API. When a list has grown too large two approaches can be taken to address the situation: How to purge items from a large history list safely via PowerShell, How to quickly identify large lists in SharePoint, Defensive Workflow Design Part 2 - SharePoint Topology, Defensive Workflow Design Part 3 - Separation of Concerns, Defensive Workflow Design Part 4 - Slow Down and Speed Up, Defensive Workflow Design Part 5 - Batching.
var tabCtrl = document.getElementById('tabCtrl');
As I know my urls are only going to have colons ':' and forward slashes '/', that's all my UDA is catering for. If this global setting is enabled, much more detail regarding the execution and performance of workflows is stored in the database. If you had that option, that would be the way to go. This output is a collection of all of the attachment URLs, along with the identifying JSON key, extracted from the web result.
Here's a link to the NWAdmin White Paper : http://connect.nintex.com/files/folders/technical_and_white_papers_nw2010/entry12004.aspx.
Note: Existing workflow instances will complete using the old history list. Would be great to see where there are lists with a large amount of items. This will make the list hidden and less likely for a user to try to access it and modify the contents manually.
After we publish and run the workflow, we can go back to the Manage Workflow History Lists in Site Settings and we'll see that the number of items in our new list has increased. at Nintex.Workflow.HumanApproval.Message.AddContextDataToString(String input, NWContextDataCollection data, Boolean escapeValuesForSql, Boolean decodeInput) After many moons, I finally decided to sit down and automate some work that I regulary did manually. Configure the Update Item action by selecting Current Item for the Update setting, and selecting the AttachmentURLs multiline text field from the Field drop-down list. Finally, set Store Result In to the ServerRelativeURLsCollection.
Unpublish a workflow. Thanks for your help. a custom inline function would most definitely be more robust. Logs a user-defined entry to the workflow history list. These are like the ingredients in the recipe you’re about to read. at Nintex.Workflow.Activities.WriteToHistoryListActivity.Execute(ActivityExecutionContext executionContext) When following an instructional article like this, sometimes it’s easiest to just set up the variables you need at the start. i'm new to nintex workflow i want to get all the workflow history to make a report i tried through accessing the GetWorkflowHistory() method always it return 0 logs please help me to fix this thanks in advance. In the Input Text setting, click Insert Reference and select ServerRelativeURLJson from the Workflow Variables tab.
In addition to creating one to one mappings of Nintex and SharePoint content databases (Covered here: https://community.nintex.com/docs/DOC-1092). Second, the SharePoint site’s web URL is put back together with the relative URL given to us by the web request, so now we have a complete URL. I have used below command -, NWAdmin.exe –o PurgeHistoryListData -siteUrl http://......./sites/sitename -lastActivityBeforeLocal 2013-09-15 00:00 -state All, However its giving me below notification - "No matching workflow instance ids found in the Nintex Workflow database.". With Nintex Workflow 2010 and now Nintex Workflow 2013, you can create other history lists and configure workflows to use those. Nintex Workflow 2013 also logs information about each workflow instance, but that information is stored in several tables within the Nintex Workflow content database.
After this step, I used Regular expression steps to replace single, double quote and comma separately.
Printable View Click New from the ribbon and name the new History List something meaningful like the workflow name and history list.
As I mentioned, this only handles colons and forward slashes, but you can add more. You can use the GetWorkflowHistory service operation to retrieve workflow history for site workflow instances, filtered by workflow name and workflow state. I haven't done this though. we have one site page and there we just want to pass the list name and list item id or any unique id and it should give me the current state of the WF. } The replacement text is: The $1 tells the regular expression that we want to replace the entire line (the key-value pair) with the part that is in the first set of parentheses (the URL value). If you were to look at the resulting text from the response, it has a lot of information we don’t need, and the parts that we do need are identified as ServerRelativeUrl. After many moons, I finally decided to sit down and automate some work that I regulary did manually. For more information about how to understand the information returned by GetWorkflowHistory and GetWorkflowHistoryForListItem, see Understanding workflow history. Note: If verbose logging is not enabled, some properties, such as the BeforeProperties and AfterProperties collections, may not be available from the ActivityLogInfo object. | You must be a registered user to add a comment. Click the appropriate link below.
There are some limitations in SharePoint in regards to performance of lists that grow to be quite large. The workflow starts with a Build String action, configured with the following text: /_api/web/lists/GetByTitle('LIST_TITLE')/Items(LIST_ITEM_ID)/AttachmentFiles.