IEventHandler - ISHWorkflow.cBatchWorkflowAction
Technical reference about the cBatchWorkflowAction procedure and configuration
Overview
cBatchWorkflowAction allows you to configure and perform mass workflow actions in a background task.
Algorithm / Process Flow
Provides the functionality to perform a status transition over objects contained in the same group (Publication, MasterDocument) in multiple languages at once.
- Launch RELEASETRANSLATION with eventdata:
- target languages: fr, de, ja, zh, fi, nl
- working language: en
- resolutions: High, Low
- autocompletemode
- doc id
- language card list: <default empty>
- Remaining languages set to de, ja, zh, fi, nl. Calculate/process languages fr, en.
- Launching baseline report for fr, en
- If forceorder is set to 'yes' then the list of language card ids is build in a specific order. Otherwise the object order as available in the baseline report is kept.
- Launch RELEASETRANSLATIONS to perform inbox action, with same EventId and EventData:
- remaining languages: de, ja, zh, fi, nl
- working language: en
- current language: fr
- List of all language card ids of the report
- RemainingCardIds: all except the first performactionbatchsize number of cardIds.
- Back to remaining card Ids
- Back to RemainingLanguages
Configuration options / Parameters
The background process to trigger the cBatchWorkflowAction is configured within the background task configuration which is accessible from the Content Manager web client using
<handler eventType="RELEASETRANSLATIONS">
<scheduler executeSynchronously="false" />
<authorization type="authenticationContext" />
<execution timeout="01:00:00" recoveryGracePeriod="00:10:00" isolationLevel="None" useSingleThreadApartment="true" />
<activator>
<comIEventHandler projectName="ISHWorkflowIso" className="CBatchWorkflowAction">
<configuration>
<parameters>
<parameter name="performaction" type="value">Change2Released</parameter>
<parameter name="performactionbatchsize" type="value">500</parameter>
<parameter name="forceorder" type="value">yes</parameter>
</parameters>
</configuration>
</comIEventHandler>
</activator>
<errorHandler maximumRetries="3">
<actions>
<!-- IEventHandler_DoRequest doesn't throw an exception...so, errors can only be time outs or errors during the creation of the COM+ dll -->
<add errorNumber="*" action="Retry" delay="00:01:00" />
</actions>
</errorHandler>
</handler>
- performaction
- The inbox action to be performed.
- performactionbatchsize
- Batch size of the objects on which the performaction will be performed.
- forceorder
-
Indicator to force a specific objecttype order while releasing the objects. If set to 'yes' the following order is applied: ISHMasterDoc, ISHModule, ISHLibrary, ISHIllustration, ISHTemplate.
Allowed values are: yes / no
Usage / Examples
Typical usage of this functionality includes the Out of the Box available function
- RELEASETRANSLATIONS
Revision information
Since SDL Trisoft 2009 (patch 3.8.7) the ISHWorkflow and ISHWorkflowIso variant are available.
Since SDL LiveContent Architect 2014 (InfoShare 11.0.0), the configuration is moved from InfoShareConfig.xml to the background task configuration.