Workflows

The images sitting in a folder with @doNotArchive='true' were not skipped during archiving. The check was done only inside the images linked to a document, but not for images linked to an article.
Now fixed: if an editorial image is into a folder with @doNotArchive='true', then it is ignored by the archiving process.

Modified date: 14/06/2016 18:07:36 - P4 Changelist: 82551 - From build: main.2936.x (T)

Now the printing workflows can optionally set a specific workstate to the pages successfully printed.
This way, the user can check visually the pages that have been printed without errors.
It is now possible to define into the printQueue object both the success workstate ('successWorkstateName' parameter) and the error workstate ('errorWorkstateName' parameter).
The printing workflow sets the workstate of the page to the success workstate if the page is printed without errors: otherwise, it sets the workstate to the error workstate.
If the workstate names are not defined into the printQueue, then the printing workflow looks for the 'printSuccessWorkstateName' and 'printErrorWorkstateName' user parameters.
 
You must reimport the following workflow (using 'cmd4 config -in ...'):

..\config\global\gn4\wf_PrintTemplate.xml

 
and the following object (using 'cmd4 import -in ...')

..\config\data\gn4\dataSrcTemplate_GeneratePDF.xml

 
 
You can optionally reimport the following objects (they contain the definition of the workstate parameter):

 
..\config\data\gn4\securityScope_Default.xml
..\config\data\gn4\printTemplate_PrintFile.xml
..\config\data\gn4\printTemplate_Variant.xml
..\config\data\gn4\printTemplate_VariantArchive.xml

Modified date: 10/06/2016 17:21:07 - P4 Changelist: 82502 - From build: main.2932.x

Moved all the calls to Facebook from the GNFacebookClient.dll into the 'publishWF' workflow of the publishing template 'pubTemplateFacebook.xml'.
This allows to easily debug the Facebook responses and to use the future Facebook functionalities without recompiling the code.
Now the publishing workflow uses only the Facebook.dll. It doesn't use the GNFacebookClient.dll library anymore.
Note that the GNFacebookClient.dll library is still used by the GetFacebookAccessToken.exe utility.
The 'pubTemplateFacebook.xml' publishing template must be reimported.

Modified date: 16/05/2016 12:24:18 - P4 Changelist: 82122 - From build: main.2907.x (T)

[1] Workflow: wf_archiveToday and wf_archive cannot handle more than one edition

GN4-4305

The wf_ArchiveToday.xml workflow passed more edition ids to the wf_Archive.xml workflow all at once, but wf_Archive.xml can manage only one edition at a time.
Now fixed: wf_ArchiveToday.xml calls multiple times the wf_Archive.xml workflow, passing only one edition id at a time.
The wf_ArchiveToday.xml and wf_Archive.xml workflows must be reimported.

Modified date: 26/04/2016 17:31:24 - P4 Changelist: 81875 - From build: main.2887.x

[75] Workflow: the versions of the story are empty when archiving an edition

GN4-4228

When archiving an edition, the text versions were missing into the generated stories.
This was because the xml navigator had an internal limit (set to 18 levels) which is generally enough to retrieve all the needed data.
Note that this internal limit is needed to manage eventual circular references during the navigation.
However, navigating a page with both the 'references' and 'versions' options, deeply to the textual content of a version of the body, consumes more than 18 levels.
In fact, the applied XPath is something like this:

gn4:page/nav:referencing/nav:referencingBy[@attrName='linkObject.pageLayers.pageRef']/nav:refs/nav:refObject/gn4:article/nav:versions/nav:version/nav:obj/
gn4:article/gn4:txts/gn4:body/nav:versions/nav:version/nav:obj/gn4:body/gn4:tText

 
Now fixed: modified the wf_Archive.xml workflow to increase the internal limit of the navigator.
Note that, into the server, the navigation limit can be increased only in particular cases: when we are using both the 'references' and 'versions' options into an 'unlimited' navigation driven by the xslt transformation.
The wf_Archive.xml workflow and xsl_Archive.xslt stylesheet must be reimported.

Modified date: 04/04/2016 17:42:17 - P4 Changelist: 81525 - From build: main.2865.x (T)

[86] Workflow: crop does not work using Windows Authentication

GN4-4205

When using the Windows Authentication, the crop dialog in Fred4 did not display any picture.
This was because the GN4 volumes had the credentials set, but the workflow ignored them.
Now fixed: the crop workflow reads the GN4 volumes using the correct credentials.

Modified date: 31/03/2016 18:34:48 - P4 Changelist: 81482 - From build: main.2861.x (T)

[96] Workflows: implement the MessageDialog activity in clients

GN4-4155

Implemented the '''MessageDialog''' interactive workflow activity in the Windows client applications that allows a simple message to be presented to the users along with optional options using either checkbox or radio button controls. For example:
dim messageDialog as new MessageDialog(Context) with {
.Message = "This is the message displayed at the top"
}
 
dim messageDialogResult as MessageDialogResult = Await messageDialog.Do()
 
messageDialog = new MessageDialog(Context) with {
.Message = "A single checkbox option"
}
 
messageDialog.OptionMessages.Add(new MessageDialogOption("This is the single checkbox option"))
 
messageDialogResult = Await messageDialog.Do()
 
if messageDialogResult.IsChecked then
' do this if checked
else
' do this if unchecked
end if
See the forum topic http://forum.teradp.com/topic.asp?TOPIC_ID=900 for examples.

Modified date: 29/03/2016 18:15:58 - P4 Changelist: 81446 - From build: main.2859.x

[97] Workflows: print pages from inside a workflow

GN4-4191

In GN4 there are two different types of printing: client and server.
In client printing, Fred4 opens the pages and sends their data to the server (../edo.ashx?cmd=Print); then the server generates the PDF.
In server printing, Fred4 sends only the page ids to the server (../edo.ashx?cmd=ServerPrint); then the server opens the pages and generates the PDF.
Note that both the printing types, client and server, can be synchronous or asynchronous, according to the used printing presets.
Because printing many pages could take several minutes, it would be useful to print pages directly inside a workflow (that is, without calling the ../edo.ashx?cmd=ServerPrint REST method).
For this purpose, the edfn:serverPrint() method has been added to the editorial XSLT extensions.
It is possible to call the edfn:serverPrint() method from inside a workflow applying a XSLT stylesheet; it accepts the same parameters than the ../edo.ashx?cmd=ServerPrint REST method.
Created a new workflow, called wf_PrintEdition.xml, which receives the id of an edition and the name (or the id) of the printing preset to use. This workflow calls the edfn:serverPrint() extension and prints all the pages of the edition using the input printing preset.
Note that, into the workflow, you can specify the printing options (if needed) and the Tracy's options.
The wf_PrintEdition.xml workflow can be executed from srv4, or scheduled in Back4; for example:

srv4 wf PrintEdition -ids 12345 -pars "configName:PDF File;"

Modified date: 29/03/2016 17:02:27 - P4 Changelist: 81442 - From build: main.2859.x

[131] Workflows: importing .doc creates useless tags in database

GN4-4149

In GN4, when importing an old Microsoft Word (.doc) document, the text was imported into the database as html ('story.xmlText' attribute), but the html tag was wrapped by the useless 'root' and 'richTextHtml' tags. Now fixed: the useless tags have been removed.
The workflow wf_ImportActivityData.xml must be reimported.

Modified date: 14/03/2016 15:08:13 - P4 Changelist: 81252 - From build: main.2844.x (T)

[191] Workflows: implement custom interactive activity

GN4-2588

Added the '''MessageDialog''' interactive workflow activity that allows a simple message to be presented to the users along with optional options using either checkbox or radio button controls. For example:
dim messageDialog as new MessageDialog(Context) with {
.Message = "This is the message displayed at the top"
}
 
dim messageDialogResult as MessageDialogResult = Await messageDialog.Do()
 
messageDialog = new MessageDialog(Context) with {
.Message = "A single checkbox option"
}
 
messageDialog.OptionMessages.Add(new MessageDialogOption("This is the single checkbox option"))
 
messageDialogResult = Await messageDialog.Do()
 
if messageDialogResult.IsChecked then
' do this if checked
else
' do this if unchecked
end if
See the forum topic http://forum.teradp.com/topic.asp?TOPIC_ID=900 for examples.

Modified date: 23/02/2016 16:54:06 - P4 Changelist: 80945 - From build: main.2824.x (T)

[226] Workflows: length out of range error for article.plainText

GN4-4022

When I4 (or a Back4 queue) created an article with text longer than 100000 characters, Ted4 was not able to open that article and the 'article.plainText: length out of range' error occurred.
Note that 'article.plainText' is a computed attribute being truncated to maximum 100000 characters.
The problem occurred only using the code workflows (not with old windows workflows).
This was because the article's texts are read using the LoadXml activity; this activity uses the XDocument.Load() .NET method, which seems to normalize the '\n\r' end-of-line characters to '\n'.
These end-of-lines changes corrupt in some way the counting of characters of the unicode string.
Now fixed: modified the LoadXml activity to use the XmlDocument class instead of the XDocument class. 
Note that the 'srv4 recompute' command fixes the corrupted articles.

Modified date: 16/02/2016 14:05:25 - P4 Changelist: 80798 - From build: main.2817.x (T)

[264] Workflows: copy authors from image to img

GN4-3923

The wf_CropBatch.xml workflow was not copying the authors field to the editorial image.
Now fixed: the metadata are correctly copied from the source image (editorial or wire) to the cropped one.

Modified date: 01/02/2016 18:26:14 - P4 Changelist: 80579 - From build: main.2802.x (T)

[299] Workflows: wftest solution cannot be compiled

GN4-3913

In WFTest.zip daily archive, fixed the compilation of the WorkflowTesterExpress and WFUtilsTester projects.
Note that the compilation's platform (x86 or x64) must match the platform of the .dll stored into the \bin folder.

Modified date: 22/01/2016 15:09:12 - P4 Changelist: 80408 - From build: main.2792.x (T)