Activities of "EngincanV"

Is the app-pro template with version 4.4.0-rc.1 for commercial user released? I am still cannot download a start template code with the 4.4.0-rc.1

Hi @trendline, yes it's released. Could you specify the version (--version 4.4.0-rc.1) for downloading a startup template if you are using the CLI? (If you use Suite you can check the preview box while creating a project) Because otherwise, it might be using a cached template (with version 4.3.3)

Hi support,

When I try to go to My profile address after logging in to the commercial.abp.io, I get an "Internal Server Error" error.

Hi @gvnuysal, thanks for reporting this issue. It will be fixed.

Hi @serdar,

• Can you change your proxy-server call as in the below screenshot? (It should be products instead of product)

• Because Suite generates app service for Product as ProductsAppService.

Hi, I need the steps to reproduce this problem. Can you also specify your version?

• Hi @VivekKoppula, your HttpRequest Activity's path must start with " / ".
• So your path must be /hello-welcome instead of hello-welcome.

• After publishing the workflow, you should be able to navigate to the route (/hello-welcome) and view the output that you've defined.

• You can import the following JSON to create the workflow from the Elsa Dashboard.

{
  "$id": "1",
  "definitionId": "b165f4cb25be4b6c8cfb660d859673d7",
  "versionId": "6a49a7f97881419d8c75dd0f4a4fe76a",
  "name": "support",
  "displayName": "support",
  "version": 1,
  "variables": {
    "$id": "2",
    "data": {}
  },
  "customAttributes": {
    "$id": "3",
    "data": {}
  },
  "isSingleton": false,
  "persistenceBehavior": "WorkflowBurst",
  "deleteCompletedInstances": false,
  "isPublished": true,
  "isLatest": true,
  "activities": [
    {
      "$id": "4",
      "activityId": "9db82643-3f96-4b7d-bef0-ca743f97f63d",
      "type": "HttpEndpoint",
      "displayName": "HTTP Endpoint",
      "persistWorkflow": false,
      "loadWorkflowContext": false,
      "saveWorkflowContext": false,
      "persistOutput": false,
      "properties": [
        {
          "$id": "5",
          "name": "Path",
          "expressions": {
            "$id": "6",
            "Literal": "/hello-welcome"
          }
        },
        {
          "$id": "7",
          "name": "Methods",
          "expressions": {
            "$id": "8",
            "Json": "[\"GET\"]"
          }
        },
        {
          "$id": "9",
          "name": "ReadContent",
          "expressions": {
            "$id": "10"
          }
        },
        {
          "$id": "11",
          "name": "TargetType",
          "expressions": {
            "$id": "12"
          }
        }
      ]
    },
    {
      "$id": "13",
      "activityId": "72503314-05d2-46d2-9c41-08f6d15782d9",
      "type": "WriteHttpResponse",
      "displayName": "HTTP Response",
      "persistWorkflow": false,
      "loadWorkflowContext": false,
      "saveWorkflowContext": false,
      "persistOutput": false,
      "properties": [
        {
          "$id": "14",
          "name": "StatusCode",
          "expressions": {
            "$id": "15"
          }
        },
        {
          "$id": "16",
          "name": "Content",
          "expressions": {
            "$id": "17",
            "Literal": "Hello world from /hello-welcome."
          }
        },
        {
          "$id": "18",
          "name": "ContentType",
          "expressions": {
            "$id": "19"
          }
        }
      ]
    }
  ],
  "connections": [
    {
      "$id": "20",
      "sourceActivityId": "9db82643-3f96-4b7d-bef0-ca743f97f63d",
      "targetActivityId": "72503314-05d2-46d2-9c41-08f6d15782d9",
      "outcome": "Done"
    }
  ],
  "id": "6a49a7f97881419d8c75dd0f4a4fe76a"
}

Hi @VivekKoppula, if you update the path of the HttpRequest Activity like /elsa-hello-world, you should be able to navigate the route and display the output.

P.S. There is already a defined path with that name (/elsa-hello-world), so you should define a different path (it should be relative-path. E.g. /hello-world), otherwise it will give an error.

Hi @Neozzz, as stated here if you add an app service method named GetDocumentAsync it will calculates as /api/app/file/{id}/document but if you would specified it like GetAsync it would have transformed it into /api/app/file/{id}.

• If you want to customize your route calculation, you can check here.

Hi @gvnuysal, CreateInputFile class has been replaced with CreateFileInputWithStream class.

public class CreateFileInputWithStream
{
    [Required]
    [DynamicStringLength(typeof(FileDescriptorConsts), nameof(FileDescriptorConsts.MaxNameLength))]
    public string Name { get; set; }

    public IRemoteStreamContent File { get; set; }
}

So your code can be changed like below,

CreateFileInputWithStream blobInput = new CreateFileInputWithStream
{
    File = input.Content,
    Name = input.Name
};

Hi again @Leonardo.Willrich, can you change your OnReadHandler method as below?

protected async Task OnReadHandler(GridReadEventArgs args)
{
    LastRequest = args.Request;
    List<IFilterDescriptor> filters = null;
    if (LastRequest.Filters.Any())
    {
        var filterDescriptors = LastRequest.Filters.SelectMemberDescriptors().ToList();
        if (filterDescriptors.Any())
        {
            filters = new List<IFilterDescriptor>();
            foreach (var filter in filterDescriptors)
            {
                filters.Add(new FilterDescriptor { Member = filter.Member, Operator = filter.Operator, Value = filter.Value });
            }
         }
    }

    LastRequest.Filters = filters;
    await LoadData();
}

• FilterDescriptor class has a variable named MemberType and wrong value is assigned this variable automattically.

If it does not work for you, please let me know. If it works you can close the question.

Hi @Leonardo.Willrich, I am checking.