Native Call

Native Call is used to run the .EXE, .BAT or .SH files asynchronously during the execution of a process flow.

Steps to create a Native Call:

1. Click Configure > EXTENSIONS > Native Call.

2. Click Create Native Call. 
   
   
   

3. Enter the name and description of the new Native Call service in the Name and Description fields respectively.
4. Select the extension of the file i.e. .exe, .bat or .sh in the Default Extension field.
5. Enter the filename with full path in the File Name(Absolute Path) field.

6. To specify any arguments for selected batch or executable file enter the arguments in the Argument(s) space separated field.

7. Enter the path of directory, where you want the run the specified batch or executable file, in the Working Directory (Absolute Path) field.

   All files specified into batch or executable file must be placed on the server on which the Connect Server is running.

   If Working Directory is not specified, the home directory of Connect Server becomes the working directory. All the files specified into batch or executable file will be looked into Connect Server home path. For example, there is batch file Mybatch.bat and it is placed on C drive. The contents of batch file are Copy File1.txt File2.txt. File1.txt is placed in C drive. Since the working directory is not specified the batch file will look for File1.txt and it will cause error. So you can either specify the working directory (i.e. C:) or specify the absolute path (e.g. copy C:\File1.txt C:\File2.txt) in the batch file.
8. Expand the Advanced Properties.
9. Select the Project in the Project field. 

10. Click Save.

    When using a native call in a process flow, the waitForEnd property is set to False by default. This implies that the native call and other activities in the process flow are executed simultaneously. If you want to wait till the native call is complete, before executing the next activity in the process flow, you need to set this property to True.