Data Type reused in Digital Modeling Suite
•
0 likes•255 views
Join our R&D team to learn how using the Digital Enterprise Suite (DES) allows you to re-use existing data types in modeling decisions and processes.
Recommended
Recommended
More Related Content
Similar to Data Type reused in Digital Modeling Suite
Similar to Data Type reused in Digital Modeling Suite (20)
More from Denis Gagné
More from Denis Gagné (20)
Recently uploaded
Recently uploaded (20)
Data Type reused in Digital Modeling Suite
- 1. Trisotech.com Data Types Reuse in the Digital Modeling Suite Mélanie Gauthier, Modeling Lead at Trisotech Simon Ringuette, R&D Lead at Trisotech
- 2. Trisotech.com Data Types Reuse in the Digital Modeling Suite OData <XSD/>
- 4. Trisotech.com Advantages of reusing existing data types Leverage existing material in the enterprise Keep things familiar Easier integration with exiting system (internal or external)
- 5. Trisotech.com Scenario Calculate the BMI (Body Mass Index) of a patient oUsing structure from XSD in Workflow Modeler oUsing data from Odata in Decision Modeler oUsing data from an OpenAPI in Workflow Modeler
- 6. Trisotech.com XSD Standard of the W3C Defines the structure of an XML file Modelers supports include and import statements Can be imported in all modelers supporting data types
- 8. Trisotech.com OData OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. More focused on data with defined set of operations to access them Can be imported in Decision and Workflow Modeler; creates both the data and the operations
- 10. Trisotech.com OpenAPI Standardized way to describe REST API that can be consumed by human and machines to know how to interact with a system without any supplementary documentation required. Under the Linux Foundation Version 2 and 3 can be imported in the Decision Modeler and the Workflow Modeler Creates both the data types and the operations
- 13. Trisotech.com Centralized data Data can be defined in one model and reused in others One tool that can be used for this is the Knowledge Entity Modeler
- 15. Trisotech.com Reuse data types with the Digital Enterprise Graph
- 16. Trisotech.com Data type reuse by reference/by copy Data types are indexed in the Digital Enterprise Graph They can either be used by reference or by copy By reference: osynchronized each time the model is open owhen they are changed while the model is opened By copy: onot automatically synchronized ocan be synchronized manually
- 17. Trisotech.com Pro and Cons of using by reference Pro oAlways in sync with their source so there’s a greater consistency accross all models Cons oNo modification can be done locally on the element oChanges done to the type might break the model
- 18. Trisotech.com Pro and Cons of using by copy Pro oType can be modified locally to suite your needs oNo external changes will affect your model Cons oLess consistency accross all model oChanges must be fetched manually
Editor's Notes
- Today we are going to focus on three of the modelers available in the Digital Modeling Suite: Workflow, Decision and Knowledge Entity. The Digital Modeling suites allow business user and technical users to modelise the business logic of their enterprise. Workflow Modeler focus on the process of the enterprise while the Decision Modeler focus is the business logic based The Knowledge Entity Modeler is more like a centralized glossary where you can keep the terms used in your enterprise, the types and even the rules. We will show you how you can imported existing data types from XSD, Odata and OpenAPI to the modelers. We will do a small détour to show how those data can be fetch to use in the Digital Automation Suite. Then we will demonstrate how you can create new terms and types from the KEM. From there, we’ll show you how those types can be used through the Digital Enterprise graph either by reference or by copy.
- World Wide Web Consortium Published 20 years ago to replace the Document Type Definitions (DTDs)
- Open Claculate Patient BMI - XSD Show the XSD file than import in the modeler Show the item definition Do the mapping Publish the model, execute from an XML file
- Open Calculate Body Mass Index Odata Show the Odata file, espcecially the entity Patient Import the Odata; enter the url https://odata.triso.tech/simon/simon Show the different operations available Show the imported data type Go to BKM get patient, change to O, select operation and interface Go to Invoke get Patient, do the invocation and the mapping of id Set output type to Patient Go toe Determine BMI Category and set the parameter patient.weight/height Execute in the modeler directly
- Broader than Odata since you can add all of your operations and also how the security is implemented
- Open Claculate Patient BMI – Open API Show the OpenAPI file Import it Show the operation and the ouptut parameter Show the data type Assign th e type to patient Map the service task to the operation and interface No exécution for this one
- Open the HeatlthCare model Show the Patient entry and the Blood Pressure one. Show the type of Patient Explain how this centralizes knowlege helps. This is common knowlege can then be used to build all the models. In our example we could have share use of the same patient definition to remove the need of complex mapping.
- Create a new Workflow model Drop Patient Show the definition, the data type with all its sub types Go to Data type and show the reuse from graph. Import Appointement Drop a new data objec and assign Appointement to it Unlock Appointement Go back to the KEM. Change patient (add an item component Birthdate) Change appointement, remove reason. Save the model. Go back to the workflow modeler. Show the change in the Patient type. Show Appointement, it hasn’t changed. Synchronized manually.
- Presentation will be available soon on our website