This article describes how to read Out arguments of a Workflow, but when using Workflow Manager 1.0, you don't have access to the workflow running in a host:
http://blogs.msdn.com/b/rjacobs/archive/2009/09/24/wf4-how-to-access-out-arguments.aspx
I have read the following documents about Workflow Manager 1.0
Developers Introduction to Windows Workflow 1.0
Workflow Manager 1.0 Tutorial
How to create a Workflow for Workflow Manager 1.0
What is Workflow Manager 1.0
Installing and configuring Workflow Manager 1.0
I have downloaded and dissected he sample code provided by microsoft, but the information I need is not included.
Workflow Manager 1.0 Samples
All the samples appear to return values using
WorkflowInstance.UserStatus
and set this using a SetUserStatus activity in the workflow, which isn't much use if you want to read the value of an Out argument defined in the workflow itself.
Related
I am currently working on to upgrade dotnet core framework version from 1.0 to 2.1 of an existing product.
The UI of the same is made in Angular which makes service calls to AWS Lambdas (made using dotnet core) for all the requirements. User data is stored in AWS Cognito and every time a service call is made it first gets verified by fetching data from Cognito. This part stopped working after the framework upgrade.
The following lines of code stopped fetching data:
if (!HttpContext.Items.Keys.Contains("APIGatewayRequest"))
{
//Log error
}
HttpContext.Items["APIGatewayRequest"] as APIGatewayProxyRequest;
Custom api gateway authorizer is used for Cognito and also HttpContext is used inside a controller.
The following image shows the Request.HttpContext structure for me:
Any information around this issue will be great.
Finally, after trying desperately for a couple of days, I got the resolution. In the newer version of DotNet Core the value of the HttpContext key got changed from "APIGatewayRequest" to "LambdaRequestObject" causing all the pain. And the code was using the value directly from a constant declared inside the project and was not using the constant "AbstractAspNetCoreFunction.LAMBDA_REQUEST_OBJECT" provided by the framework.
TFS URL : http://tfs.{my-organization-name}.com:8080/tfs/
TFS : On Premise
Version : TFS 2018 Update 2
Query: I want to use #CurrentIteration('[Project]/Team') in TFS Query, which I want to run from REST APIs. e.g. #CurrentIteration(‘[MyProject]/MyTeam’) (I have always only one team associated with one project, not more than one)
Issue: In TFS query, I have defined #CurrentIteration to get iterations dynamically but, as per their protocols, this variable will only work from their Web Portal and not from REST APIs.
Resolution: If we add team name as a parameter in braces with #CurrentIteration then, that will work for REST APIs and Web Portal both. But now when I add team as parameter I am getting below error in TFS.
Error: The ability of the #CurrentIteration macro to accept a team is disabled.
(I did research on it and it looks like, this ability might be available only in Azure DevOps Server 2019 and later version. I am not sure about this. Need help here.)
Reference link1
Reference link2
Reference link3
Can anyone have any idea why i am getting this error? Where can i have option to enable this ability in my on premise TFS web portal?
As you mentioned, this feature will be avaiable only on TFS 2019.
See the official featuers timeline here:
Clarify query iteration schedules with the #CurrentIteration Team parameter: 2019
Where I can find example for workflow implementation? Actually we are not able to attach workflow definition to a Page or Component. We have created new Workflow definition for Page and Component when we open a page and go to Workflow tab it is showing "Approval Status: Undefined"
We recently upgraded from Tridion 5.3 to Tridion 2011 SP1, we have executed the step mentioned in Upgrade manual "Upgrading existing default Workflow Process
Definitions"
As per my understanding under workflow tab we should be able to select workflow definition to be followed by Page or Component
For Pages, Workflow Processes are attached to Structure Groups (you'll be able to select the Process Definition in the Workflow Tab of the Structure Group). When attached to a SG, any page that you create or edit in that SG will start the workflow for that item. Note that Structure Group's do not inherit this setting, so every SG you'll have to attach the process to.
For Components, Workflow Processes are attached to the Schema (you'll be able to select the Process Definition in the Workflow Tab of the Schema). When a Schema has a workflow, any Component that is created or edited using that schema will be put into a workflow.
Note that child Publications won't automatically have Components and Pages kick into workflow. For example, if your schemas with attached Process Definitions are at the 010 level, and your components are at the 020 level, you'll have to go to the Workflow Tab in the Publication properties of your 020 level and make sure to check "Enable Workflow Process Associations in Shared Schemas and Structure Groups".
Hope that helps!
Having trouble with automatic decisions in Tridion 2011 SP1.
I have an auto-decision item that go down one of two paths (one to a manual decision and the other to a manual activity). Screenshot attached.
What I need to do is analyse the permissions of the user that submits the first step in the workflow and automatically move the workflow down the correct path.
I am using an event handler for the AutomaticAssignActivity (tested successfully with event log writes) and have found in the API how to finish the activity but there's not overload for assigning the next activity.
I found this post an interesting read and tried to implement the CoreServiceSession and SessionAwareCoreServiceClient but each time the code tries to load the core service I receive the following error: Could not load file or assembly 'Tridion.ContentManager.CoreService.Client, Version=6.1.0.996, Culture=neutral, PublicKeyToken=ddfc895746e5ee6b' or one of its dependencies. The system cannot find the file specified.
I am using the core service in my web layer for some minor content generation but it doesn't want to work from within the events system. What am I doing wrong? My events system DLL is in the Tridion bin folder where Tridion.ContentManager.CoreService.Client.dll sits.
Any help appreciated :)
Note that if you are developing an Event handler, you should better use the TOM.NET API (it is the preferred API for Event System and templating developments)
For all the rest, use Core Service
If you want to use core service, you can create a .NET DLL and then call it from your automated activity. This thread has some good information about it:
Which API can I use for writing SDL Tridion workflow activities?
We are using SourceForge Enterprise Edition 4.4 in one of our project.
My question is, in CollabNet SFEE (SourceForge Enterprise Edition 4.4), how will we get attachments associated with an Artifacts Using SFEE SOAP API?
We have made our own .net 2.0 client. We are not using .net SDK provided by Collabnet,
If you commit with a message you can add "[artf1000]" (where artf1000 is your artifact number) to the beginning or end of your commit message. Then it will associate to that artifact you can also do this with documents using doc1000, to get the id of the item you can use the URL it is what is after the http://sfeeserver/sf/go/.
Documents and artifacts are the only item I have used this for so I am not sure about other types of links, but I would imagine anything that has a /go/ID could be referenced by the ID.
ie:
http://sfeeserver/sf/go/artf1000
http://sfeeserver/sf/go/doc1000
Edited to add:
I have seemingly successfully tried this with releases, tasks, and discussions as well.
You can cheat a little bit and have a look at the scripts from SFEE. Log into your SFEE via SSH and take a look at the following script:
/usr/local/sourceforge/sourceforge_home/integration/post-commit.py
Maybe it helps...