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.
