nintex workflow sharepoint

empty, "section" Control hides(2) Custom "Submit" and "Close" buttonsInsert a two button control, such asAdd a rule for the submit button as follows "Disable submit after commit" rule"Error message Prompt" rules, such as"Error message emptying" rule, such as"Submit Form" rules, such asAbout the settings for the data connection "master commit", such asFile name format is (author _ date _ Time)Test User _20120720_003011Concat (String (Iuser), "_", translate (translate (substring (now (), ":", "")

assigned for the first time. Otherwise, the task is reassigned.If (String. IsNullOrEmpty (e. TaskProperties. AssignedTo )){E. TaskProperties. AssignedTo = "helloworld/user1 ";E. TaskProperties. ExtendedProperties ["Comments"]= "Please input approve comments in here .";}Else{E. TaskProperties. ExtendedProperties ["Comments"] ="Task is reassigned to you ";}} 3) design the InfoPath form: When the ReAssign check box is selected, the "Reassign this to" area on the right is displayed. The rules of

activity cannot be found. Step 2)Process "sign approval" Specify the completionmode for approval as requireall and executiontype as parallel. Bind the taskoutcomes attribute of "sign for approval" to the workflow field: Handle the initialized event of "sign for approval: Private void will sign approval _ initialized (Object sender, eventargs E){This. will sign for approval. Users. Add ("DC \ user1 ");This. will sign for approval. Users.

Scenario 1: A workflow customized using SharePoint designer or a workflow provided by a template You can use the eventhandler Extension Method to add the permission control statement to the itemadded eventhandler task list of the new task. Only assign the permission of the current item to the task assign to object, or assign the read-only permission to other

Many friends who use kaneboy. spsworkflow always want documents to be copied across sites. That is to say, in a process action, documents can be copied from one site to another. Today, I updated kaneboy. spsworkflow and added two new flow actions, cross-site copy and file deletion. (STRANGE: Why didn't these basic actions be added before ?), The accompanying DOC file is also updated. You can download it from the SharePoint

SharePoint state machines with built-in default process logic As we mentioned in the previous article, SharePoint's task encapsulation mechanism determines that there are two problems with its state machine application, one is to add one eventdrivenactivity for each approver, and the other is that the approval number must be determined during the design period. Is there any way to solve these two problems? Thanks to WF's ability to dynamically modif