...
The Remove User from Group activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- GroupDN group DN (text box editor type) (type: string): the group DN in eDirectory.UserDN DN String value for the group where the user will be removed from. For example, "CN=FlowsterGroup,o=FlowsterDemo", where FlowsterGroup is the name for the group and FlowsterDemo is the parent container of the group).
- user DN (text box editor type) (type: string): the user DN of the DN String value for the user that which will be removed from the group in eDirectory.
...
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 Remove User from Group activity:
...
- For example, "CN=FlowsterUser,o=FlowsterDemo", where FlowsterUser is the name of the user and FlowsterDemo is the parent container of the user).
The Read Only Output variable are the possible output values that the activity will provide:
- Output (type: boolean): outputs the status of the operation: True is successful, otherwise False.
As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.
Execution: the activity will check for the given DNs (Group and User DN) and if both found, it will remove the user from the group:
List Entries
This activity returns all the entries in the specified container. No attributes are returned.
Activity Parameters
The List Entries activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- Search Base (text box editor type) (type: string): the container DN where the search is done. For example, "o=FlowsterDemo", meaning that the activity will search in this specific container after its entries.
- Search Filter (text box editor type) (type: string): the search filter. If left empty, the activity will return all objects from the given container (Search Base). There can be also used the following filters:
- ObjectClass=User: will return only the entries of type User
- ObjectClass=Group: will return only entries of type Group
- ObjectClass=Computer: will return only entries of type Computer
- combinations of the above mentioned filters
The Read Only Output variable are the possible output values that the activity will provide:
- DN List (type: List<string>): outputs a list of strings containing the found DN for each object that matches the filter.
As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.
Execution: the activity will search for entries in the given container, depending on the provided filter (if the filter is empty, all entries will be listed):
Search Attributes
This activity searches for attribute values based on the search filter of the first matching DN.
Activity Parameters
The Search Attributes activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- Search Base (text box editor type) (type: string): the container DN where the search is done. For example, "o=FlowsterDemo", meaning that the activity will search in this specific container after its entries.
- Search Filter (text box editor type) (type: string): the search filter:
- If left empty: the activity will return the container's attributes. It will also be left empty is a CN is provided at the Search Base field
- ObjectClass=User: will return only the attributes for the entries of type User
- ObjectClass=Group: will return only the attributes for the entries of type Group
- ObjectClass=Computer: will return only the attributes for the entries of type Computer
- combinations of the above mentioned filters (except empty)
The Read Only Output variable are the possible output values that the activity will provide:
- Attributes List (type: List<KeyValuePair<string,string>>): outputs a list of KeyValuePair string containing the found attribute name and value for the first object that matches the filter.
As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor.
Execution: depending on the given Search Base and Search Filters, the activity will output a list with all found attributes. Below there are some examples of using the activity with different search filters and search bases:
- Search Base is a container, no filter provided:
- activitycontent:
- activity execution:
- activitycontent:
- Search Base is a container, filter for Users provided:
- activity content:
- activity execution:
- activity content:
- Search Base is a container, filter for Groups provided:
- activity content:
- activity execution:
- activity content:
- Search Base is an User, no filter provided
- activity content:
- activity execution:
- activity content:
- Search Base is a Group, no filter provided:
- activity content:
- activity execution:
- activity content:
- Search Base is a Computer, no filter provided:
- activity content:
- activity execution:
- activity content:
Rename Entry
This activity renames the cn attribute for an entry in Novell eDirectory.
Activity Parameters
The Rename Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- New DN (text box editor type) (type: string): the new CN value.
- Old DN (text box editor type) (type: string): the old DN that will be renamed.
- Parent DN (text box editor type) (type: string): the parent DN of the entry.
The Read Only Output variable are the possible output values that the activity will provide:
- Output (type: string) outputs the status of the operation.
As mentioned above, the values for all the required parameters can be provided by IN arguments/variables or inserted through the inline / extended editor. Below is an example of predefined arguments, ready to be used by the Rename Entry activity:
...