Adding new schemas

If you are not using the published ISO 20022 UNIFI schemas or the EPC revised schemas published for SEPA, you will have to add any customized schemas to the framework.

This might be necessary if you are implementing recommended and mandatory fields in the customer–to bank messages. It might also be appropriate if the message is being sent to another member of an AOS community, and the schema has been modified to more specifically define those message element fields that are permitted by SEPA. This process requires tree and map modifications.

Follow these procedures to add a new schema:
  1. Add the new schema name to the sepagen.xsd schema located in the mapsandschemas directory, and save the file. This is a simple schema, and contains a choice group with the list of schemas currently used by SEPA. A new element can be inserted as follows: 
    <xs:element name="custom_schema_name" type="xs:string">
  2. Open the Type Designer and modify the existing sepagen file by importing the sepagen.xsd schema that you edited in step 1 as a Classic type tree.
  3. Place the modified type tree in the type_trees directory.
  4. Check to make certain that your customized schema is located in the mapsandschemas directory.
    Note: You must edit sepagen after it is created to remove any restriction lists that may have been created by the import process. At this point in the validation, we need to treat the bulk of the instance document as a blob of data (disregarding XML tags), until it is passed to the lower level maps that perform the validation

The previous steps will allow an instance document based on your new schema to be processed by the validation framework. However, to perform specific validation, you must add a new validation step for this schema. See Adding new validation steps.