SiteTreeServices Class Ingeniux CMS Web Services API

Provides the functionality to work with Ingeniux CMS site tree.
Inheritance Hierarchy

SystemObject
  CMSServicesBase
    CMSContentServiceBase
      IngeniuxCMServiceSiteTreeServices

Namespace: IngeniuxCMService
Assembly: IngeniuxCMService (in IngeniuxCMService.dll) Version: 9.0.565.0 (9.0.565)
Syntax

[ServiceBehaviorAttribute(IncludeExceptionDetailInFaults = true)]
[AspNetCompatibilityRequirementsAttribute(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)]
public class SiteTreeServices : CMSContentServiceBase

The SiteTreeServices type exposes the following members.

Constructors

  NameDescription
Public methodSiteTreeServices
Top
Methods

  NameDescription
Public methodCanMovePage
Determines if a collection of Pages can be moved to another location by current User.
Public methodCreateNewPage
Creates a new Page or Components, from either Page Creation Rule or Schema specified.
Public methodEmptyRecycleFolder
Permenantly deletes all Pages placed under the Recycle Folder.
Public methodGetChildPages
Retrieves collection of the information of Children of a given Page. Returns up to 50 entries, starting from given index.
Public methodGetPageProperties
Retrieves Properties of a single Page node, which includes collection of meta data of the Page.
Public methodMoveCopyPage
Moves or Copies a Page node from one location to another location. All the descendants of the Page node gets moved/copied together.
Public methodMoveCopyPageAdvanced
Moves or Copies a Page node from one location to another location. All the descendants of the Page node gets moved/copied together. This operation divides instructions of Move/Copy into separate parameters.
Public methodNewPageWorkflowCheck
Determines whether a Page created via Page Creation Rule or Schema needs to be added to Workflow. If yes, doesn't have a User to assign to, or a the User to assign the Page to must be selected.
Public methodRecurseToPage
Retrieves the entire ancestors collection to the given Page, starting from the Content Store. Each ancestor entry contains its children entries.
Top
See Also

Reference