Forum Discussion

gteachout's avatar
gteachout
Ideator I
6 years ago

AML code needed to load Requirements Engineer items

I am trying to batch load a series of requirements from another system into Requirement Engineering. I have been able to create a item using the following code.

<AML>
<Item type="re_Requirement" action="add">
<classification>Text</classification>
<global_version>34012</global_version>
<req_complexity>Low</req_complexity>
<req_document_type>8DF7037346A64816B8BBD8700AFCFE15</req_document_type>
<managed_by_id>EA1E67E3DD2340CEA4D49E1670AFBCE0</managed_by_id>
<req_title>Batch load test3</req_title>
<req_priority>Low</req_priority>
<req_risk>Low</req_risk>
</Item>
</AML>

Where it is failing is when I add in the <content> tag information.

<content xml:lang="en">Aras Review

Document Control
11977 and 12666| This goes hand and hand

15964 Aras or Scale?

13207 Does Scale need Legacy classification/Remove</content>

I can see there is other coding tags needed to format the text but do not know how or what coding is needed. Can someone share a example or a process on how to complete this task.

7 Replies

    • gteachout's avatar
      gteachout
      Ideator I
      6 years ago

      Thanks for the response, here is the error message I receive

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP-ENV:Body>
      <SOAP-ENV:Fault xmlns:af="http://www.aras.com/InnovatorFault">
      <faultcode>SOAP-ENV:Server</faultcode>
      <faultstring>
      <![CDATA[Data at the root level is invalid. Line 1, position 1.]]>
      </faultstring>
      <detail>
      <af:legacy_detail>
      <![CDATA[Data at the root level is invalid. Line 1, position 1.]]>
      </af:legacy_detail>
      <af:exception message="Data at the root level is invalid. Line 1, position 1." type="System.Xml.XmlException"/>
      </detail>
      </SOAP-ENV:Fault>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>

      • Gopikrishnan's avatar
        Gopikrishnan
        Accelerator II
        6 years ago

        Hi

        Can you try with below


        <AML>
        <Item type="re_Requirement" action="add">
        <classification>Text</classification>
        <global_version>34012</global_version>
        <req_complexity>Low</req_complexity>
        <req_document_type>8DF7037346A64816B8BBD8700AFCFE15</req_document_type>
        <managed_by_id>EA1E67E3DD2340CEA4D49E1670AFBCE0</managed_by_id>
        <req_title>Batch load test3</req_title>
        <req_priority>Low</req_priority>
        <req_risk>Low</req_risk>
        <content>Aras Review

        Document Control
        11977 and 12666| This goes hand and hand

        15964 Aras or Scale?

        13207 Does Scale need Legacy classification/Remove</content>
        </Item>
        </AML>

        It it doesn't work, try removing special characters in content tags

  • rif68941's avatar
    rif68941
    Ideator II
    5 years ago

    The challenge with using the batch loader for adding Requirements, as part of Requirements Engineering, is that there is an onBeforeAdd server method that generates the data for the <content>...</content> property. The data for the <content>...</content> is taken from the <item_number> and <req_title> properties.

    So the <contents>...</contents> property seems to be overwritten by the server event, thus not considering any inputs from the batch loader.

    A small change to the onBeforeAdd method could allow further fields to be added to the Requirement - a Description field for example.

    But I do not have the experience to update this method.

    Further investigation has identified a high-risk method of automatically adding a 'Title' and 'Text' elements to a already defined re_Requirement. Use SQL (via applySQL or SQL Server Management Studio).

    The <content>...</content> from an existing pro-forma requirement can be inserted into an existing re_Requirement table record. The results present, and are editable.

    For example, 

    1. Create a pro-forma template of the re_Requirement manually. With the addition of a Title block and a Text block, the database record is

    <Requirement aras:id="06915ffbc3bd4f3a9f341b16e94857d1" reqId="696D862F9799459D987B3D63D86FC249" xmlns:aras="">http://aras.com/ArasTechDoc" xmlns="">www.aras.com/REStandard"><Requirement-Info aras:id="a8b2b599b8244e738845a2272e0f2176"><Requirement-Chapter aras:id="5a7f493f2f504bd39b3ddf6b20500bbf"><aras:emph> </aras:emph></Requirement-Chapter><Requirement-Title aras:id="2ac08c9e494244e19f2d45269d0aa66e"><aras:emph>RiF Test item 3</aras:emph></Requirement-Title><Requirement-Number aras:id="9572d3bca90a467d9f036356ea5eb1e2"><aras:emph>REQ-000000012</aras:emph></Requirement-Number></Requirement-Info><Title aras:id="1ACDBF2AB9D74A9B89BB6175FDA7AABc" ><aras:emph xmlns="">Description</aras:emph></Title><Text aras:id="C46ABE3370A34C4C85FE33C2A28E630e"><aras:emph xmlns="">This is the description of the Requirement</aras:emph></Text></Requirement>

    2. The textual content of 

    <Title aras:id="1ACDBF2AB9D74A9B89BB6175FDA7AABc" ><aras:emph xmlns="">Description</aras:emph></Title><Text aras:id="C46ABE3370A34C4C85FE33C2A28E630e"><aras:emph xmlns="">This is the description of the Requirement</aras:emph></Text>

    Can be inserted into the <contents> field for a re_Requirement that has been created using AML (for example) or the GUI without extra fragments.

    Until ARAS provides a better approach for programmatically generating extra content, the method may be used with caution.