/
Workflow

Workflow

Owned by Silvia Neag (Unlicensed)
Last updated: Jul 19, 2021 by wiki

Activities



Convert From DateTime To FileTime

This activity converts the DateTime value to FileTime.

Parameters:

  • Date - Full Format (text box editor type) (type: string): input date in the following format 'dd/MM/yyyy HH:mm:ss' to be converted to FileTime value. 

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

  • Output  (type: Int64): outputs the converted value.


Convert From FileTime To DateTime

This activity converts the FileTime value to DateTime.

Parameters:

  • FileTime Value (text box editor type) (type: Int64): input FileTime value that needs to be converted to DateTime value. 

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

  • Output  (type: DateTime): outputs the converted value.

Execution Log:


Custom ForEach

This activity cycles through elements of a collection.

When dragging the activity, the iterator type is required. If the collection to be iterated is of type Collection<Int32> , then the value selected in Select Types window should be of type Int32.

If the collection to be iterated is a collection of sub-collections of type Collection<Collection<PSObject>>, the TypeArgument property of the ForEach activity should be of type Collection<PSObject> and a second ForEach activity is to be used to iterate through the remaining collection. The TypeArgument property of the second ForEach should be of type PSObject.


For each element of the provided collection the activity will execute all activities dragged into the Body area.



Custom ForEach Conditional

This activity cycles through elements of a collection until a condition is met. The type of the input collection is detected automatically without user selection (as for Custom ForEach activity). The values for Condition and Values parameters can be bound to variables, global variables or IN arguments. 


For each element of the provided collection the activity will execute all activities dragged into the Body area. When the condition in Condition field is evaluated to True, it exists the iteration cycle.


NOTE: When a collection of custom type is used, the iterator will be converted to Object type automatically and a conversion to collection  type is required before accessing the iterator. E.g. Collection<KeyValuePair<String,String>> is the collection to be iterated. The iterator automatically is converted to Object not to KeyValuePair<String,String> which is the collection type, so the user must convert the Iterator to the collection type in the workflow logic as follows:

 

  • Step 1: add a convert activity in the Body sequence of the CustomForEachConditionalV421 activity

  • Step 2: declare a variable with Variable type - the type of the collection. E.g. variable Collection is of type List<KeyValuePair<String,DateTime>> so the Iterator1 should be of type KeyValuePair<String,DateTime> .  

 

  • Step 3: convert Iterator to Iterator1 using Convert activity.

  • Step 4: use Iterator1 to access custom properties of the custom type. E.g. Iterator1.Key for KeyValuePair<String,String> type.



Custom If

This activity executes a sequence of actions based on the result of a condition.

The condition evaluates if the element of the collection that is being iterated, is equal to "Flowster". If the condition is true, it will execute the "If Branch". If the condition is false it will execute the "Then Branch". The value for Condition parameter can be bound to variables, global variables or IN arguments. 




Custom While

This activity executes a sequence of actions until the given condition is no longer true.

This activity represents a control-flow type activity and it allows activities inside the block to get executed repeatedly on the given Boolean condition. The condition evaluated in the CustomWhile activity is 'Counter < 5' where "Counter" is a predefined IN argument with default value '0'. The block consists of two activities, one Assign activity to increment the value of the "Counter" by 1 at every step and a Write activity to display the "Counter" at each step. The CustomWhile execution stops when "Counter" value is higher than 5. The value for Condition parameter can be bound to variables, global variables or IN arguments. 




Delay 

This activity creates a delay until the given date & time.

Parameters:

  • Date - Full Format (calendar control): the date in the following format: 'dd/MM/yyyy HH:mm:ss'.
  • Day (text box editor type)(type: int32): enter the day when the delay will be finished. 
  • Hour (text box editor type)(type: int32): enter the hour when the delay will be finished. 
  • Millisecond (text box editor type)(type: int32): enter the millisecond when the delay will be finished. 
  • Minute (text box editor type)(type: int32): enter the minute when the delay will be finished. 
  • Month (text box editor type)(type: int32): enter the month when the delay will be finished. 
  • Second (text box editor type)(type: int32): enter the second when the delay will be finished. 
  • Year (text box editor type)(type: int32): enter the year when the delay will be finished. 



Delay by Date

This activity creates a delay until the given date & time.

Parameters:

  • Input Date (calendar control): the date in the following format: 'dd/MM/yyyy HH:mm:ss'.



Evaluate Expression

This activity evaluates an input expression.

Parameters:

  • Input Value (text box editor type) (type: string): the input value to be evaluated.

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

  • Output  (type: string): outputs the expression result.


 


Log Track Data

This activity writes the input value to the Track Data.

Parameters:

  • Input Value (text box editor type) (type: string): the input value to be written to the Track Data.




Selective Execution

The "Enabled" property default value is checked, thus the execution of the child activities inside the Selective Execution sequence is enabled. 


 

The switch to disabled may be done either from the Properties panel  or from the Workflow Designer panel.


Write

This activity writes text to console without ending the line.

Parameters:

  • Text (text box editor type) (type: string): the text value that should be written to the console.


Start Flowster Workflow

This activity starts the specified workflow using the Flowster RestAPI.

Activity Parameters

The Start Flowster Workflow activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Client Hash (text box editor type) (type: string): the client hash for the RestAPI. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Comments (text box editor type) (type: string): specify a comment for the workflow.
  • Execution Agent (text box editor type) (type: string): the Machine Name or IP address and the Port for the Windows execution agent which will execute the workflow. If this field remains empty, the default (Flowster Core) execution agent will be used.
  • Linux Execution Group (text box editor type) (type: string): the name of the Linux Execution Group which contains the Linux Execution Agent(s) that will execute the workflow. If this field remains empty, then the Linux Execution Agent will be ignored. Also, if from Administrator there is set "No Linux Agent" on the timestamp, then this field will be ignored.
  • Parameters Collection (text box editor type) (type: string): the parameters needed to be sent to the workflow. Arguments/Variables of type Array ( e.g. String[] , Int32[] ), Collection<T> ( e.g. Collection<String>), List<T> ( e.g. List<KeyValuePair<String,String>>) MUST be initialized before they can be used as binding. E.g. If a parameter of type Collection<String> is bound to a workflow parameter, it MUST be initialized either by setting value New Collection(Of String) in the Default Value column in the Designer - Arguments area or by using Assign ( or other initializing activities ) activity to assign New Collection(Of String) value to the argument/variable. NOTE: A detailed example regarding how to configure them can be found below.
  • Password (text box editor type) (type: string): the user password.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example from Flowster Studio Portal.
  • Rest API Address (text box editor type) (type: string): enter the Rest API Address. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Schedule Time (text box editor type) (type: string): the schedule time when the workflow should be executed. Accepted format is: dd-mm-yyyy HH-MM (E.g. 31-03-2015 12-06).
  • StartedBy (text box editor type) (type: string): enter the username with domain for the user that starts the workflow. If left empty, the specified 'Username' will be used.
  • Username (text box editor type) (type: string): the username with domain.
  • Workflow Category (text box editor type) (type: string): filter the workflows by the Category name. The timestamp must be a direct member of the selected category. If this parameter is set, then the Display Name field is needed as well.
  • Workflow Display Name (text box editor type) (type: string): the Display Name for the active workflow that you want to start with the activity. If more timestamps exists within the given display name, then try narrowing down the results by using the Workflow Category field. Otherwise, the first active timestamp will be retrieved and executed. The Display Name can be copied from Flowster Administrator.
  • Workflow ID (text box editor type) (type: string): the workflow's ID. It can be copied from the Flowster Administrator by selecting any timestamp from the desired workflow. This parameter takes precedence over the "Workflow Timestamp ID", "Workflow Display Name" and "Workflow Category" parameters.
  • Workflow Timestamp ID (text box editor type) (type: string): the workflow's ID. It can be copied from the Flowster Administrator by selecting the desired timestamp. This parameter takes precedence over the "Workflow Display Name" and "Workflow Category" parameters.

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

    • Output  (type: boolean): outputs True if the workflow was started, otherwise False.
    • Output Guid  (type: string): outputs the workflow Guid
    • Output ScheduledWFID  (type: Int32): outputs the scheduled workflow's ID


Configuration: below there can be seen a detailed example on how to configure Flowster Administrator and the Start Workflow activity in order to properly execute another Flowster workflow via the Start activity.

    • Flowster Administrator configuration:
      • go to the Integrator Page and define a new client:



      • with the mouse selection on the newly added client, go to the Security tab, click Edit Rights and add the desired users (NOTE: there will be available for assignment only the users added into Flowster as User type, not as Admin type.If the workflow is desired to be executed by an user which is admin, then the user should be added in two security groups: admin type and user type. Avoid assigning User Groups, due to the fact that a password will need to be set, and the activity cannot use a group password instead of an user one - cannot use IsUserInGroup):



      • select the assigned user and click the Set Password button. Give a password for the user (it is not mandatory to be used the user's default password. This password will be used only via RestAPI, in the Start Flowster Workflow activity.)
      • after assigning a password to the user, a field called RestAPI Endpoint will be displayed:







    • Start Flowster Workflow activity configuration:
      • copy the Client Hash App and paste it into the activity's ClientHash field:


      • copy the RestAPI Endpoint and paste it into the activity's RestAPI Address field:


      • insert the user in the domain\username format (a user which was assigned to the RestAPI client in Flowster Administrator):


      • insert the user's password (the password set on the RestAPI client in Flowster Administrator):


      • from Flowster Administrator → Portal Page, select the timestamp of the workflow which will be started by the activity, look into the workflow Details tab, copy the ID and paste it into the activity's Workflow ID field:


      • insert some Comments, if desired:


      • insert an Execution Agent IP if the workflow is desired to be started on a different Execution Agent than the default one (the Execution Agent format should be IP:PORT if it is not locally installed).
        NOTE: the user must have rights over the selected Windows Execution Group where the agent is configured. This can be set from Flowster Administrator, Security Groups Page, by assigning execution groups to the security group where the user belongs to (for more details see /wiki/spaces/FS/pages/16022342163):



      • if assigned, insert the Linux Execution Group.
        NOTE: the user must have rights over the selected Linux Execution Group. This can be configured from Flowster Administrator, Security Groups Page, by assigning execution groups to the security group where the user belongs to (for more details see /wiki/spaces/FS/pages/16022342163):



      • in the Parameters Collection section insert all the parameters that need to be sent to the workflow that will be started. The image below displays an example of parameters which will be configured from Administrator and values given from portal:

        where:
        • The Name column should contain the exact names as the parameters defined in the workflow that will be started
        • The Value column may contain default parameter types (String, Int32, Boolean etc.(No arrays can be sent via default values)) or can be bound to variables/arguments ( including variables/arguments of type Array ( e.g. String[] , Int32[] ), Collection<T> ( e.g. Collection<String>), List<T> ( e.g. List<KeyValuePair<String,String>>)), for executions via Flowster Portal (parameters that can be later defined in Administrator or given directly from Portal), as seen in this example. The Server, User and Password are arguments defined via the StartWorkflow workflow:


      • CAUTION: if using variables of type Boolean they must be set always even if they are optional and can't be sent in the parameters list of the activity, they need to be set in the workflow as variables with default value or IN argument with default value. 
      • IMPORTANT: Arguments/Variables of type Array ( e.g. String[] , Int32[] ), Collection<T> ( e.g. Collection<String>), List<T> ( e.g. List<KeyValuePair<String,String>>) MUST be initialized before they can be used as binding in Parameters Collection parameter of this activity , as seen below:

                                          

                                         




Execution:

  • via Designer:
    • define values for the parameters given in the ParametersCollection area (the Password argument will be excluded because of plain text reasons. This parameter, in case of not having an encrypted value for it, will be defined on the workflow which will be started - for this example only):



    • execute the workflow:



    • go to Flowster Administrator → Execution Logs and check if the workflow was started and executed:



  • via Flowster Portal:
    • bind the parameters given in the ParametersCollection area to defined arguments (these arguments should be defined inside the Start Workflow workflow):



    • check in the workflow in order to create a timestamp for it in Flowster Administrator:



    • mark the workflow as active:



    • select the timestamp and go to the Parameters section. Click Edit Parameters, select the Password one and make it as Password (not hidden) type:



    • Save and Close and go to Flowster Portal. Click Start workflow for StartWorkflow. Provide the input values and click Start workflow:



Start Snippet Workflow

This activity starts the specified snippet workflow. 

Activity Parameters

The Start Snippet Workflow activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Parameters Collection (parameters collection editor type) (type: string): the parameters needed to be sent to the snippet workflow. These parameters are filled in automatically once the snippet is selected using 'Snippet' parameter. The values for the parameters can be manually inserted (only string values are accepted) or via INarguments/variables (other types of values are accepted such as: Int32, Boolean, String[] etc.). In the examples below, the 'FolderName' parameter is given by direct value and the 'FolderPath' parameter is bound to an IN argument:

Snippet (text box editor type) (type: string): select the snippet workflow. This list is populated with active snippets. If this list is empty, this means there is no active snippet configured in Administrator. 

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

  • Output Tracking Data (type: List<KeyValuePair<string,string>>): outputs a list of KeyValuePairs containing the Snippet Workflow Tracking Data.
  • Output OutArguments (type: List<KeyValuePair<string,object>>): outputs a list of KeyValuePairs containing the Out arguments names and values.



Configuration : before Start Snippet Workflow activity is used , user must have at least one active snippet workflow in Administrator, as seen below. For further on information about createing a snippet workflow, please visit 


IMPORTANT: 

  • If the snippet's parameter list is modified (e.g. delete one parameter), all workflows that are linked to the snippet (workflows that use the snippet in Start Snippet workflow activity) must be checked out to refresh the snippets by clicking on Refresh Snippets button and checked in. This step is necessary so the list of snippet's parameters is refreshed in the linked workflows as well. If only the snippet's activities block is modified (reorder activities, add/delete activities etc) there is no need for an additional check in of the linked workflows. 



Execution: the execution tracking data of a snippet workflow is inserted into the Tracking Data of the triggering workflow. 



The values for the out arguments are displayed at the end of the snippet's Tracking Data. In order to extract values from Output OutArguments parameter, a Cast activity is needed to cast the object to the type of the out argument in the snippet. For example, if a snippet has an out argument of type Array<Int32>, the output argument is sent as an object to the Output OutArguments in the list of KeyValuePairs of arguments. In order to obtain values from the array, a cast from Object type to System.Int32[] is required using Cast activity, as seen below:

   


One must define a local variable of the resulted type to store the cast result, in this example a new variable MyArrayOfInt32 was created of type System.Int32[]. In the Operand field, the index of the interested out argument from the list was inserted, in this example, the forth out argument:


The array values are now stored in the local variables and may be extracted either by iteration or by index, for example MyArrayOfInt32(0) to extract the first element in the array. 


Stop Flowster Workflow

This activity stops the specified workflow using the Flowster RestAPI.

Activity Parameters

The Stop Flowster Workflow activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Client Hash (text box editor type) (type: string): the client hash for the RestAPI. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Password (text box editor type) (type: string): the user password.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example from Flowster Studio Portal.
  • Rest API Address (text box editor type) (type: string): enter the Rest API Address. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Scheduled Workflow ID (text box editor type) (type: Int32): enter the ID for the scheduled workflow that you want to stop , or bind this parameter to the 'Output ScheduledWFID' from the 'Start Flowster Workflow' activity.
  • Username (text box editor type) (type: string): the username with domain.
  • Workflow GUID (text box editor type) (type: string): enter the GUID for the workflow timestamp that you want to stop, or bind this parameter to the 'Output Guid' from the 'Start Flowster Workflow' activity. This parameter takes precedence over the 'Scheduled Workflow ID' parameter.

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

  • Output (text box editor type) (type: string): Outputs True if the operation succedded, otherwise False. 

Get Workflow Execution Status

This activity retrieves the status for the specified workflow using the Flowster Rest API.

Activity Parameters

Parameters:

  • Client Hash (textbox editor type) (type: string): the client hash for the RestAPI. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Password (text box editor type) (type: string): the user password.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example from Flowster Studio Portal.
  • Rest API Address (text box editor type) (type: string): enter the Rest API Address. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Username (text box editor type) (type: string): the username with domain.
  • Workflow Guid (text box editor type) (type: string): the workflow guid returned by the "Start Flowster Workflow" activity. 

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

  • Output (type: String): outputs the Workflow Execution Status. Valid status: 'Completed', 'Aborted', 'Terminated', 'Error', 'Denied', 'Expired', 'Exception' and 'Started'.


Get Workflow Parameters

This activity retrieves the specified workflow's parameters using the Flowster Rest API.

Activity Parameters

Parameters:

  • Client Hash (textbox editor type) (type: string): the client hash for the RestAPI. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Password (text box editor type) (type: string): the user password.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example from Flowster Studio Portal.
  • Rest API Address (text box editor type) (type: string): enter the Rest API Address. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Username (text box editor type) (type: string): the username with domain.
  • Workflow Category (text box editor type) (type: string): filter the workflows by the Category name. The timestamp must be a direct member of the selected category. If this parameter is set, then the Workflow Display Name field is needed as well.
  • Workflow Display Name (text box editor type) (type: string): the Display Name for the active workflow that you want to start with the activity. If more timestamps exists within the given display name, then try narrowing down the results by using the Workflow Category field. Otherwise, the first active timestamp will be retrieved and executed. The Display Name can be copied from Flowster Administrator.
  • Workflow ID (text box editor type) (type: string): the workflow's ID. It can be copied from the Flowster Administrator by selecting any timestamp from the desired workflow. This parameter takes precedence over the "Workflow Timestamp ID", "Workflow Display Name" and "Workflow Category" parameters.
  • Workflow Timestamp ID (text box editor type) (type: string): the workflow's timestamp ID. It can be copied from the Flowster Administrator by selecting the desired timestamp. This parameter takes precedence over the "Workflow Display Name" and "Workflow Category" parameters.

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

  • Output (type: Collection<KeyValuePair<String,String>>): outputs a collection of KeyValuePairs, containing the parameters found with their Names and other properties. In order to use the output, you can iterate through the elements and use the Get KeyValuePair activity with the keys: 'Name' , 'DisplayName' , 'ParameterType' and 'IsRequired'.


In order to iterate through the Ouput parameter collection, ForEach activity is used together with Get KeyValuePair activity to extract the value of the key Name:



Execution:


Get Workflow Tracking Data

This activity retrieves the Tracking Data for the specified workflow using the Flowster Rest API.

Activity Parameters

Parameters:

  • Client Hash (textbox editor type) (type: string): the client hash for the RestAPI. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Password (text box editor type) (type: string): the user password.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. This parameter is used only when the user wants to send an encrypted password from outside the workflow, for example from Flowster Studio Portal.
  • Rest API Address (text box editor type) (type: string): enter the Rest API Address. It can be copied from the Flowster Administrator by selecting the client App for the RestAPI.
  • Username (text box editor type) (type: string): the username with domain.
  • Workflow Guid (text box editor type) (type:string): enter the workflow quid. This parameter can be obtain from the Output parameter of the "Start Flowster Workflow" activity

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

  • Outputs (type: Collection<String>): outputs the Workflow Tracking Data lines
  • Output Workflow Output (type: Collection<KeyValuePair<String,String>>): outputs a list of dictionaries containing the OutArguments's Name, Value and Type. In order to use the output you can use the GetKeyValuePair activity with the keys: 'Name', 'Type' and 'Value'.

See below an example on how to iterate the list of OutArguments and extract output parameter 'ParamListKeyValuePair' of type List<KeyValuePair<String,DateTIme>> value. NOTE: because the values stored in the 'Value' keys of the list of dictionaries, are of type Object, a conversion is needed if the type of the output argument is different than Object, as seen below:

                      




Wait For More Input

This activity waits for more user input. It sends an email notification to the user(s), mentioning to provide more values from Portal in order to continue the execution.

Functionality

If this activity is included in a workflow, when it is executed, it will send an email to all the users set in the Assigned User(s) parameter. Users must be members of a Security Group in Flowster Studio. If assigned users are members from a Users type group, the group should have permissions to access the Portal.

After the workflow is started, when the execution reaches this activity, the status of the execution is updated from Running to Waiting for user input. 

When resuming the workflow, a list of selected parameters will be displayed with the initial values  for the user to input (or not) different values. If more than one activity is used in the same workflow with the same selected parameters, on the next resume action, the values of the parameters will be the previous ones, not the initial ones. 

Activity Parameters

Parameters:

  • Assigned User(s) (text box editor type) (type: string): Specify the assigned users to input new values, by domain and samaccount separated by semicolon ';'. E.g. 'DemoDomain\Demouser1;google\demo@gmail.com;customuser1'. For Azure users use the format: 'azure\demoUserEmail@azure.com', for Google Auth users: 'google\demoUserEmail@google.com' and for custom users: 'customuser' (the identifier from Security Groups in Administrator).
  • Days (text box editor type) (type: Integer): the number of days to wait for user action. If set to 1, it means that if 1 day passes and no input was given, the workflow will be marked as expired.
  • Deactivate Default Mails (combo box editor type) (type: string): specify whether to deactivate the default approval mails. If set to 'True' no approval mails will be sent, including the mails set in 'Notify by email' category.
  • Notification Mail (text box editor type) (type: string): specify a customized email notification text in HTML format.
  • Notification Text (text box editor type) (type: string): specify a customized notification text in HTML format. This value will be displayed in the Resume window in Portal. 
  • Parameter Group (combo box editor type) (type: string): the parameter group containing the parameters that need new input values. These parameter groups are defined in Administrator, in the Edit Parameters window.
  • Selected Parameters (combo box editor type) (type: string): select which parameters to be shown when click on Resume button in Portal. If Visible column is unchecked for a selected parameter, it will be hidden when Resume Workflow window opens. If any parameters are selected, the "Parameter Group" parameter is ignored.


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

  • Output Expired (type: Boolean): outputs the expired status.
  • Output Parameters  (type: List<KeyValuePair<String,Object>>): outputs a list of KeyValuePairs, containing the changed parameters' names and values.

The values from the output parameter can be extracted, for example, by using a Custom ForEach activity or by using GetKeyValuePair activity, to extract a specific parameter:

For example, GetKeyValuePair activity is used to extract the new value for ADGroups (String[]) parameter from Output_NewParameterValues output returned by WaitForMoreInput activity:

  

The value extracted from key ADGroups is of type Object, but the value stored is of type String[], therefore a cast is needed to cast the int_NewADGroups parameter from Object to String[], using Microsoft activity, Cast:


If the parameter type is generic (Int32, String), Cast activity is not needed, just an implicit cast of the object type to desired type. For example, CInt(Port) or Username.ToString().

Write Data To Storage

This activity writes the given input data into a text file located in the network path set for the active tenant.

Activity Parameters



Parameters:

  • Content Formatted (text box editor type): specifies the content to be written in the file. External variables/arguments values can also be written, by using the $using:variableName syntax.
  • Input String (text box editor type) (type: string): the content to be written in the file, in a simple string format. In order to split the string in multiple lines, insert a vbCrlf syntax between the desired strings (e.g. "string1" + vbCrlf + "string2" or by using variables/arguments: Variable1 + vbCrlf + Variable2 + vbCrlf + Argument1).

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

  • Execution Result String  (type: boolean): outputs the result of the execution (True if the execution was successful or False if not).
  • Execution String  (type: string): outputs the string that will be appended to the created file.


This parameter requires a Central Storage Path to be defined in Administrator for the tenant where it will be used (see how to configure the tenant's storage path:  /wiki/spaces/FS/pages/16060940329).

This activity can be used multiple times in a workflow, each time appending the new content to the execution file. It can insert predefined strings and/or variables/arguments values.

When this activity is used in a workflow, in the Flowster Studio Portal - History page there will be given the possibility to download the created file by selecting the Info option for an execution and clicking the Download link:



This is an example of a file which can be created by using this activity:


Related content