Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: MichPaule on July 10, 2024, 09:46:29 pm
-
EA 16.1.1628 (64bit) .QEAX database
According to https://sparxsystems.com/enterprise_architect_user_guide/16.1/modeling_fundamentals/scriptlets.html:
Scriptlet Permissions
Code in Scriptlets cannot alter or update elements in the model database. It can, however, read and update copies of the elements that are displayed on a diagram. Updates to elements made by Scriptlets are NOT written back into the model database.
My observation:
My test scriptlet modifies the value of an element's tag and the changed value immediately is visible in the database table t_objectproperties (checked with DB Browser for SQLite).
After closing the model and re-opening again the changed value is visible in the Properties tab (diagram containing scriptlet has not been opened).
To me is is clear that the scriptlet was able to change a tag value (which would be a great benefit for me).
But: How does this relate to the above mentioned restriction?
Would someone (Eve?) try to explain this discrepancy?
TIA
Michael
-
Wow, 7 days and no replies :-[
Looks like not so many people touched scriiptlets yet.
@Eve: Please comment on that briefly!
Thanks in advance :)
-
Michael,
If you want to contact Sparx, you'll have to go through proper channels. This is a user forum, and Sparx employees only respond occasionally here.
Geert
-
Yes Geert,
but which channel would be best?
It is presumably not a Bug and also it isn't a Feature Request.
So I have sent a mail to [email protected] hoping it will be answered.
In this case I will post the answer here.
The priority support is no way for me as our IT doesn't want to hand out the login data :(
Michael
-
If the documentation says "1+1=2" and you find that "1+1=3" then that counts as a bug for me.
You shouldn't worry too much about whether its a bug or a feature. Sparx will decide that for you anyway.
Simply use the bug report form. (I'm not sure if priority support really makes a difference with regards to bugs. A bug is a bug, regardless whether it was noticed by a "priority" user)
Geert
-
Inquiry issued (#24077892).
Let's see what they have to say...
-
Inquiry issued (#24077892).
Let's see what they have to say...
Update:
The issue has been confirmed and will be investigated further by our development team.
;)
-
Good to know. So it will be fixed or not. Like a sack of rice will eventually topple in China.
q.