Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v73
  • v74
  • v73
  • v72
Login
  • Getting Started
  • Administrator documentation
  • Functional characteristics
  • Technology description
  • System requirements
  • Admin Panel
  • Platform installation
  • Platform configuration
  • Platform maintenance
  • Custom channels guide
    • Overview
    • Creating and configuring a channel
    • Entity field configuration
    • Template language
    • Entities
    • Pipes
      • Pipe: Basic Concepts
      • Result
      • Errors
      • Log
      • Pack
      • Unpack
      • HTTP Request
      • Store Set
      • Store Get
      • Selector
      • SQL
      • Eventer
      • Scheduler
    • Pipelines
  • Extra
  • Processing HTTP/HTTPS traffic
  • Administrator API
This is documentation for Altcraft Platform v73. This documentation is no longer maintained.
The information for up-to-date platform version at this page is available (v74).
  • Custom channels guide
  • Pipes
  • Result
Documentation for version v73

Result

caution

Can only be used in Entities pipelines (see Entities).

Description​

The Result pipe sets the result of synchronous pipelines to Entities (see Entities). If params.path is not specified, the result will be taken from $in.data.

Peculiarities:

  • An empty result is not an error;
  • The Result pipe does not have to be the last one in the chain. After recording the result, the pipeline can perform some other logic, for example, closing the session.
  • A pipeline can have several Result pipes, but not a single such pipe should have parent pipes with Result types in the chain. (The result should be recorded only once.)
  • Must return an object or an array of objects

Structure​

FieldType ValueExampleRequiredDescription
idnumber10yesPipe's ID
typestring"result"yesPipe's type
paramsResultParamsObject
noType-specific parameters
outsOutsObject
noPipe"s outputs

ResultParamsObject
FieldTypeExampleRequiredDescription
path

string

"$#in.data.categories"noPath to the field which will be used to show a result

Errors​

  1. Error processing params.path – params.path was specified, but the format is incorrect or the field was not found.
  2. Error processing $in.data - params.path is not set and there is no data key in the $in object.

Examples​

  1. Correct example. $#in.data.categories is supposed to contain an array of objects:
{
"id": 10,
"type": "result",
"params": {
"path": "$#in.data.categories"
}
}
  1. An example of an error. $#in.data.categories is supposed to contain an array of objects:
{
"id": 10,
"type": "result",
"params": {
"path": "$in.data.categories"
}
}

The result here is returned as a string, which is incorrect in this case.

Last updated on Mar 31, 2025
Previous
Pipe: Basic Concepts
Next
Errors
  • Description
  • Structure
  • Errors
  • Examples
© 2015 - 2025 Altcraft, LLC. All rights reserved.