Hello dear forum,
I am looking into changing the symbol palette for our main dB. We are considering an incremental approach rather than a big bang as different EA dimensions have different stakeholders and different volumes of existing models.
However, We have a quite a few customizations in terms of derived symbols with custom graphics which seems to cause problems as they appear to exist outside the two symbol palettes. I also dont want to migrate archived material on a separate dB.
- Is there a way to adress custom symbols to the different palettes?
- Is there a way to disregard the custom graphics when selecting the new palette?
I would like to design new graphics without replacing the old and instead use the palettes to control the appearance of custom graphics.
An example:
From "Capability Configuration", three different symbols have been derived. Each new symbol has been given custom graphics in the same style as the classic palette.
During a transition phase some users will start using new palette. However, custom symbols will still have the classic style. If I replace the custom graphics with the newer style, the users still using the classic symbols will have a mix. This is also true for archived content.
I appreciate any advice or discussion on this topic.
Erik
Hi Erik,
The ARIS provides 2 kinds of palette, the classic palette contains all objects symbols from ARIS 7.2 Method, and the default palette contains the newer symbols. When you select one kind of palette the ARIS will not address the custom symbols to the different palettes, and this answer your first question. About the second question, one way to 'disregard' is by using the Method Filter where you have to allow each symbol you want to use.
About what you wrote, I think that one way to handle these custom symbols is to configure the Method Filter, and using the Filter you have a control for each symbol that want to be used by end users.
BR
AO
Thank you for your reply.
I took the filter approach and created a bunch of new symbols to replace the old ones. The plan was to do this in each model when requested. That would allow me to softly steer new modeling initiatives towards the new look while allowing all the old content to remain unchanged.
However i stumbled on problems related to templates. Please follow the link to another post if you are interrested.
https://www.ariscommunity.com/users/erimos81/2020-12-21-problem-symbol-size-related-new-palette-setting