Versions Compared

Version Old Version 96 New Version Current
Changes made by

wiki (Unlicensed)

wiki (Unlicensed)

Saved on

Key

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


Activities



Connect to Active Directory

...

  • ClearAttribute (text box editor type) (type: string): the attribute that will be cleared/removed.
  • Entry (text box editor type) (type: string): the entry path of the Active Directory entry, or bind this parameter with the output parameter of a Get Entry activity. If the Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://servername.dc1.com/CN=DemoUser,OU=DemoOU,DC=dc1,DC=com"



Using Get Entry activities: get Entry activities can be used in order to extract the needed entry paths from Active Directory. The steps below are describing a scenario of how to use both Get Entry and ClearADAttributeValue activity:

...

  • Attributes (text box editor type) (type: string): enter computer specific Attributes for the new created computer. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD).
  • CN String (text box editor type) (type: string): the CN String value that will be associated with the Canonical Name of the object. For Example: 'CN=DemoComputer1' will create a computer with the Canonical Name: dc1.com/__DEV-Testing/Computers/DemoComputer1.
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field.
  • Parent Entry (text box editor type) (type: string): the parent entry for the new created computer. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com"
  • sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new computer.

...

  • Attributes (text box editor type) (type: string): enter group specific Attributes for the new created group. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD). For example, it can be inserted the displayName attribute. In the Collection editor window, when adding a new member, at Name insert the attribute's name (e.g. displayName) and at Value insert the value that the attribute should take.
  • CN String (text box editor type) (type: string): the CN String value of the place where the group will be created. For Example: 'CN=TEST'. This value will be associated with the CN attribute.
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field. The example presented in the screenshot can be translated as "displayName,TestingGroup".
  • Group Type (combo box control) (type: string): choose the type of the group you want to create. Flowster Studio provides the following options:
    • Local Security Group
    • Global Security Group
    • Builtin Group
    • Universal Security Group
    • Global Distribution Group
    • Local Distribution group
    • Universal Distribution group
  • Parent Entry (text box editor type) (type: string): the parent entry for the new created group. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".
  • sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new group.

...

  • Attributes (text box editor type) (type: string): enter user specific Attributes for the new created user. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD). For example, it can be inserted the displayName attribute. In the Collection editor window, when adding a new member, at Name insert the attribute's name (e.g. displayName) and at Value insert the value that the attribute should take:
  • CN String (text box editor type) (type: string): the CN String value of the place where the user will be created. For Example: 'CN=TEST'. This value will be associated with the CN attribute.
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field. The example presented in the screenshot can be translated as "displayName,TestingUser;mail,TstUser@flowster.de;company,Flowster Solutions".
  • Parent Entry (text box editor type) (type: string): the parent entry for the new created user. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
  • Password (text box editor type) (type: string): the password for the User.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the User. (This parameter is used only when the user wants to send an encripted password from outside the workflow, for example Flowster Portal)
  • sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new user.

...

 

Execution: the activity will output the result of the group creation, displaying the newly created user's Path.




Create User With Password String

This activity creates a new entry of class 'User' in Active Directory.

Activity Parameters

The Create User With Password String activity parameters can be provided by manual inserted values or via IN arguments or variables:



Parameters:

  • Attributes (text box editor type) (type: string): enter user specific Attributes for the new created user. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD). For example, it can be inserted the displayName attribute. In the Collection editor window, when adding a new member, at Name insert the attribute's name (e.g. displayName) and at Value insert the value that the attribute should take:
  • CN String (text box editor type) (type: string): the CN String value of the place where the user will be created. For Example: 'CN=TEST'. This value will be associated with the CN attribute.
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field. The example presented in the screenshot can be translated as "displayName,TestingUser;mail,TstUser@flowster.de;company,Flowster Solutions".
  • Parent Entry (text box editor type) (type: string): the parent entry for the new created user. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"
  • Password String (text box editor type) (type: string): the string value for the password. When editing this parameter, the value of the password will appear as plain text.
  • sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new user.

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

  • Entry Path (type: string): outputs the path of the new created user.
 

Execution: the activity will output the result of the group creation, displaying the newly created group's Path.



...

  • Entry (combo box control) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser_1,OU=Users,DC=dc1,DC=com"

...

...

  • Action (combo box control) (type: string): choose to Enable/Disable the specified computer account.
  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for a computer account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoComputer1,OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Attribute (text box editor type) (type: string): the attribute for which the value(s) will be edited. Here should be inserted the name exactly as seen in Active Directory (e.g. displayName)
  • Attributes (text box editor type) (type: string): the attributes as a collection for the AD entry that you want to edit. This parameter can be used in case of multiple attributes that will be edited. Attributes will be added as a list, with their Names and new Values
  • CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "AttributeName1,Attribute1Value;Attribute2Name,Attribute2Value". This parameter can be used instead of the Attributes one if there is desired to write all attributes and their values as a single string
  • Date Format (text box editor type) (type: string): if 'Value Type' is 'DateTime', enter the date format string. For example: dd.MM.yyyy; if no value is entered, the system defaults are used.
  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
  • Value Type (combo box control) (type: string): choose Data type for the edited value. In our example String will be needed
  • Value(s) (text box editor type) (type: IEnumerable<string>): enter new value(s) for the attribute (the one provided in the Attribute field), separated by ','. Being of type IEnumerable<of string>, the value(s) should be written between {}
    • Examples of values:
      • simple string: {"Demo Test"}
      • multiple values: {"Demo Test","Demo Name","Demo Value"}
      • simple string with comma in it: {"Demo, Test"}
      • multiple values with comma inside of the string: {"Demo, Test","Demo, Name"","Demo, Value"}

...

The Edit User Account Status activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

  • Action (combo box control) (type: string): choose to Enable/Disable or Lock/Unlock the specified user account.
  • Attempts (text box editor type) (type: string): the number of allowed bad password attempts.
  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Output Status (type: boolean): outputs the result status. If the operation succeeded then TRUE, otherwise FALSE.
  • Output Statusmessage (type: string): outputs the status message from the trackingdata about the change.

Execution: the activity will check the provided entry and if found, will perform the selected operation on it (enable, disable, lick, unlock):

...

  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Entry (text box editor type) (type: string):  the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"
  • Selected Attribute (text box editor type) (type: string): specify an attribute for which you want a separate output. This parameter is used when it is desired for the activity to return only the value(s) for a single attribute (e.g. sAMAccountName)

...

  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry (for GetEntry binding usage, see the Add Computer To Group activity) activity or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"

...

  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=Demouser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Attributes (text box editor type) (type: string): the attributes to retrieve for found users, in addition to the 'Path' attribute, which is retrieved by default. The attributes must be separated by ','. For example: name,distinguishedName,sAMAccount.
  • Group Name (text box editor type) (type: string): the group name. This value can be used when no path is given for the group
  • Group Path (text box editor type) (type: string): the entry for the group. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the 13669534395Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".


...

  • Entry Path (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
  • Group Path (text box editor type) (type: string): the entry for the group. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoGroup1,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Entry (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the 13669534395Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=Demouser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
  • Entry New Location (text box editor type) (type: string): the entry for the new location (in this example a group is given). The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/OU=DemoUsers,DC=dc1,DC=com".

...

  • Computer (text box editor type) (type: string): the entry for the computer. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoComputer1,OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com".
  • Group (text box editor type) (type: string): the entry for the group where the computer is a member of. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Group (text box editor type) (type: string): the entry path of the group where the other group is a member of, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".
  • Group To Be Removed (text box editor type) (type: string): the entry path of the group that will be removed from the group, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroup1,OU=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".

...

  • Group (text box editor type) (type: string): the entry path of the group where the user is a member of, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".
  • User (text box editor type) (type: string): the entry path of the user that will be removed from the group, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...