- Tested for supporting PAIN.008.001.001 and PAIN.008.001.002 (version 1&2)
- The XML is generated based on core ISO2022 XML specification and does not support or include any 'Bank' or 'Financial Institution' specific rules or customization.
- Please note that the App does not consider or support any 'Bank' or 'Financial Institution' or such 'Entity' specific rules or customization. Since organizational rules vary.
- However the app is quite scalable and any such specific rules or customization can be easily built on top of the existing codebase (on-demand) since it already provides a ground framework.
- Feel free to submit such business rule specification as requirement or enhancement on the project issue tracker.
Note: PAIN008, PAIN001, PACS003 and PACS008 Generation is complete (ModeGenOnly). Other two modes are pending i.e. ModeValOnly and ModeValAndGen.
Please do not download from source code section as it may not be stable.
Instead use any latest stable release version, available for download from Releases section
Simply double-click the main script file named 'VBSX_Main.vbs' to launch the utility. This will launch the command line interface. Please note that you might get UAC prompt if UAC is enabled on your windows.
Note : Drag and Drop may work with UAC disabled.
Win 7 / 8 / Server.
User provided 'seed' or 'template' file for each specific file type (pain008, pacs003) to be produced.
MSXML6 Official Download here
Require admin privileges / script execution privileges (elevated UAC prompt) on your windows system.
-
The Parser has been designed 'not to resolve externals'. It does not evaluate or resolve the 'schemaLocation' or other attributes specified in DocumentRoot for locating schemas. The reason is that most of the time schemaLocation is not always valid or resolvable as XML travels system to system. Hence this design avoids non-schema related errors.
-
The parser validates strictly against the supplied XSD (schema definition) only without auto-resolving schemaLocation or other nameSpace attributes from the XML document. This provides robust validation against supplied XSD. Also the validation parser inherently validates all XML for well-formedness / structural.
-
The validation parser needs Namespace (targetNamespace) which is currently extracted from the supplied XSD. Please make sure that 'targetNamespace' declaration if any, in your XSD is correct. The targetNamespace decalaration is not mandatory and hence XSD without targetNamespace are also validated properly.
Please refer the Issue list.
Feel free to contribte by logging any new defects, issues or enhancement requests
- Tushar Sharma
This is licensed under the Apache-2.0 License - see the LICENSE.md file for details