Skip to main content

Workflow FinishActivity

Image
By
Where you ever annoyed with the ActivityFinish class? Namely, that second parameter nextAssignee of type Trustee of the constructor?

The constructor signature is the following:

public ActivityFinish(string message, Trustee nextAssignee, Session session);

So what do I pass as nextAssignee? Figuring that out is not easy... Luckily though, you can simply pass null for the assignee and Tridion will then use the user/group that is defined in the Activity Definition (in the Workflow Visio diagram).

What if I want to properly assign a nextAssignee? How do I figure out who the next assignee should be? Well, one way I used in the past was to identify the last manual Activity (thus not automatic, because they are performed by the implicit Tridion user as defined in the SDL Tridion Content Manager MMC snap-in / Workflow settings / Automatic Trustee ID). Then I used this Trustee for the ActivityFinish.

Alternatively, as shown by the code-below, I identify the next activity, then take its implicit assignee and use that:

String lastManualActivityMessage = GetLastManualActivityMessage();
ActivityDefinition nextActivityDefinition = GetNextActivityDefinition();
ActivityInstance activityInstance = CurrentWorkItem.Activity as ActivityInstance;
Trustee nextActivityAssignee = null;

if (nextActivityDefinition == null) { // last activity
    Logger.Info("FinishActivityHandler: This '{0}' is the last activity in the Workflow",
        Info.ActivityDefinitionTitle);
} else { // there is next activity
    nextActivityAssignee = nextActivityDefinition.Assignee;
    if (nextActivityAssignee == null) {
        Logger.Warn("FinishActivityHandler: Cannot find assignee for next activity '{0}'",
            nextActivityDefinition.Title);
    }
}

ActivityFinish activityFinish = new ActivityFinish(lastManualActivityMessage,
    nextActivityAssignee, Util.Session);
activityInstance.Finish(activityFinish);

Some methods above, like GetLastManualActivityMessage(), GetNextActivityDefinition(), will be presented in some next posts.

The code sample above are part of YAWF (Yet Another Workflow Framework).

Labels:

Comments

Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...
2 comments
Read more

Toolkit - Performance

By
This post if part of a series about the File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents performance data that was captured for each major functionality with and without caching Linking, CP Assembler, Component Presentation Factory, Dynamic Content Queries, Model Factory. The data was captured on a 2014 Macbook Pro 15", 16 GB RAM, 2.6 GHz Intel Core i7 running OS X El Capitan. Test methodology: each test was run for 3 minutes and the total number of successful Toolkit API calls was measured. Then the number of calls per second was computed 'with cache' and 'without cache' test runs. Then a cache boost factor was calculated by diving (the number of API calls with cache) / (number of API calls without cache). Each cache test was executed 3 times, with different cache time-to-live values of 1 second, 5 seconds and 0 seconds (eternal cache, no expiration). The rationale is to see what impact different cache expiration/evi...
Post a Comment
Read more

REL Standard Tag Library

By
The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...
2 comments
Read more