Get all contract terms templates

get

/fscmRestApi/resources/11.13.18.05/contracts/{contractsUniqID}/child/ContractTerms

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Contracts resource and used to uniquely identify an instance of Contracts. The client should not generate the hash key value. Instead, the client should query on the Contracts collection resource in order to navigate to a specific instance of Contracts to get the hash key.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey :Finds a contract terms template.
      Finder Variables:
    • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
    • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

      Example:
      self,canonical
    • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
    • The resource item payload will be filtered in order to contain only data (no links section, for example).
    • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
    • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

      Format: ?q=expression1;expression2

      You can use these queryable attributes to filter this collection resource using the q query parameter:
      • ArticleEffectiveDate; string; The effective date of a clause in a template.
      • AsyncUpload; boolean; Indicates whether upload can be done in the background.
      • AttachedDocFile; string; The attached document file of the template.
      • AttachedDocFileDesc; string; The attached document file description of the template.
      • AttachedDocFileTitle; string; The attached document file title of the template.
      • AttachedDocumentFileName; string; The attached document file name of the template.
      • AuthoringPartyCode; string; The authoring party code of the template.
      • AuthoringPartyMeaning; string; The authoring party meaning of the template.
      • AutogenDeviationsFlag; string; Indicates whether deviations should be generated automatically.
      • ContractExpertEnabled; string; Indicates whether the contract expert is enabled for the contract template.
      • ContractSourceCode; string; The contract source code of the template.
      • ContractSourceMeaning; string; The contract source meaning of the template.
      • ContractTypeId; integer; The contract type ID associated with the template.
      • CreatedBy; string; The user who created the template.
      • CreationDate; string; The date when the template was created.
      • Description; string; The description of the template.
      • DocNumberingScheme; number; The document numbering scheme of the template.
      • DocumentNumber; string; The document number of the template.
      • ExpertLastRun; string; The date and time of when the expert was run the last for the template.
      • InstructionText; string; The instruction text of the template.
      • LastUpdateDate; string; The last update date of the template.
      • LastUpdateLogin; string; The last update login of the template.
      • LastUpdatedBy; string; The user who last updated the template.
      • LockTermsFlag; string; Indicates whether the terms are locked for update for the template.
      • LockedByUserId; integer; The locked by user ID of the template.
      • LockedByUserName; string; The locked by user name of the template.
      • NewESTR; boolean; The new ESTR of the template.
      • PendingVariables; number; The pending variables of the template.
      • ReferenceTemplateId; number; The reference template ID.
      • ReferenceTemplateName; string; The reference template name.
      • ShowCcBoxInWordYn; string; The indicator of whether CC box is shown in word for the template.
      • SimpleContractYn; string; Indicates whether it's a simple contract or not.
      • SkipPrintAmendmentsYn; string; Indicates whether amendment printing should be skipped or not.
      • SourceCode; string; The source code of the template.
      • TemplateId; number; The ID of the template.
      • TemplateName; string; The name of the template.
      • TermsContentRefreshDate; string; The content refresh date of the template.
      • TermsDownloadSource; string; The source of terms download.
      • USTA; boolean; The USTA of the template.
    • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
    Header Parameters
    • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
    • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

    There's no request body for this operation.

    Back to Top

    Response

    Supported Media Types

    Default Response

    The following table describes the default response for this task.
    Headers
    • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
    • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
    Body ()
    Root Schema : contracts-ContractTerms
    Type: object
    Show Source
    Nested Schema : Items
    Type: array
    Title: Items
    The items in the collection.
    Show Source
    Nested Schema : contracts-ContractTerms-item-response
    Type: object
    Show Source
    Nested Schema : Contract System Variable Values
    Type: array
    Title: Contract System Variable Values
    The system variable values resource is used to get the system variable values of a contract.
    Show Source
    Nested Schema : Contract User Variable Values
    Type: array
    Title: Contract User Variable Values
    The user variable values resource is used to get the user variable values of a contract.
    Show Source
    Nested Schema : contracts-ContractTerms-SystemVariableValues-item-response
    Type: object
    Show Source
    Nested Schema : contracts-ContractTerms-UserVariableValues-item-response
    Type: object
    Show Source
    Nested Schema : Contract User Variable Clause Usages
    Type: array
    Title: Contract User Variable Clause Usages
    The user variable clause usages resource is used to get all the clauses that have this user variable.
    Show Source
    Nested Schema : contracts-ContractTerms-UserVariableValues-ClauseUsages-item-response
    Type: object
    Show Source
    Back to Top