Checking on features
Our highly individualizable, modular platform offers unparalleled customization through a robust feature system.
Last updated
Was this helpful?
Our highly individualizable, modular platform offers unparalleled customization through a robust feature system.
Last updated
Was this helpful?
Our platform's extensive feature system allow for easy customization to meet your needs. Checking on the the current state of features through REST or GraphQL endpoints enables quick reactions in your clients. This level of configurability ensures a personalized experience for optimal efficiency.
Upon successful request, you will receive a response similar to the following example:
The name
field denotes the feature name, while the status
field indicates whether the corresponding feature is currently enabled, disabled or inactive. If a feature is inactive it cannot be enabled or disabled. The version
field indicates the current version of the corresponding feature document.
Enter the feature name you want to query in the URL in <FEATURE-NAME>
. Upon successful request, you will receive a response similar to the following:
Specify the feature you want to edit in the URL in <FEATURE-NAME>
, enter the document version in <DOCUMENT-VERSION>
and input the desired status (enabled
, disabled
or inactive
) in <STATUS>
You can also use GraphQL to query for details of features of the system.
Upon successful request, you will receive a response similar to the following example:
Enter the feature name you want to query in the query parameter in <FEATURE-NAME>
. Upon successful request, you will receive a response similar to the following:
All functions and endpoints related to this feature will be available.
All functions and endpoints related to this feature will not be available.
This is a transitional state recommended for disabling a feature. Entities that are already in the processing pipeline of the targeted feature can still be processed, but new entities won't trigger the feature. For example, if an order has been created but a pick job has not been generated yet, setting the picking feature to inactive would allow a pick job to be created for that order. However, any new orders created after setting the feature to inactive would not trigger the creation of pick jobs.
Be aware, that the fulfillmenttools GraphQL API is currently in .