Synchronize Composer Input-Events definitions

Processing AccountingIntegrator Input-Events

Before you can process the Rule Engine Input-Events, you must synchronize and complete their definitions in the Designer.

  1. Export Rule Engine Input-Events Types
    Use the Export Finance function to export the AI Enabler Process-Context-In and Input-Events objects into an XML file.
  2. Transform Rule Engine Input-Events Types
    Execute the transformConfiguration script to:
    • Transform the XML file into Datastore or InterPlay configuration files.
    • Integrate in an annotation file, if needed, additional information or small transformations in the original configuration.
    • Inside the Designer installation, in the extra/work/AccInt/financialExport folder, there is a sample file named annot.properties.template that provides examples on how to manage individual properties during the transformation process.
  1. Configuration import into Designer
    Execute the importDocument script to import the configuration file into the Designer where:
    • Input-Events now correspond to Objects.
    • Process-Context-Ins become Collections.

All data formats that are supposed to describe the stored data in Datastore must be defined in the Composer as Input Event types. For formats related to Output-Events in the Rule Engine configuration, you must create an Input-Event with an "Output" type.

If the Output-Event is associated with an Audit-Rule, check that the Audit-Rule has the same name as the Input-Event.

  1. Customization
    Once the Rule Engine configuration is imported into the Designer, you can customize it and add:
    • Variable recycling properties that InterPlay uses internally but are neither imported nor exported.
      You can use variables to compute or display intermediate results.
    • Constraints such as minimum and maximum value for numeric properties or possible values for alphanumerical properties (for InterPlay).
    • Criteria to optimize the access to the properties that will be the most used queried in the Datastore.
    • Tags to group the Object Types and simplify the creation of Datastore queries.
    • Spaces to store the objects and partitions calculation definitions.
  1. Publication of the configuration
    Publish the configuration to make the configuration available to the Axway AI Suite components.
  2. Data import
    Using the importDocument script, you import the configuration that has been generated to the Designer where you can enrich it with additional constraints. You then complete the configuration and create dedicated editors.
  3. Deployment
    When the configuration is ready, you generate a deployment package via the Deploy button.
  4. Configuration import
    Using the Repository scripts, you import the deployment package into the target Repository instance (alternative to the deployment from the User Interface).
  5. Configuration update
    Using the InterPlay scripts you update the InterPlay instance target with the new configuration. If new formats have been added, new database tables will be created to store the records corresponding to these formats.
  6. Import of AccountingIntegrator data files
    Using the importDocument script, you import AccountingIntegrator data files that respect the format you have specified in the configuration. The files are imported into Collections and stored in the InterPlay database. You can modify data via the dedicated Editors.
  7. Export of InterPlay data Collection
    Using the exportDocuments script, you export the Collections using the AccountingIntegrator format.

 

Note   Configuration import and update are performed automatically when you click the Deploy button in Designer if the InterPlay instance target has been linked to Designer.

Related Links