Good and interesting question! :)

From my understanding there is some idea that the workflows should be able to be fired async (like in a new thread) there’s some setting for this in the co figs. Given this there workflows would not have any access to the current HttpRequest. While this is a concept it does not really work so I’ve always been running in “synchronous” mode.

In this mode you should have access to the HttpContext via HttpContext.Current, which maybe means that you could populate the request body or maybe set a redirect to your controller to serve the file.

This would depend on when in the pipeline the redirect from Forms is set.

Are you following what I’m thinking?

Hi Markus,

Thank you for getting back to me on this.

"HttpContext.Current, which maybe means that you could populate the request body or maybe set a redirect to your controller to serve the file."

So at this point in the workflow it is calling/redirecting to the controller to serve the file, but doesn't.

I tried introducing this to the controller:

 MemoryStream ms;


        //using (streamReader = new StreamReader(System.Web.HttpContext.Current.Request.InputStream))
        using (ms = new MemoryStream())
        {
            using (var document = DocX.Create(ms, DocumentTypes.Document))
            {

                System.Web.HttpContext.Current.Request.InputStream.CopyTo(ms);
                ms.Position = 0;
                using (StreamReader stream = new StreamReader(ms))
                {
                    // Add a title
                    document.InsertParagraph("Adding Custom Properties to a document").FontSize(15d).SpacingAfter(50d).Alignment = Alignment.center;

                    //Add custom properties to document.
                    document.AddCustomProperty(new CustomProperty("CompanyName", "Xceed Software inc."));
                    document.AddCustomProperty(new CustomProperty("Product", "Xceed Words for .NET"));
                    document.AddCustomProperty(new CustomProperty("Address", "3141 Taschereau, Greenfield Park"));
                    document.AddCustomProperty(new CustomProperty("Date", DateTime.Now));

                    // Add a paragraph displaying the number of custom properties.
                    var p = document.InsertParagraph("This document contains ").Append(document.CustomProperties.Count.ToString()).Append(" Custom Properties :");
                    p.SpacingAfter(30);
                    document.Save();

                }

            }
        }

        return File(ms.ToArray(), "application/vnd.openxmlformats-officedocument.wordprocessingml.document", "Test.docx");

I don't think I get it tbh...

Hi!

Are you saying that you've managed to perform a redirect to the controller from the workflow but that the file is not served?

Does the controller work when you hit it directly?

Hi!

Hmm, I'm not a 100% sure that I understand you, but let me try. It feels like we're talking about two things, both how to get the workflow to return a redirect to a controller and how to get the controller to serve a file.

As I understand:

You have another (non Umbraco project) where you have this controller and serving the files works, but you haven't manage to get this working with Umbraco?

What kind of controller are you trying to use? A "RenderMvcController"?

You could use a "regular" controller (inherit the standard mvc Controller-class) and route this.

https://our.umbraco.com/forum/using-umbraco-and-getting-started/101128-need-to-use-standard-mvc-controller

Then, like I wrote, I'm not 100% sure that you can redirect from the workflow to this controller but it might be possible by setting up the HttpContext from your workflow.

Hi,

Thank you for not giving up on me :-)

"You have another (non Umbraco project) where you have this controller and serving the files works, but you haven't manage to get this working with Umbraco?" Yes

"What kind of controller are you trying to use? A "RenderMvcController"?" Yes

"You could use a "regular" controller (inherit the standard mvc Controller-class) and route this. https://our.umbraco.com/forum/using-umbraco-and-getting-started/101128-need-to-use-standard-mvc-controller Then, like I wrote, I'm not 100% sure that you can redirect from the workflow to this controller but it might be possible by setting up the HttpContext from your workflow."

Thank you very much will give that a try..

is working on a reply...