•The 'Search' WindowsWorkflow activity has a new property XQuery, that specifies the GNQuery expression to use to generate the search. If empty of nor specified (the default) the activity use the old-style XML search conditions, if specified the old-style XML search conditions are ignored. Added a sample sequential WindowsWorkflow wf_articleNew for creating a new article without form. It can be called from portal or client apps.

•Save activity failed to read source FTP file if received only as url, not binary: When receiving the source files (ActivityData) only as urls (and not as binary stream), the Save activity failed to read the source FTP files because it did not use the network credentials (anonymous FTP login). It could occur when the FTP files were read with a Fetch activity having List="true" attribute. (available also in 1.4.1556.2)

•There is a new sequential activity "UnSpike" that undeletes objects - see documentation at http://tech.teradp.com/tech/html/gn4/docs/VSdoc/frlrfTeraDPGN4WorkflowActivityUnspikeClassTopic.html (available also in 1.4.1556.2).

•When calling a custom dll using the Code activity, no error message was displayed if the method's name or parameters were wrong.

•Changed the wf_import_tark to schedule the regeneration of thumbnails and previews of image and pages. New WindowsWorkflows are  wf_CreatePreviewThumbnailDocumentIds and wf_CreatePreviewThumbnailImageIds. They expect the objects ids as parameter, and for document objects, the variant PDF_[Smallest File Size] must exists.

•Added the WindowsWorkflow wf_CopyUserConfig, called from the portal users management page, that allows copying the relevant user configs to other users.

•When cropping a big image, the standard crop worfklow creates a small variant to be displayed in the crop dialog and saves it into the original image. This could raise an error if the user has no permissions to write on the image ('Content' attributes). To avoid this error, now the standard crop worflow displays always the already existing 'image.preview' image in the crop dialog. Only if the preview is missing, then the WindowsWorkflow creates a new variant like before. (available also in 1.4.1556.2).

•The 'Object reference not set to an instance of an object' exception occured when the Code activity called a method having an 'out int' parameter.

•In the WindowsWorkflow panel of GN4 clients, the 'SearchForm' activity did not show the result objects if they didn't derive from the 'folderObject' type. Now, also the objects that don't derive from the 'folderObject' type (like 'extractDest') are correctly displayed by the 'SearchForm' activity.

•Windows clients: the Upload activity ignored the MinFileCount property. In clients WindowsWorkflow, besides the 'MaxFileCount' property, now the 'Upload' activity supports the 'MinFileCount' property too (the web portal already did). If the 'MinFileCount' property of the 'Upload' activity is not specified, its default value is 1. If the 'MinFileCount' property is explicitly set to 0, then the uploaded files are optional.

•Crash binding the To property of the Save activity to a WindowsWorkflow parameter like this:

<Save

x:Name="saveZip"

Data=" . . . "

To='{wf:ActivityBind mainWorkflow, Path=ParValue["outFilePath"]}'/>

caused a crash when executing the workflow. Now fixed.

•"LoadData" activity: when passing multiple data ids in the "DataIds" property and corresponding multiple source paths in the "SrcPaths" property the resulting "DataOut" list contained the correctly loaded data but with random source paths - e.g. passing 345 and 346 as data ids and A.jpg and B.jpg as the source paths could result in the data with id 345 associated with either A.jpg or B.jpg - instead than always A.jpg as expected. Now fixed.

•The "TransformXml" activity failed with an invalid cast exception if it had no XSLT and its "XmlIn" property was bound to the "XmlOut" property of a "XmlReplicator" activity. Now fixed.

•The WindowsWorkflow importImg was not deleting existing clipping path for images submitted again without it