Semantic Check results for FADs in ARIS CONNECT Designer

Hello,

We raised ticket#5381177 and were advised to log a feature request for the topic.

Currently, in the modelling screen of ARIS CONNECT Designer, if semantic checks are run on an EPC model which has FADs for objects, in the results pane ( at the bottom of screen), the sematic errors from FADs are not displayed. We were advised in the ticket that this is by design and is done to prevent multiple tabs from opening and prevent crashing of the browser ;to include FADs Sem Checks should be executed in Repository.

Like on thick clients, when users are on CONNECT Designer, they would like to run the Semantic Check from the designer interface (instead of navigating to groups / Repository) so that they can see the errors on the modelling screen in a single view and fix them appropriately. Running semantic checks from repository and then opening models is not very intuitive as you have to move back and forth in tabs plus it doesn’t show visually the errors in models.

We agree that opening lots of models may lead to issues, however we do think that semantic check issues can be highlighted without opening FADs in new tabs ( we already have an option to run sem check for models +FADs without opening them in thick client) . Hence, we think below features would make a lot of sense:
1. If the object ( whose FAD has errors) can be marked like it is done currently (red cross) for issues with semantic check for the objects
2. The table which lists out errors should include errors related to underlying FADs (if applicable)

If these features are available, users can then open only the individual FADs where semantic check fails and it would greatly increase user experience.

Also, currently it is confusing for users as they may get a false positive message that no error exists ( even though FADs may have issues). This is further more problematic if the semantic checks are configured as a prerequisite for APG publishing workflows.The system tells you that there are no issues, but when you start the workflow, you find out that semantic check fails or worse that the FADs are excluded from semantic checks and are published anyways (like on our environment currently).

This is when we reached out to SAG Colleagues ( Dietmar Durek), as we always had the understanding that the FADs are bundled with EPCs whenever semantic checks are run, and Dietmar decided to raise an incident as that was his understanding as well.

We have also been hearing that CONNECT Designer functionalities are being enhanced to match those of thick clients, and we would strongly urge you to address the functionality highlighted in this incident somehow.

Thanks.