Uses of Interface
com.redwood.scheduler.api.model.ProcessServerCheck

Packages that use ProcessServerCheck

Package	Description
com.redwood.scheduler.api.model	Scheduler API - Model
com.redwood.scheduler.api.model.compatibility_14

Uses of ProcessServerCheck in com.redwood.scheduler.api.model

Fields in com.redwood.scheduler.api.model with type parameters of type ProcessServerCheck

Modifier and Type	Field	Description
static QueryObjectType<ProcessServerCheck>	ProcessServerCheck.TYPE	Type that can be used in SchedulerSession.executeObjectQuery(QueryObjectType, String, Object...).

Methods in com.redwood.scheduler.api.model that return ProcessServerCheck

Modifier and Type	Method	Description
ProcessServerCheck	ProcessServer.createProcessServerCheck()	Create a new ProcessServerCheck linked to this object.
ProcessServerCheck	ProcessServerCheckLog.getProcessServerCheck()	Get the ProcessServerCheck.
ProcessServerCheck	SchedulerSession.getProcessServerCheckByUniqueId(Long uniqueId)	Get the ProcessServerCheck by UniqueId.

Methods in com.redwood.scheduler.api.model that return types with arguments of type ProcessServerCheck

Modifier and Type	Method	Description
RWIterable<ProcessServerCheck>	ProcessServer.getProcessServerChecks()	Get an RWIterable over an ordered collection of ProcessServerChecks.

Methods in com.redwood.scheduler.api.model with parameters of type ProcessServerCheck

Modifier and Type	Method	Description
void	AbstractConcreteObjectCallback.handle(ProcessServerCheck theProcessServerCheck)
void	ConcreteObjectCallback.handle(ProcessServerCheck theProcessServerCheck)

Uses of ProcessServerCheck in com.redwood.scheduler.api.model.compatibility_14

Methods in com.redwood.scheduler.api.model.compatibility_14 that return types with arguments of type ProcessServerCheck

Modifier and Type	Method	Description
Iterator<ProcessServerCheck>	ProcessServerComp.getProcessServerChecks()	Deprecated. this method should never be used directly, and is only provided to ensure binary compatibility with previous releases of the software, use ProcessServer.getProcessServerChecks() instead.