Changes for page Limitations of eMagiz definitions
Last modified by Danniar Firdausy on 2024/09/16 14:32
From version 6.6
edited by Danniar Firdausy
on 2024/09/16 14:28
on 2024/09/16 14:28
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -2,7 +2,7 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 5 -In this microlearning, we will delve intomecruciallimitationsyouwill need to be aware of when importing your definitionsintoeMagiz.Understandingtheseconstraintswillhelpyoumakeinformeddecisionsand avoidpotentialissues.5 +In this microlearning, we will focus on certain limitations when importing your definition in eMagiz. It is necessary to understand these limitations in order to make the correct choices before importing your definition into eMagiz. 6 6 7 7 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 ... ... @@ -12,22 +12,29 @@ 12 12 13 13 == 2. Key concepts == 14 14 15 -This microlearning centers around learning which limitations you need to take into account when importing your definition .16 - *With eMagiz definitions we mean: Structured data models that represent how a message should look like at a certain point in the flow17 - *With limitations we mean: Restrictions of what will and what won't work when importing your definitions15 +This microlearning centers around learning which limitations you need to take into account when importing your definition 16 +With eMagiz definitions we mean: Structured data models that represent how a message should look like at a certain point in the flow 17 +With limitations we mean: Restrictions of what will and what won't work when importing your definitions 18 18 19 +Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition 20 + 21 +* Imported files cannot be larger than 1MB 22 +* xs:all statements cannot be represented in the data model. 23 +* Iterations (maxOccurs) over a threshold of 50 are not accepted 24 +* Cross reference between entities that could lead to an infinite loop are not accepted 25 + 19 19 == 3. Limitations of eMagiz definitions == 20 20 21 -In this microlearning, we will focus on certain limitations when importing your definition in eMagiz. It is necessary to understand these limitations in order to make the correct choices before importing your definition into eMagiz. Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition28 +In this microlearning, we will focus on certain limitations when importing your definition in eMagiz. It is necessary to understand these limitations in order to make the correct choices before importing your definition into eMagiz. 22 22 30 +Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition 31 + 23 23 * Imported files cannot be larger than 1MB 24 -* xs:all statements cannot be represented in the data model. 25 -* ref statements cannot be represented in the data model. 26 -* choice constructs cannot be represented in the data model. 33 +* xs:all statements cannot be represented in the data model 27 27 * Iterations (maxOccurs) over a threshold of 50 are not accepted 28 28 * Cross reference between entities that could lead to an infinite loop are not accepted 29 29 30 -Below we will specify per limi tations what this exactly means.37 +Below we will specify per limiations what this exactly means 31 31 32 32 === 3.1 Imported files cannot be larger than 1MB === 33 33 ... ... @@ -42,41 +42,35 @@ 42 42 * Write a custom XSLT that will transform the incoming message to a structured messages that you can validate via the tooling 43 43 * Use a custom XSD as validation and use the standard eMagiz tooling for your transformation, whereby you assume that your system definition has a defined structure 44 44 45 -=== 3.3 ref statementscannotbe representedinthedatamodel===52 +=== 3.3 Iterations (maxOccurs) over a threshold of 50 are not accepted === 46 46 47 - Asspecified beforein earliermicrolearnings, eMagiz definestheexpectedstructurewiththehelpof data models.Withinadata modelyouneed tospecify the associationbetweenentities.In XSD terminologythisis represented asfollows <xs:element type="itemsType" name="items"/>.However,sometimes we see adifferentnotationthatisnotworkingwhenimportinganXSD inMagiz. Thisnotationis<xs:group ref="status_group"/>. To get this in you need torewritetheassociationinyourXSD a bittoreflectthefirstnotation andmentionthattheassocation isoptional(minOccurs="0").54 +To prevent weird results when it comes to the creation of data models we do not accept maxOccurs above 50. To succesfully import your definition you should change the maxOccurs setting to unbounded. This way eMagiz will succesfully import the definition. As of today we have never encountered a practical case where this caused issues. 48 48 49 -=== 3.4 C hoicestatements cannotberepresentedinhedata model===56 +=== 3.4 Cross reference between entities that could lead to an infinite loop are not accepted === 50 50 51 - Asspecifiedbefore inearlier microlearnings,eMagizdefinesthexpected structurewiththeelpof data models.Withina data model youneedtospecifytheassociationbetweenentitiesandorderwithin these entities.In XSDterminologythisisrepresentedas follows <xs:complexType><xs:elementname="employee"type="employee"/><xs:elementname="member"type="member"/></xs:complexType>.However, sometimesweseethata choice isofferedintheXSD. Thisnotationmeansthat youcansupply AorB. Thisnotationis<xs:complexType><xs:choice><xs:elementname="employee" type="employee"/><xs:elementname="member"type="member"/></xs:choice></xs:complexType>. To get this inyouneed toemovethe referencetothe <xs:choice>andthe</xs:choice> linesin yourXSDand makeeach elementwithin thechoiceoptional(minOccurs="0").58 +In some cases we see definitions in which entities keep referecing each other. This could cause an infinite loop to occur when trying to build up the correct structure of your system message. Therefore we do an initial check when importing your file to safeguard ourselves against creating infinite loops in our portal that will in the end break the eMagiz portal. 52 52 53 -== =3.5Iterations (maxOccurs) over a threshold of 50 arenotaccepted===60 +== 4. Assignment == 54 54 55 -To prevent weird results when it comes to the creation of data models we do not accept maxOccurs above 50. To succesfully import your definition you should change the maxOccurs setting to unbounded. This way eMagiz will succesfully import the definition. As of today we have never encountered a practical case where this caused issues. 62 +Make sure that at least one of the attributes within one of your data models is set to Confidential 63 +This assignment can be completed within the Design phase of your (Academy) project that you have created/used in the previous assignment. 56 56 57 -== =3.6Cross referencebetween entities that could lead toaninfinite loop are not accepted===65 +== 5. Key takeaways == 58 58 59 -I n some cases we seedefinitionsin which entitieskeepreferecing each other. This could causeaninfiniteloopto occurwhentrying to build up thecorrectstructure ofyoursystem message. Thereforewe doaninitialcheck whenimportingyourfile to safeguardourselves against creating infinite loopsinour portal that will inthe end break the eMagiz portal.67 +Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition 60 60 61 -== 4. Key takeaways == 69 +* Imported files cannot be larger than 1MB 70 +* xs:all statements cannot be represented in the data model 71 +* Iterations (maxOccurs) over a threshold of 50 are not accepted 72 +* Cross reference between entities that could lead to an infinite loop are not accepted 62 62 63 -* File Size Limit: Imported files must be 1MB or smaller to ensure system stability. For larger files, please contact your partner manager for a tailored solution. 64 -* No xs:all Statements: eMagiz cannot process xs:all statements which allow elements in any order. Convert these to xs:sequence to ensure compatibility. 65 -* No ref Statements: ref statements for element references aren't supported. Use explicit element definitions instead. 66 -* No choice Constructs: eMagiz does not support xs:choice constructs. Modify your schema to make elements optional rather than using choices. 67 -* Max Occurrences Limit: maxOccurs values over 50 are not accepted. Adjust to unbounded if needed for successful import. 68 -* Avoid Infinite Loops: Cross-references between entities that may create infinite loops are not allowed. Ensure your definitions avoid such structures. 74 +== 6. Suggested Additional Readings == 69 69 70 - ==5. SuggestedAdditionalReadings==76 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz. 71 71 72 - Ifyouareinterested inhistopic andwantmore informationon it please read the help text provided by eMagiz and see the followinglinks:78 +== 7. Silent demonstration video == 73 73 74 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] 75 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] 76 -*** [[Creating a message definition (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-creating-a-message-definition||target="blank"]] 77 -*** [[Importing a message definition (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-design-import-message-definition||target="blank"]] 78 -* [[Limitations (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22limitations%22||target="blank"]] 79 - 80 +As this is a theoretical microlearning there is no video 80 80 ))) 81 81 82 82 ((({{toc/}}))){{/container}}