Overview of Infor BI Application Engine Process Editor
The Application Engine Process Editor is a tool that you need to define, verify, compile, test, and publish Application Engine processes. In principle, Application Engine processes are plain text files that contain the code written in the BI# programming language. The Application Engine Process Editor includes a text editor and supports the whole life cycle of a process.
Most business processes are fairly complex and you will rarely define a process that works out of the box. As long as your process definition is not complete, you can edit and test it locally with the Application Engine Process Editor. After you have fully completed and tested the process, you can publish it using the Application Engine Process Editor.
Before you publish a process, you must ensures that the process is valid. You must document it and you must provide the required information according to the rules of the BI# programming language. See The BI# programming language.
Whenever you publish a process, it is stored in the Repository database to which you are currently connected and it receives a unique version number. You cannot change or delete the version number of a process. You can load each version of a process separately in the Application Engine Process Editor. When you modify and publish a process, it receives a new version number automatically.
To use a process in other Infor BI or Infor d/EPM applications, you must specify its name and its version. This information ensures that even if you change a process, it will not affect any product that uses a former version of the process. If you prefer to use a different version of a process, you must explicitly change it in the application where it is used. In this way, auditors can check whether any process version has changed since the last audit.
In each process, you must define the version of the runtime implementation that it uses. This is another mechanism to ensure better compliancy. Like a version of a process never changes, also the runtime versions never change. If you update products to newer versions, all former runtime implementations are provided unchanged. If new functions are provided, they come with an additional runtime version. Also here, to address a new runtime version explicitly, you must change the process, which again is verifiable.