[BUG] IsSystem property is manditory for Definitions and Instances about elsa-core HOT 1 OPEN

To address the issue where workflow definitions or instances without the "IsSystem" property set are not showing up in Elsa Studio, you should ensure that the property is explicitly set to false for all existing definitions and instances in the database. This is necessary because the behavior has changed with the introduction of the "IsSystem" property in Elsa version 3.1.0 and later.

Since the property was newly introduced, entities that were created before the update may not have this property set, leading to them being filtered out when Elsa Studio tries to list them. By setting "IsSystem" to false, you ensure that these entities are included in the list.

If you have direct access to the database, you can run an update query to set the "IsSystem" property to false for all records where it is not set. If you are using MongoDB as your persistent storage, the query would look something like this:

db.workflowDefinitions.updateMany(
  { "IsSystem": { "$exists": false } },
  { "$set": { "IsSystem": false } }
);

db.workflowInstances.updateMany(
  { "IsSystem": { "$exists": false } },
  { "$set": { "IsSystem": false } }
);

Please replace workflowDefinitions and workflowInstances with the actual collection names in your MongoDB database.

Remember to back up your database before running any update queries to prevent data loss.

If you are not comfortable running database queries or do not have direct access to the database, you may need to contact the Elsa support team or the community for assistance on how to best apply this change to your environment.

This comment was generated by Glime.

from elsa-core.