I’m exploring ways to utilize Lucid's rule-based conditional formatting to perform quality checks on BPMN diagrams. My goal is to ensure diagrams follow best practices listed below.
Best Practices list:
- Avoid using filler words like "and," "the," or "an" in task names. Task names should be concise, e.g., "Send file" instead of "Send the file."
*My current approach: I’ve created a conditional formatting rule - If the shape type is "activity" and the text contains "the," then apply a custom style to highlight the task.
I’m looking for a similar or better approaches for the below checks as well:
- Ensure pools and swimlanes are appropriately named. They should not be empty or have default names like "Pool" or "Lane."
- Activity Type Assignment: Verify that all activities have an associated activity type (e.g., Manual, Service, User, etc.).
- If a task is automated (i.e., task type is "Service"), there should be a data store tagged to the task.
- Each task should have only one incoming and one outgoing arrow. If multiple incoming arrows are needed, a merging gateway should be used.
I’m curious to know if anyone in the community has experience setting up similar rules in Lucid. Any suggestions or insights on how to improve my approach would be greatly appreciated!
Thanks in advance for your help!
