Elsa Workflow issues after updating to abp 7.1 #4920

5 Answer(s)

• 

  0

  liangshiwei created one year ago

  Support Team Fullstack Developer

  Hi,

  You can check this: https://github.com/abpframework/abp/issues/16201

  Save Cancel
• 

  0

  neethucp created one year ago

  Hi, we have added the automapping for elsa dashboard manually. And the dashboard issue is sorted. But major issue we are facing is with workflow instance not getting updated. Following is the code in elsa to save the instance. On debugging we found that entity is in detached state and hence change tracking not working for update. https://github.com/elsa-workflows/elsa-core/blob/392b4509217bf1c2b8c90a4ed669bc71ab45f4ab/src/persistence/Elsa.Persistence.EntityFramework/Elsa.Persistence.EntityFramework.Core/Stores/EntityFrameworkStore.cs

  Save Cancel
• 

  0

  liangshiwei created one year ago

  Support Team Fullstack Developer

  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.

  There is no breaking changes from 7.0 to 7.1, can you reproduce this issue with a new project and share it with me? shiwei.liang@volosoft.com I will check it.

  Save Cancel
• 

  0

  liangshiwei created one year ago

  Support Team Fullstack Developer

  Hi,

  It's a bug we will fix it in the patch version.

  You can try this:

  public override void ConfigureServices(ServiceConfigurationContext context)
  {
      context.Services.AddSingleton<AutoMapper.IConfigurationProvider>(sp =>
      {
          using (var scope = sp.CreateScope())
          {
              var options = scope.ServiceProvider.GetRequiredService<IOptions<AbpAutoMapperOptions>>().Value;
  
              var mapperConfigurationExpression = sp.GetRequiredService<IOptions<MapperConfigurationExpression>>().Value;
              var autoMapperConfigurationContext = new AbpAutoMapperConfigurationContext(mapperConfigurationExpression, scope.ServiceProvider);
  
              foreach (var configurator in options.Configurators)
              {
                  configurator(autoMapperConfigurationContext);
              }
              var mapperConfiguration = new MapperConfiguration(mapperConfigurationExpression);
  
              foreach (var profileType in options.ValidatingProfiles)
              {
                  mapperConfiguration.Internal().AssertConfigurationIsValid(((Profile)Activator.CreateInstance(profileType)).ProfileName);
              }
  
              return mapperConfiguration;
          }
      });
  
      context.Services.AddTransient<IMapper>(sp => sp.GetRequiredService<AutoMapper.IConfigurationProvider>().CreateMapper(sp.GetService));
  
      context.Services.AddTransient<MyMapperAccessor>(sp => new MyMapperAccessor()
      {
          Mapper = sp.GetRequiredService<IMapper>()
      });
      context.Services.AddTransient<IMapperAccessor>(provider => provider.GetRequiredService<MyMapperAccessor>());
      
  }
  
  public class MyMapperAccessor : IMapperAccessor
  {
      public IMapper Mapper { get; set; }
  }
  

  Save Cancel
• 

  0

  neethucp created one year ago

  That fixed the issue. Thank you.

  Save Cancel