Workflows

Build 1501 on 14/Nov/2017  This topic last edited on: 3/Dec/2015, at 16:33

[44] Workflows: newTask does not copy all event's attributes

GN4-3756

The newTask workflow was not correctly copying all the selected event's attributes.

Now fixed. Re-import the config wf_newTask.

Modified date: 23/11/2015 11:40:57 - P4 Changelist: 79622 - From build: main.2732.x (T)

 

 

[32] Workflows: interactive archive for selected objects

GN4-3636

A new workflow, wf_archiveObjectsInteractive, allows interactive archiving of objects not linked to pages/documents or to articles linked to pages/documents.
User is prompted to select publication and date to be used in the correspondant fields of the archived elements.
New file:
wf_archiveObjectsInteractive
Modified Files:
xsl_ImportDocumentsAudio.xml
xsl_ImportDocumentsImage.xml
xsl_ImportDocumentsStory.xml
xsl_ImportDocumentsVideo.xml

Modified date: 14/10/2015 18:13:02 - P4 Changelist: 78876 - From build: 2.2.2692.x (T)

 

[88] GN4: workflow to copy article to multiple titles

GN4-3528

Added a sample workflow to copy one or more selected articles to multiple target titles, selected in a dialog.
The copied articles are renamed as [original name]_[target title] and moved in a Folder /[target title]/Pool
If the target folder does not exist, the copy will not be done.
Available from i4, under article Send menu, and Ted/Fred

Modified date: 14/09/2015 16:05:57 - P4 Changelist: 78515 - From build: 2.2.2662.x (T)

 

[98] Workflow: crop with watermark saves the watermarked pic to folder

GN4-3470

When setting the watermark path in the wf_Crop.xml, now the watermark is applied only to the image object created in the database.
Vice versa, the output image (in the file system path defined in the extract destination) is generated always without the watermark.
This is because the watermark, in the editorial cropping, is used as a simple label for the users which creates the page layout.

Modified date: 08/09/2015 18:11:41 - P4 Changelist: 78441 - From build: 2.2.2656.x (T)

 

[99] Workflow: split the crop workflow to execute the transform activities in background

GN4-3473

In cropping workflow, now it is possible to schedule the cropping operation.
In fact, after clicking 'Next' button in the cropping dialog, the actual crop of the picture could be a bit slow if a watermark is applied.
The crop process has been splitted into two workflows (wf_Crop.xml and wf_CropBatch.xml). These workflows must be reimported into the database.
The wf_Crop.xml workflow only shows the crop dialog; then, it calls the wf_CropBatch.xml workflow, which actually crops the picture.
 
The wf_Crop.xml workflow accepts a new parameter, called 'async': if 'async' is 'false' (default) or missing, then the cropping operation is executed into the same session, just like before.
Vice versa, if 'async' is 'true', the cropping operation is scheduled as Back4 task and the workfow panel is closed immediately, without waiting the creation of the cropped image.
At the beginning of the workflow files, there is the list of all the configurable parameters and their descriptions.
 
When adding an image to an article or dropping it onto a placeholder in page, Fred4 needs the id of the new cropped image. The problem is: if the cropping is asynchronous, wf_Crop.xml cannot wait the end of the Back4 task to retrieve the id of the cropped image. In this case, wf_Crop.xml first creates an empty image into the database, so to have immediately a valid id. This empty image is then replaced by the scheduled workflow wf_CropBatch.xml, which generates the final cropped image.

Modified date: 08/09/2015 18:11:41 - P4 Changelist: 78441 - From build: 2.2.2656.x (T)

 

[192] Workflows: show final log even if an object is spiked during the workflow execution

GN4-3416

When a workfow creates/modifies GN4 objects, the final log was something like this:
"Created 3 story ('myStory1', 'myStory2', 'myStory3')"
If some of these new objects were spiked by another process during the workflow execution, then the final log was not displayed and the following error occurred: "Object(s) with id ... have been spiked (ERR0229)".
Now, the workflow shows always the final log, specifying the ids of the spiked objects:
"Created 1 story ('myStory1'). 2 Already spiked object(s) (1234, 8901)"

Modified date: 22/07/2015 14:22:38 - P4 Changelist: 77850 - From build: 2.2.2608.x (T)

 

[209] Workflows: initialization of attributes in ObjectUI

GN4-3389

Into the workflow dialog of GNPortal and i4, the initMode="Value" flag of the ObjectUI's attribute didn't work: now fixed.
Note that the same ObjectUI already worked fine into the workflow dialog of clients and into the GNPortal editing dialog (non workflow).

Modified date: 15/07/2015 11:15:23 - P4 Changelist: 77720 - From build: 2.2.2601.x (T)