IntentArchitect / Support

A repository dedicated to handling issues and support queries
3 stars 0 forks source link

Issue with custom stereotype not being applied #66

Closed Laura-BSC closed 1 year ago

Laura-BSC commented 1 year ago

Ask a question

I have created a custom module. In the module builder, I have defined a custom elements for the domain designer (Security Role & Security Function). I have added stereotype definitions (SecurityRoleData and SecurityFunctionData) that are always applied to elements of the type 'Security Role' and 'Security Function' respectively. Within the same Intent solution, I have created a test app and when I install the module and add the Security Role or Function to the domain, it adds the stereotype as expected.

I am not trying to use the module in another application. I have installed the same version of the module but the stereotype is not applied, nor can it be manually applied.

Any ideas about what I might have missed?

Module builder: image

Test App: image image

Other application: image image

dandrejvv commented 1 year ago

Hi @Laura-BSC

Did you set the following fields on the Catalyst.Modules.RBAC package? image

You can find Module Settings by clicking on the Catalyst.Modules.RBAC package in your Module Builder: image

Please try that and recompile and reinstall your module and see if the stereotypes show up in your other applications. Hope this helps and let me know if this doesn't solve the problem.

Laura-BSC commented 1 year ago

Hi Dandre,

I have set that on the module settings. I tried to install the module on one of our other projects and it works as expected, so I suspect there is an issue with the project i'm trying to install it to. I'll dig around and see if I can find the cause of the issue

dandrejvv commented 1 year ago

To confirm something else, could you verify that your RBAC module's imodspec file has a metadata section that resembles the following?

<metadata>
    <install target="Domain" src="../intent/TestModule/Intent.Metadata/Module Builder/Catalyst.Modules.RBAC/Catalyst.Modules.RBAC.pkg.config" externalReference="551ef154-873c-403c-b4a1-27a720dfeb84" />
</metadata>
Laura-BSC commented 1 year ago

It does. I played around a bit comparing the differences between the project that the RBAC module stereotypes worked in and the one that didn't. The noticeable difference is the one where it doesn't work makes use of another of our custom modules. It seems that when I install that module and the RBAC module, only the last one to be installed allows the stereotypes to be used. I have another custom module that doesn't cause this issue. I'll troubleshoot further and see if I can figure out what is causing the conflict between the two modules

dandrejvv commented 1 year ago

Hi @Laura-BSC . I see. If you do need one of us to assist in this matter let us know on the other support channel and we can have a call to investigate with you. Would it be ok if then close this Issue?

Laura-BSC commented 1 year ago

Hi Dandre,

I found the issue - some of the objects in the module builder had the same GUIDs. I must have copied things across from the other module as a starting point for the RBAC module or something and it kept the same Ids for the copied elements, so when I installed both modules, they were conflicting with one another

dandrejvv commented 1 year ago

Hi @Laura-BSC , I was about to provide that suggestion but it seems you beat me to it. I'm glad you managed to resolve your issue.