Hello all,
we would like to hide some symbols in a model.
To be more precise we have some BPMN models including data objects as outputs of activity tasks and we would like to produce reports with the models' images not including the data objects (and their connections).
I first thought of applying a custom template to the model, but it seems you cannot make a symbol invisible in a template (unless maybe by setting the model background color to the line color/text color/fill color of the symbol ?).
I then thought of :
- copying the original model to a temporary one
- removing all occurrences of the unwanted symbols and their connections in the copy model
- deleting the temporary model when the report is done
But it's kind of using a sledgehammer to crack a nut.
Any ideas?
Thanks for your help
Regards
M
I just found out about the "Evaluation filter" (never paid attention to this before) that seems to be the tool I'm looking for.
I just gave it a try but without any success: I added an evaluation filter that did not take "data objects" into account, tried in with the report that outputs a model to a pdf file and got a pdf with all objects (including the data objects) without the ... objects' names.
I'll keep trying.
Hi,
an evaluation filter works just the same as a method filter. If you do not have an object in your (evaluation) filter, which has occurrences in a model that is in the filter, you see a shadowed version of the symbol. A user gets the information that there is something he is not allowed to inspect. That probably does not have much effect in your case, since the BPMN data objects are gray anyway. It does have the effect, that the report does not get any information about the object itself, hence you do not see the name of the data object and the report also has no chance to read any other attributes of the object.
Mon, 07/22/2019 - 16:04
Bonjour Michel,
in order to hide the grayed out objects completely in your diagram there is an Architect/Designer Option "Hide non-configured objects" (cf. online help page /abs/help/en/handling/ba/index.htm#63523.htm). If you create your report output with your evaluation filter and this option enabled, it should do the trick.
Another way of "masking" the symbols could be a layout template setting the symbol size to zero, which your report script could apply before writing the diagram output and reset to your standard template afterwards. The relevant scripting methods you can find in the standard report "Format models" in category Administration.
Regards, Martin
Thanks a lot @M and Martin
Combining the evaluation filter and the option "Option "Hide non-configured objects" " I almost got it.
Original model, exported as pdf , no filter
Same report (export as pdf) with an evaluation filter filtering the data objects , with the option "Option "Hide non-configured objects" " unset in Architect
The data object is grayed out. Note that the arrows of the connections between the tasks and the events are gone ! (don't know why)
Now checking the option "Hide non-configured objects" and using the evaluation filter :
The data object and its connection to the task are gone as wanted, but also the connections between the tasks and the events (which are not filtered by the evaluation filter)
I guess I have to dig a little more
Hi Michel,
it looks as though the connections between task and events were already filtered in the second image (the arrows disappeared, maybe there were two types of connections on top of each other?). So I suspect you missed some connections in your evaluation filter.
I suggest the following approach:
1. Create a new evaluation filter based on your method filter.
2. Edit your new evaluation filter and in the filter wizard only deselect the data object symbols (there are 3 of them: input, output, undefined) in the BPMN model type(s) you want to evaluate. This should also deselect the corresponding connection occurrences from and to those symbols only in the model type.
This way the data object type (Cluster/data model) stays in the filter and could be evaluated. Only the occurrences should disappear. The result will depend on how your report is built: If it evaluates on the definition level, this way the relationships could still be seen in the report result (though not in the graphic). If it evaluates the actual occurrences then you are fine. If it does not evaluate the relationships to the data objects at all, it does not matter anyway.
