Weekly feature improvement and bugfix summary

The following feature improvements have been implemented, and bugs fixed in the past week:

Inventory

• Inventory builder now shows best practice prompts to guide you through providing well-crafted prompts that can significantly improve the analysis of uploaded diagrams and images, enabling the inventory builder to accurately extract relevant architectural elements for each fact sheet type.

  

Reports

• Last week, we announced the release of changes to the grouping and color-coding of numeric data in reports, specifically a shift in the color differentiation. We received feedback stating the approach is valuable, but the chosen colors with strong differentiation don't meet expectations. Therefore, we've decided on a timely follow-up release with a compromise of less intense coloring than it is now, but still with more distinction than before. This release will be rolled out to your reports on Wednesday, July 2.

  

Diagrams

• Previously, labels added to data flow interfaces were only visible in "Edit” mode and would disappear when you saved and switched to "View” mode. This issue has been resolved. Labels will now display correctly after you save a diagram.

Automations

• You can now add conditions that evaluate the content of string fields in automations, not just single-selects. To do so, add a "Field value (string)" condition, select the relevant field, and pick an operator (e.g., is, is not, contains, is blank, ...) and set the value. Chain them with your existing triggers and actions to make them even more powerful. Here are some examples that are now possible:

  • Remind the application owners when the fact sheet description is empty or does not contain specific organizational required details.

  • Create a tag or to-do if the functional fit description is empty.

  • Send an email to stakeholders if a GDPR compliance field includes the word "approved".

  

Calculations

• Once again, we've extended the capabilities of calculations. This time, with the possibility of reading lifecycle fields and triggering them daily if any time-based field is used. You can access the lifecycle field with data.<lifecycleFieldName>.<phaseName> (e.g., data.lifecycle.active). Calculations using lifecycle fields run daily for all target fact sheets at 12 AM (midnight) UTC in all workspaces and hosting regions.

Architecture decisions

• You can now add tables to text components in your architecture decisions as a structuring element in workspaces with SAP LeanIX Architecture and Road Map Planning. Many purposes can be realized with it, such as comparisons, timelines, prioritization matrices, dependency tracking, risk assessments, status reporting on decision details, and rationale overview.

  

Transformations

• When planning transformations for suggested SAP solutions of the reference catalog in workspaces with SAP LeanIX Architecture and Road Map Planning, there is now always the option to create new fact sheets, in addition to selecting one of the existing ones.

Documentation

• At the beginning of next week, the documentation will move into its new home at the SAP Help portal, where it will be available in many more languages.