Versions Compared

Version Old Version 12 New Version 13
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Backup Path (text box editor type) (type: string): the path where the backup file will be created. The path can be manually written or selected by clicking the  button.
  • BackupName (text box editor type) (type: string): the name of the backup file that will be created. Should be a .dmp extension file (E.G. XE.dmp, where XE is the name of the current database).
  • exp.exe Path (text box editor type) (type: string): the the path of exp.exe (the Oracle export utility), or select it with the File Browser. By default, exp.exe is located in C:\oraclexe\app\oracle\product\11.2.0\server\bin\ folder, where C:\oraclexe\app\oracle\product\11.2.0\server\ is also the value for the ORACLE_HOME environment variable.
  • Password (password editor type) (type: string): the password for the provided username. The password should be the same as the one given for the Connect to OracleSQL activity. The Backup Database activity creates a connection string based on the user provided at the connection activity and the password provided in the backup activity.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the sql server. (This parameter is used only when the user wants to send an encrypted password from outside the task, for example Flowster Portal).
  • SID (text box editor type) (type: string): the Oracle SID (Oracle System Identifier, which is used to distinguish Oracle database instances). By default it will be set to XE, which is also the Oracle's default database name. 

...

The file can be seen in the specified location:


 

 

 

 

Delete Row(s) from Table

This activity deletes Row(s) from a SQL Server database table.

...

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Delete Row(s) from Table activity:

 

 

 

 

Insert Row(s) into Table

This activity inserts Row(s) on a SQL Server database table.

...

 

Execution: the activity will insert the new row into the selected table. In the database, the row can be seen with the ID 3:

 

 

 

 

 

Remove User Access from Database

...

 

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs True or False if the execution was successful or not.

 

 

 

 

Run query

This activity runs a query on an Oracle Server database.

...

 

Execution: In the Tracking Data there can be seen the returned results:

 

The same result can be seen when executing the same SQL Select query from Oracle Application Express:

 

 

 

 

Select Row(s) from Table

This activity selects and returns Row(s) from a SQL an Oracle Server database table.

Activity Parameters

The Select Row(s) from Table activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Distinct (combo box control)   (type: string): whether the returned values should be distinct or not.
  • Fields (text box editor type) (type: string): the column headers that you want to be returned with the select command. If you enter more than one you should separate them with ','. Order By (text box editor type) (If all fields needs to be returned, then just use "*". The " * " has the same role as used in the SQL select all statement: select * from table
  • Order By (text box editor type) (type: string): the column header that you want to result to be ordered by. Order by Direction (combo box control) (typeFor example, if "ID" is inserted, then the values returned will be ordered depending on the value set in the ID column. If no value is provided, the activity will return the values in the same order as taken from the table. 
  • Order by Direction (combo box control) (type: string): choose to order the resulted rows in ASC Ascending or DESC Descending direction. It will be ignored if Order By is not set.
  • Table (text box editor type) (type: string): the table name on which to run the select.
  • WHERE (text box editor type) (type: string): the Where statement. For example: ID>2, where ID is a column header.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Select Row(s) from Table activity:

Image Removed

 

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: collection<collection<string>>): outputs a collection of collections of strings containing the selected rows.To use the elements of the collection, use Get Element From Collection activity.
  • Output Columns (type: int32): outputs the number of columns returned.
  • Output Rows (type: int32): outputs the number of rows returned.
 

Image RemovedImage Added

 

A more complex example, with fields, orders and statements can be seen in the image below:

Image Added

Execution: In the Tracking Data there can be seen the returned results:

Image Added

 

The same result can be seen when executing the same SQL Select query from Oracle Application Express:

Image Added

 

 

 

 

 

Export from Database

This activity exports data from a Database into an XML or a CSV file.

Activity Parameters

The Export from Database activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Destination Path (combo box control) (type: string): the path where the export (csv or xml) file will be created.
  • File Name (text box editor type) (type: string): the name of the XML file or CSV file that will be created. E.g. 'XE_ExportFile'.
  • File Type (combo box control) (type: string): the type of the file that will be created. For each of them a different set of parameters will be displayed.
  • Overwrite (combo box control) (type: string): whether to overwrite the file if it already exists.
  • Root Name (text box editor type) (type: string): the name of the root for the .xml file. This field should be completed only when XML is selected in the File Type field. As syntax, for example, xml_root can be used.
  • Table (text box editor type) (type: string): the table from where the export will be made.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs True or False if the execution was successful or not.
 

 

Execution: the activity will create an export file of the table settled in the Table field, in the specified folder:

 





Import into Database

This activity imports data into a Database from an XML or a CSV file.

Activity Parameters

The Import into Database activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • File Type (combo box control) (type: string): the type of the file that will be imported from. For each of them a different set of parameters will be displayed.
  • First Row Header (combo box control) (type: string): whether the CSV file includes the header as a first row or not.
  • Import File Path (text box editor type) (type: string): the path where the file will be selected from, or choose it with the file browser.
  • Table (text box editor type) (type: string): the table name where the file will be imported. If left empty it will take the 'Name' of the CSV File or the 'Root Name' from the XML File.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Import into Database activity:

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: boolean): outputs True or False if the execution was successful or not.