I'm having issues seeing the "Value" and "Margin" values when my context is a specific classifier of the original generic context with redefined values. For instance, my parent block is "Power Supply" which has Vmax:Real with no default value. I have a specific power supply, "Power Supply 123", with Vmax redefined as 300, and a generalization relationship to "Power Supply", Vmax within "Power Supply 123" is redefining Vmax from "Power Supply". I have a requirement, "Power Supply shall have a Vmax greater than 120", with a satisfy link between requirement and Vmax value property from the "Power Supply" block. When I run "Power Supply 123" in simulation I get the green/red highlight on the redefined Vmax value property as intended. When I make "Power Supply 123" or a saved instance of "Power Supply 123" as the context of the Requirement table, I cannot see values for "Value" or "Margin". When I force a default value for Vmax for my template "Power Supply" block it does show up in the requirement table. It's like Cameo cannot interpret redefined values within the Requirement Table and I think it should. This is causing issues as I would like to toggle different configurations quickly and see if they meet the requirements. What am I doing wrong?
Very good!! Is it possible to implement it using Refresh 1? I'm having troubles to run the simulation starting from the ground up on Refresh 1 version....
Hello. It should be navigation from your model. Instance is just representation of your model e.g. ua-cam.com/video/zyMONpAjAwE/v-deo.html. Let us know if something else is needed.
Hi. Great videos. Thank you! A request. Can you create a video that shows how to generate a sequence diagram from execution of activity diagram? Many thanks.
@@MBSEExecution thank you for your reply, the video was great in educating me on ALH. But on further research this method does not work for instance specifications because they are not part of the block. Additionally, due to Cameo not being able to pass arrays through ports, if you have blocks with multiplicity > 1, ALH will not work. I think I may have found an effective method of importing the Instance Specification class and creating an instance of it in the body of my opaque action.
2:36 very helpful to remember how to turn this setting on.
Thanks for the video Saulius. Can we see the verification results in this table for values generated through constraint blocks?
Thank you Amit. This is the plan for the future versions.
I'm having issues seeing the "Value" and "Margin" values when my context is a specific classifier of the original generic context with redefined values.
For instance, my parent block is "Power Supply" which has Vmax:Real with no default value. I have a specific power supply, "Power Supply 123", with Vmax redefined as 300, and a generalization relationship to "Power Supply", Vmax within "Power Supply 123" is redefining Vmax from "Power Supply". I have a requirement, "Power Supply shall have a Vmax greater than 120", with a satisfy link between requirement and Vmax value property from the "Power Supply" block. When I run "Power Supply 123" in simulation I get the green/red highlight on the redefined Vmax value property as intended. When I make "Power Supply 123" or a saved instance of "Power Supply 123" as the context of the Requirement table, I cannot see values for "Value" or "Margin". When I force a default value for Vmax for my template "Power Supply" block it does show up in the requirement table.
It's like Cameo cannot interpret redefined values within the Requirement Table and I think it should. This is causing issues as I would like to toggle different configurations quickly and see if they meet the requirements. What am I doing wrong?
Very good!! Is it possible to implement it using Refresh 1? I'm having troubles to run the simulation starting from the ground up on Refresh 1 version....
Hello Adriano. Red marking is available for long time. Extra properties like margine and bound are R2. Green marking is v2022x
How do I call a slot value in a nested instance specification through javascript on an opaque activity?
Hello. It should be navigation from your model. Instance is just representation of your model e.g. ua-cam.com/video/zyMONpAjAwE/v-deo.html. Let us know if something else is needed.
This is cool, Saulius! I think the "Use Requirements Terms Glossary" should be enabled by default as it is important, what do you think?
Hello Mohammed, thank you for the feedback! Totaly. This is requested so many times.. Hope will be considered soon.
Hi. Great videos. Thank you! A request. Can you create a video that shows how to generate a sequence diagram from execution of activity diagram? Many thanks.
Hello, thank you! Yes will do.
@@MBSEExecution thank you for your reply, the video was great in educating me on ALH. But on further research this method does not work for instance specifications because they are not part of the block. Additionally, due to Cameo not being able to pass arrays through ports, if you have blocks with multiplicity > 1, ALH will not work. I think I may have found an effective method of importing the Instance Specification class and creating an instance of it in the body of my opaque action.
Thank you for the feedback Olurun. Feel free to share if you can!
Nice!
Thank you Bruce!