Starts in:
2 DAYS
4 HRS
29 MIN
10 SEC
Starts in:
2 D
4 H
29 M
10 S

Activities of "neethucp"

We have integrated elsa workflow to abp project. It was all working fine with abp v7.0.3. But when we updated abp to version 7.1 following issues started happening

  1. Unable to access elsa dashboard api's as automapper mappings configured in elsa package stopped working.
  2. Elsa workflow instances doesn't save properly when updated, as entity change tracking doesn't work. Elsa gets the entity from the database and maps the latest changes to the entity using automapper and then saves the dbcontext. But the entity is in detached state after mapping and hence changes not saved.

Can you please shed some light on what changed with the version 7.1 that might be causing this issue. Elsa is also using .net 7 and automapper version 12.0.0.

  • ABP Framework version: v7.1
  • UI type: Blazor
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • ABP Framework version: v4.4.3
  • UI type: Blazor Server
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

We have a microservice project set up with blazor server front end project. We are trying to send notificatio on status change using signalR. We have created a hub inheriting from AbpHub and followed Microsofot's documentation to connect to hub from blazor server project. We are getting "Antiforgery token validation failed. The required antiforgery cookie ".AspNetCore.Antiforgery.RfvzpqGUp6I" is not present." when hubConnection.StartAsync() is invoked.

Do we have to add any configuration to make this work?

Showing 11 to 12 of 12 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06