Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

ER Diagram

mermaid-diagram-2024-03-25-153251.png

BIE Package List

This page displays the BIE Package list. The list shows properties such as package version ID, package version name, and package description. Users can create a new BIE package by clicking the 'New BIE Package' button at the top-right, edit an existing BIE package by clicking the record in the list, and discard a BIE package by checking the record and clicking the 'Discard' button at the top-right.

Considerations

  • Does each BIE Package have statuses similar to BIE? (e.g., statuses like WIP, QA, Production)

    • If so, what is the relationship between the status of the BIE Package and the status of individual BIEs? For example, if the status of the BIE Package is moved from WIP to QA, should the status of all BIEs belonging to that BIE Package also be moved to QA?

  • Does each BIE Package also have ownership like BIE?

    • If so, is the ownership of the BIE Package held by one person or can it be held by multiple people?

  • Can each BIE Package be copied like BIE?

  • Is the BIE Package dependent on the OAGIS release, or is it independent? For example, if working with a BIE Package targeting OAGIS 10.9, would only BIEs created in OAGIS 10.9 be available within that BIE Package? If so, it could be considered dependent.

    • If it is dependent, is BIE Package Uplifting necessary? If so, would it be a feature to uplift all BIEs belonging to the BIE Package at once?

Edit BIE Package

This page displays the specific BIE package for editing. It shows the properties of the BIE package and the list of BIEs belonging to it. Users can update the properties, add and remove new BIEs from the list, and discard the BIE package.

Considerations

  • Perhaps there is a 'Generate' button available for generating expressions for the BIE Package. In this scenario, multiple BIEs could be targeted.

    Is it necessary to insert BIE Package properties into all BIEs, or is it sufficient to insert them only into the top-level BIE (e.g., BOD)?

    For instance, consider a Notify BOM with BIE version 'v1', which is reusing a BOM with BIE version 'v2'. When generating the expression of the Notify BOM using the current logic, you may want to include properties such as packageVersionID, packageVersionName, and packageDescription specifically for the Notify BOM. However, since each BIE has a different version, the versionID property should be unique to each. 

    <!-- NotifyBOM.xsd -->
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/10" targetNamespace="http://www.openapplications.org/oagis/10" elementFormDefault="qualified" attributeFormDefault="qualified">
	<xsd:element name="NotifyBOM">
		<xsd:complexType>
			<xsd:sequence>
				<xsd:element name="BOM">
					<xsd:complexType>
						<xsd:sequence>
							...
						</xsd:sequence>
						<xsd:attribute name="versionID" use="required" fixed="v2" type="xsd:token" />
					</xsd:complexType>
				</xsd:element>
			</xsd:sequence>
			<xsd:attribute name="packageVersonName" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageVersonID" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageDescription" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="versionID" use="required" fixed="v1" type="xsd:token" />
		</xsd:complexType>
	</xsd:element>
	...
</xsd:schema>

    If the current expression logic is modified to allow the schema to access reused BIEs using reference objects, separate files may be generated for the Notify BOM and BOM. In this case, it may be necessary to represent the BIE Package properties in each file. 

    <!-- NotifyBOM.xsd -->
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/10" targetNamespace="http://www.openapplications.org/oagis/10" elementFormDefault="qualified" attributeFormDefault="qualified">
    <xsd:include schemaLocation="BOM.xsd" />
	<xsd:element name="NotifyBOM">
		<xsd:complexType>
			<xsd:sequence>
				<xsd:element ref="BOM" />
			</xsd:sequence>
			<xsd:attribute name="packageVersonName" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageVersonID" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageDescription" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="versionID" use="required" fixed="v1" type="xsd:token" />
		</xsd:complexType>
	</xsd:element>
	...
</xsd:schema>

<!-- BOM.xsd -->
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.openapplications.org/oagis/10" targetNamespace="http://www.openapplications.org/oagis/10" elementFormDefault="qualified" attributeFormDefault="qualified">
	<xsd:element name="BOM">
		<xsd:complexType>
			<xsd:sequence>
				...
			</xsd:sequence>
			<xsd:attribute name="packageVersonName" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageVersonID" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="packageDescription" use="required" fixed="..." type="xsd:token" />
			<xsd:attribute name="versionID" use="required" fixed="v2" type="xsd:token" />
		</xsd:complexType>
	</xsd:element>
	...
</xsd:schema>

  • No labels

https://oagi.org/pages/connect-membership