 | SessionFindWhereUsedCustom Method |
Searches for usage of the target object in other objects and rules. Unlike
,
this method only makes indirect calls to the management server. It then follows only the
object types defined in indirectTypes. This addresses the problem
where the normal where-used can follow objects you may not wish to follow.
Namespace: Koopman.CheckPoint
Assembly: CheckPoint.NET (in CheckPoint.NET.dll) Version: 0.5.1
SyntaxC#
public Task<WhereUsed> FindWhereUsedCustom( string identifier, DetailLevels detailLevel = DetailLevels.Standard, bool indirect = false, int indirectMaxDepth = 5, ObjectType[] indirectTypes = null, CancellationToken cancellationToken = null )
Parameters
- identifier
- Type: SystemString
The object identifier to search for. - detailLevel (Optional)
- Type: Koopman.CheckPointDetailLevels
The detail level. - indirect (Optional)
- Type: SystemBoolean
if set to true results will include indirect uses. - indirectMaxDepth (Optional)
- Type: SystemInt32
The indirect maximum depth. - indirectTypes (Optional)
- Type: Koopman.CheckPointObjectType
Object types that should be followed. A value of null will default to only following groups. - cancellationToken (Optional)
- Type: System.ThreadingCancellationToken
The cancellation token.
Return Value
Type: TaskWhereUsedA task that represents the asynchronous operation. The task result contains the WhereUsed object
Remarks
Due to the way this method manually follows indirect usages it will take longer on
average than the normal where-used method. Also if/when Check Point implement this
feature in the API natively this method will be depricated, in favor the standard API. If
indirect is false then this is identical to calling .
See Also