Workflow input types

Workflow input types

The workflows of InterformNG2 can get the input from many different input sources.

In the workflow the input type is shown as the leftmost component:


    

The input type is the type, that you select here when you create a new workflow and click here:


When you select this option, then you will see all input types, but some might be disabled as seen below:
If an input type is shown in light grey with the triangle on the right, then the input type is not allowed due to security settings. You can click the triangle to see the reason. In general the security settings are found under the Global system settings in the section, Workflow capabilities. 

The input types are all listed here:

  1. AS400 Command input
    Call InterformNG2 via a command on the IBM i platform.
  2. From Active MQ
    Read from an Active MQ message queue.
  3. From Azure Service Bus
    Reads a message from an Azure Service Bus.
  4. From IBM i output queue
    Monitor an output queue on the IBM i for input spooled files. Alternatively you can consider to monitor multiple output queues in a single workflow.
  5. From IBM i output queue (multiple)
  6. With this input type you can monitor multiple output queues with a single workflow.
  7. From IBM i output queue (Stream)
  8. Similar to From IBM i output queue - except this is for very large spooled files, that are to be processed page by page.
  9. From Kafka
    Read messages from Kafka
  10. From IBM MQ
    Read from an IBM message queue
  11. From database
    Read from a database. Please notice, that this supports only a predefined structure of the database with an input XML file found in a BLOB field.
  12. From input form menu
    This enables a web form menu. The form selects between multiple templates via a menu. The available templates are listed in the workflow.
  13. From input form
    Enables a web form. You can use this to interact with the user. 
  14. From other workflow
  15. With this you define a sub-workflow, that is to be called from other workflows.
  16. M3 input
    Use this input for processing Infor M3 files after you have configured Infor M3 and InterformNG2.
  17. REST webservice Basic
    The most simple REST webservice. You can use this to get started, but REST webservice OAuth2.0 is recommended.
  18. REST webservice OAuth2.0
    Called as a REST web service. It is recommended over REST webservice basic, but is a bit harder to setup.
  19. Read from file
    Select input files from a monitored folder.
  20. Read from FTP
    Selects an input file via FTP.
  21. Read from email server
    Read incoming emails from an email server.
  22. Read from resource folder
    Read input files from a monitored resource folder.
  23. Read from Windows share
    Read files via a folder on a Windows share.
  24. Scheduled start
    This kind of workflow will wake up each day at a specific time only contrary to the other workflows, that reacts immediately to new input files.
  25. Start approval process
    Sets up a workflow for approval of versioned resources, that require approvals. 
  26. TCP socket input
    With this the workflow can read from a TCP port and process the input.