Get all rule expressions

get

/fscmRestApi/resources/11.13.18.05/businessRuleDefinitions/{businessRuleDefinitionsUniqID}/child/ruleVersions/{RuleVersionId}/child/ruleExpressions

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • This is the hash key of the attributes which make up the composite key for the Business Rule Definitions resource and used to uniquely identify an instance of Business Rule Definitions. The client should not generate the hash key value. Instead, the client should query on the Business Rule Definitions collection resource in order to navigate to a specific instance of Business Rule Definitions 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 all the rule expressions that match the primary key criteria specified.
      Finder Variables
      • RuleDetailId; integer; Unique identifier for the rule expression.
  • 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:
    • Description; string; The description of the group of rule statements.
    • ExpressionCode; string; The unique code of the expression.
    • ExpressionInputCode; string; The code for the received expression value. For example, an element code or attribute code.
    • ExpressionInputId; integer; The unique identifier of the received expression value.
    • ExpressionInputName; string; The name of the received expression value.
    • ExpressionInputSourceCode; string; The type of the received expression value. For example, VAR, ELEM or ATTR. This is used internally to identify the source of the received expression code.
    • ExpressionName; string; The name of the expression. Expression can be, for example, a value for variable, element, or attribute.
    • ExpressionOrder; integer; The order of the expressions within hierarchy.
    • ExpressionOutputCode; string; The code for the provided expression value. For example, an element code or attribute code.
    • ExpressionOutputId; integer; The unique identifier of the provided expression value.
    • ExpressionOutputName; string; The name of the provided expression value.
    • ExpressionOutputSourceCode; string; The type of the provided expression value. For example, VAR, ELEM or ATTR. This is used internally to identify the source of the expression output code.
    • HiddenFlag; boolean; Indicates whether the rule detail line is hidden on UI or not. The default value is N.
    • InternalDefinedCode; string; The internally generated code for the variable.
    • LockedFlag; boolean; Indicates whether the rule detail line is locked for editing or not. The default value is N.
    • ParameterBooleanFlag; boolean; The value of a boolean parameter, for example, true or false.
    • ParameterDate; string; The value of a date parameter, for example, the value can be a date when an admissions application was submitted.
    • ParameterDatetime; string; The value of a date and time parameter, for example, the date and time at which a course started.
    • ParameterNumber; number; The value of a number parameter, for example, the value can be a course fee.
    • ParameterString; string; The value of a text parameter, for example, the value can be a student name.
    • ParameterTypeCode; string; The data type of the parameter value, for example, String, Date, Boolean or Number. This is used internally to populate the corresponding parameter field.
    • ParentSequenceIdentifier; integer; The internal identifier of the parent detail row.
    • RuleDetailId; integer; The unique identifier of a rule version detail.
    • SequenceIdentifier; integer; The numeric identifier generated for each detail row of the rule used to link rows.
    • StatementGroupName; string; The name of the group of rule statements.
    • TemplateSequenceIdentifier; integer; The numeric identifier of the row in the template from which the rule was created.
  • 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 : businessRuleDefinitions-ruleVersions-ruleExpressions
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : businessRuleDefinitions-ruleVersions-ruleExpressions-item-response
Type: object
Show Source
Back to Top