I have created my own UML profil with new stereotyps in Enterprise Architect and made up some basic rules how these new stereotypes have to be connected. Now I'd like to have something like a Well-Formedness check on the models which I create.
I found that there is a Model Validation with some basic UML Well-Formedness checks, but I didn't find out how I can create my own rules, which should be checked.
To create your own model validation rules, you have to write an Add-In.
Check the help file under Automation - Add-In Model - Broadcast Events - Model Validation Broadcasts. There's an example in there.
If you've never written an Add-In, check out Geert Bellekens' blog (not me) for a good quick-start introduction.
Related
I registered a model in my AML workspace, and I can see it in the Model List:
Model List view
But I cannot see it in Designer (preview), which prevents me from using the new model there.
Designer view
Looks like a bug to me. Datasets work fine.
This is known issue as the models registered in workspace cannot be consumed in Designer without the new custom module capability (in private preview) available.
The models showing up in Designer today are these generated from Designer training -> inference pipeline conversion and can only be used in Designer (not registered in the workspace).
We have an effort ongoing to reduce the confusion.
Thanks for your feedback.
This is Blanca, working on AML Designer.
We're working on aligning models concept to reduce the confusion.
Shall we set up a meeting for us to understand your scenario to use registered model in Designer?
Your inputs will greatly help us to better design the user experience.
Could you please contact keli19#microsoft.com?
Thanks a lot for your help in advance!
I have a problem in adding a pattern in Sparx Enterprise Architect.
I created a diagram and then saved as a pattern as is shown in the following figure.
In addition, I designed my own custom toolbox using MDG technology, and I want to integrate that diagram with my toolbox to be something similar to the following figure
I just need to integrate that pattern (XML file) with my custom toolbox in MDG technology.
Pretty much straight forward. Once you create your MDG
check the Patterns box. Now the next after the profiles will ask for your patterns:
Locate your pattern files (best they were saved in a separate directory) and include your pattern(s).
Your MDG should now include the added pattern(s).
To refer the pattern in a toolbox you need to add <profileID>::<patternName>(UMLPattern) manually where appropriate.
I am using Sparx Enterprise Architect for the modeling process.
I created a custom requirements toolbox which is called security requirements based on a list of security standards using MDG technology.
I would like to create a hierarchy of requirements once the user drag-and-drop the main element into the workspace all sub-elements (requirements) are displayed automatically.
How I can create or design something similar to this process.
Thanks,
You need to define a _subtypeProperty in your metatype like described in EA's documentation
As always with EA you need some try-and-error to get it working. You might compare with BPMN2 Activity which offers such a menu:
The according MDG is located under EA's program folder in the MDGTechnologies. Just find the string _subtypeProperty and following taskType.
A bit of background before I begin.
Background:
I am working on migrating an existing .NET based system to Dynamics CRM and one of its key feature is its 'Request Approval Process'. I have implemented some simpler versions of such approval processes in past but this one is a bit complex since it involves multi-level approvals, multiple approvers at one level, amendment logic, delegation functionality, etc.
Analysis Till Now:
Before pushing this question at SO, I did a fair analysis of the requirements from my end and have come up with few possible approaches:
Workflow based approach (something on lines of this)
Complete custom logic using Plugins/Web Resources (something on lines of this)
I am not explaining the details of these approaches as of now but the core issue is that none of these two approaches are fitting correctly to my requirements.
Queries:
While analyzing these approaches I came across some newer functionalities added to CRM (listed below) but did not get any additional resources to explore them further. I just want to confirm that I am not trying to achieve something which is already present out-of-the-box or going in the incorrect direction.
1. Internal Process Automation:
Reference: Here
Any leads/thoughts on this approach? I am not able to find any good documentation/articles around this.
2. Graphical Approval Workflow:
Reference: Here
This feature seems to be useful but it is mentioned to be a part of Dynamics Marketing. With the new structuring of Dynamics 365, will this feature be a part of Dynamics CRM by default?
Also, the Prerequisites section of this link mentions certain Item Types for which you can configure this functionality. So can't we use this functionality for any entity records?
Any kind of help/inputs would be appreciated.
I'd suggest the best of both worlds: using out-of-box Workflows along with custom Workflow activities that you can write with C#. Use as much out-of-box functionality as you can, but when you need to query records or run custom logic, create a custom workflow activity that can be used in your out-of-box Workflow. Custom workflow activities are similar to plugins in that they are written using C#. You can have custom inputs and custom outputs for your activity.
For example, maybe your approval process needs to look up the appropriate approving user for this record. You could write a custom workflow activity that takes an input (the record being approved) and an output (the user that has the ability to approve). Then in your Workflow, you'd add your custom activity as a step. After that step, you could send an email to the approver by using the output of that custom step.
More information about custom workflow activities: https://msdn.microsoft.com/en-us/library/gg309745.aspx
I am new to NetSuite and am trying to get an understanding of how it works in the area of business rules. So sorry if these are questions with obvious answers.
I understand a user/consultant can extend/customize it to fit with my business needs.
My questions therefore are:
Presumably a default instance of NetSuite contains various business
rules that will fit some business needs. As a user/consultant can
you view this default business logic?
Can a consultant change the core business logic? Or is it more a case of adding code before and after the default logic fires?
Is the default business logic/rules written in SuiteScript, or is SuiteScript only used by 3rd parties when extending/overriding the default logic?
Thanks
We cannot view the code that governs the default NetSuite logic and business rules, but the NetSuite Help documentation has a ton of information about how vanilla NetSuite works. All users can view and study the Help files to become more familiar with NetSuite and its default processes.
We cannot change the default code, but we can absolutely add code before and after many different events.
The default business logic is written in SuiteScript, but again, we cannot view that code. Third parties utilize SuiteScript to extend the default NetSuite functionality.
SuiteScript is not the only option for customizing NetSuite. There is also SuiteFlow, which provides users with the capability of graphically building workflows to define business rules based on user actions. No code is required (though under the covers, workflows essentially build hidden SuiteScript). There are several things that can only be accomplished in workflows and not in SuiteScript, and vice versa.
Netsuite's ERP, CRM, eCommerce modules have predefined standard rules which are acccording to industry standard. But customers have sometimes different business needs. For that we can customize Netsuite. There are various customization tools available in Netsuite. It supports to extend standard functionality as well as implement our custom logic. It provides suite scripts,a java script based API which can be used in almost every where in Netsuite for customization. Along with that it provides UI based customization in the form of SuiteBuilder. We can fire script before any standard business logic, after standard business logic run. We can add client side validations, schedule our application to trigger at specific time and many more. The standard business logic is written by Netsuite, we cant alter them, we cant see the code. It is the way it works. If you are new to Netsuite, it is suggested to read netsuite help guide. There is no online help other than Netsuite available. So you must go through them. If you have other query, feel free to ask.