I've resolved the issue by configuring UseAbpIdentity in Identity microservices.
Do I need somehow to configure Identity Microservices?
Hi,
I've done everithing according to the elsa-workflow-demo.
The suggestions does not based on last verison of Elsa. I have problems even with db migration generation.
Hi,
This is the LaboratoryServiceDataSeeder which is generated by microservice template DataSeeder:

This one is LabEquipmentDataSeederContributor I've added in order to seed:

If I add the seeding code to LaboratoryServiceDataSeeder when is working properly:
using Abc.LaboratoryService.Entities.LabEquipments;
using Abc.LaboratoryService.Enums;
using Volo.Abp.DependencyInjection;
using Volo.Abp.Domain.Repositories;
namespace Abc.LaboratoryService.Data;
public class LaboratoryServiceDataSeeder(
ILogger<LaboratoryServiceDataSeeder> logger,
IRepository<LabEquipment, Guid> repository,
LabEquipmentManager labEquipmentManager
) : ITransientDependency
{
private readonly ILogger<LaboratoryServiceDataSeeder> _logger = logger;
private readonly IRepository<LabEquipment, Guid> _repository = repository;
private readonly LabEquipmentManager _labEquipmentManager = labEquipmentManager;
public async Task SeedAsync(Guid? tenantId = null)
{
_logger.LogInformation("Seeding data...");
if (await _repository.GetCountAsync() > 0)
return;
await _labEquipmentManager.CreateAsync(
name: "Sysmex XP-300",
isActive: false,
protocol: Protocol.HL7,
connectionType: ConnectionType.TCP,
port: "5000"
);
await _labEquipmentManager.CreateAsync(
name: "Cobas 6000",
isActive: false,
protocol: Protocol.ASTM,
connectionType: ConnectionType.Serial,
port: "COM3"
);
await _labEquipmentManager.CreateAsync(
name: "Mindray BC-2800",
isActive: false,
protocol: Protocol.HL7,
connectionType: ConnectionType.TCP,
port: "6000"
);
}
}
Hi,
Everything is configured properly, I consider that is an error on discovering IDataSeedContributor.
Hi,
I am using en, not en-GB. How did you concluded that I could use it?