지금 지원 담당자와 채팅
지원 담당자와 채팅

GPOADmin 5.13.5 - User Guide

Introducing Quest GPOADmin Configuring GPOADmin Using GPOADmin
Connecting to the Version Control system Navigating the GPOADmin console Search folders Accessing the GPMC extension Configuring user preferences Working with the live environment Working with controlled objects (version control root) Checking compliance Editing objects Synchronizing GPOs Exporting and importing
Creating Reports Working with the GPOADmin Dashboard Appendix: Windows PowerShell Commands Appendix: GPOADmin Event Log Appendix: GPOADmin Backup and Recovery Procedures Appendix: Customizing your workflow Appendix: GPOADmin Silent Installation Commands About Us

Predefined Tags

Tags are typically replaced with their corresponding values by the service. However, there are cases where the tags will not be converted. For example, if a comment is not specified during the version control action then the [COMMENT] tag will be empty; or if the object is not checked out then the [TRUSTEENAME] and [TRUSTEESID] will be empty.

Keep in mind that in some cases the tags will always be empty as is the case of a pre-action for the Register version control action. At the time the pre-action is processed, the corresponding version control information would not exist.

Parameters and conditions support the following predefined tags:

Table 21. Available tags

[ACTION]

The currently executing version control action.

[VCID]

The version control identifier of the current object.

[DOMAINNAME]

The name of the domain for the current object.

[FULLPATH]

The full path of the current object in the version control system.

[ID]

The native identifier for the current object.

[LASTBACKUPID]

The identifier of the last backup for the current object.

[NAME]

The name of the current object.

[STATUS]

The version control status for the current object.

[SUBSTATUS]

The version control sub status for the current object.

[TRUSTEENAME]

The name of the user the current object is checked out to.

[TRUSTEESID]

The SID of the user the current object is checked out to.

[TYPE]

The version control type of the current object.

[VERSION]

The version of the current object.

[COMMENT]

The comment associated with the version control action.

Conditions

Whether or not an action is processed can be controlled by the use of conditions. A condition must evaluate to true in order for the action to be processed. If the condition evaluates to false then a log entry stating such is created and the current custom workflow action is not processed.

Each condition node has the following properties:

DataType

The data type of the property being compared.

Value1

The left side of the comparison.

Value2

The side of the comparison.

Operator

The operation to perform. Options depend on the DataType.

IgnoreCase

 

This is only valid for the string DataType. This property instructs the service to perform any string operations case insensitively.

The type of operations available depends on the DataType property.

The following DataTypes are available:

Table 23. DataTypes

String

This condition is performed on a string.

Guid

This condition is performed on a Guid.

Version

The condition is performed on a version.

The following operations are available for a String DataType:

Table 24.  

equal

Determines whether or not Value1 and Value2 have the same value.

not equal

Determines whether or not Value1 and Value2 are different.

contains

Determines whether or not Value2 is present in Value1

not contains

Determines whether or not Value2 is missing from Value1.

starts with

Determines whether or not Value1 starts with Value2.

not starts with

Determines whether or not Value1 does not start with Value2.

ends with

Determines whether or not Value1 ends with Value2.

not ends with

Determines whether or not Value1 does not end with Value2.

The following operations are available for a Guid DataType:

Table 25. Guid operators

equal

Determines whether or not Value1 and Value2 have the same value.

not equal

Determines whether or not Value1 and Value2 are different.

The following operations are available for a Version DataType:

equal

Determines whether or not Value1 and Value2 have the same value.

not equal

Determines whether or not Value1 and Value2 are different.

greater than

Determines whether or not Value1 is greater than Value2.

greater than or equals

Determines whether or not Value1 is greater than or equal to Value2.

less than

Determines whether or not Value1 is lesser than Value2.

less than or equals

Determines whether or not Value1 is lesser than or equal to Value2.

The available logical operators include:

Table 27. Operators

And

Logically ANDs to conditions.

Or

Logically ORs to conditions.

The logical operators ‘And’ and ‘Or’ function sequentially and grouping is not supported. For example:

would be processed as:

not as:

To use a logical “And” or “Or” operator, specify a new Condition with only the Operator property.

For example:

Example of a complete pre-action

The following example demonstrates a pre-action that creates a CheckIn directory below the GPOSettingsReports directory provided that the name of the version controlled object contains an underscore and the version is less than 4.5 or the comment ends with “_AMER”.

Troubleshooting custom workflow actions

Because custom workflow actions are performed in the background by the GPOADmin service, they will not be visible from the interface. However, you can use the logs to assess any issues. When a custom workflow action is processed, the Standard Output and Error streams are redirected and logged as part of the server actions provided the Debug logging option is enabled.

 

2013

GPOADmin server process – Information

2014

GPOADmin server process – Errors

2015

Custom Workflow Action process – Standard Output stream

2016

Custom Workflow Actions process – Error stream

 

관련 문서