IdStory Identity Manager

This task will be more complicated - basically any text column (+custom module) can contain script. Without some entity attribute annotation (~registrable), this task cannot be solved i think.

Radek Tomiška wrote:

This task will be more complicated - basically any text column (+custom module) can contain script. Without some entity attribute annotation (~registrable), this task cannot be solved i think.

This is true :( for debugging and analyze some issues will enought search only in attribute mapping. So if we will added new table or insert record in the current Usage table, only for attribute mapping it will be enough for this moment.

But this solutions isn't perfect and nice.

I almost forgot - workflow can use scripts too + from java code => I'm able to call script dynamically from every place.

But simple solution above will help I hope so.

You are right, but the simple solution will still help a lot. The question always is: "Is this script used? Where?". Java code, workflows and scripts are saved in Git repository, we can run "grep" and find if they contain the script (its code name). But we can't simply "grep" the IdM database for usage of transformation scripts.

ok, I'm just afraid, this information will not lead to admin delete some script "which is not used" :)

Implementation note for simple solution: new tab in script detail can be registered in acc module (=> mapping is not in core).

I cannot use the basic script filter since this is an acc module feature. I will create a custom controller and service in the acc module and put a new tab in the script detail.