Obsolete Pages{{Obsolete}}
The official documentation is at: http://docs.alfresco.com
Web Scripts
3.0
Draft. This is a work in progress
Note: Mandatory fields are displayed in bold
Details of a rule which include:
Details of a rule type which include:
Details of an action which include:
TODO At the moment a URL to a action or condition resource is associated with a ruleNodeId and owning node, so some more thought is needed for the URL arrays below to make the URLs dependant on only an actionID or conditionID respectively.
Details of a condition which include:
Details of an action definition which include:
Details of an condition definition which include:
Details of a parameter definition which include:
Details of an item on the action queue resource which include:
Details of the status of an action queue item which include:
Methods:
GET /api/rules/types
The rule collection may be filtered by providing values for the following optional parameters:
TODO - 'has rules on node' - this can possibly be implemented by GET, by adding a 'getMetadata' URL parameter to the URL templates below. In this case, if the 'getMetadata' parameter is provided, then metadata about the rule collection would be returned (instead of the actual collection) containing a property how many ruledetails items are in the collection.
Methods:
GET /api/node/{storeType}/{storeId}/{nodeId}/rules?includeInherited={includeInherited?}&ruleTypeName={ruleTypeName?}
GET /api/path/{storeType}/{storeId}/{nodeId}/rules?includeInherited={includeInherited?}&ruleTypeName={ruleTypeName?}
GET /api/rules/appliedtonode/{storeType}/{storeId}/{nodeId}?includeInherited={includeInherited?}&ruleTypeName={ruleTypeName?}
POST /api/node/{storeType}/{storeId}/{nodeId}/rules
=> RuleDetails
POST /api/path/{storeType}/{storeId}/{nodeId}/rules
=> RuleDetails
POST /api/rules/appliedtonode/{storeType}/{storeId}/{nodeId}
=> RuleDetails
TODO - decide the best way forward (for PUT below) to easily address enabling or disabling all rules for a given actionable node. This will most likely focus on the node as the base resource - this needs further discussion
NOTE: - PUT and DELETE here are less important to implement than their counterparts for a single Rule resource
PUT /api/node/{storeType}/{storeId}/{nodeId}/rules
=> RuleDetails[]
PUT /api/path/{storeType}/{storeId}/{nodeId}/rules
=> RuleDetails[]
PUT /api/rules/appliedtonode/{storeType}/{storeId}/{nodeId}
=> RuleDetails[]
DELETE /api/node/{storeType}/{storeId}/{nodeId}/rules
DELETE /api/path/{storeType}/{storeId}/{nodeId}/rules
DELETE /api/rules/appliedtonode/{storeType}/{storeId}/{nodeId}
Methods:
GET /api/rules/{store_type}/{store_id}/{rule_id}
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}
The PUT operation is used to update a rule. To disable or enable an individual rule, send the Rule Details including just the 'ruleNodeRef' and the 'ruleDisabled' field set to the appropriate value of either 'true' or 'false'.
PUT /api/rules/{store_type}/{store_id}/{rule_id}
=> RuleDetails
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}
=> RuleDetails
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}
=> RuleDetails
DELETE /api/rules/{store_type}/{store_id}/{rule_id}
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}
A condition collection resource is a list of conditions associated with an action.
Methods:
POST /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions
=> ConditionDetails
POST /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
=> ConditionDetails
POST /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
=> ConditionDetails
POST /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails
POST /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails
POST /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions
=> ConditionDetails[]
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
=> ConditionDetails[]
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
=> ConditionDetails[]
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails[]
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails[]
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
=> ConditionDetails[]
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions
A condition resource is one of the conditions (identified by 'conditionId') in the condition collection associated with an action
Methods:
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions/{conditionId}
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions/{conditionId}
=> ConditionDetails
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
=> ConditionDetails
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
=> ConditionDetails
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
=> ConditionDetails
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
=> ConditionDetails
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
=> ConditionDetails
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/conditions/{conditionId}
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/conditions/{conditionId}
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/conditions/{conditionId}
The action collection resource consists of a given composite action's child actions, where that composite action is in turn associated with a rule (either directly or indirectly through other ancestor composite actions).
Methods:
POST /api/rules/{store_type}/{store_id}/{rule_id}/action/actions
=> ActionDetails
POST /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
=> ActionDetails
POST /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
=> ActionDetails
POST /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/actions
=> ActionDetails
POST /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
=> ActionDetails
POST /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
=> ActionDetails
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/actions
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/actions
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/actions
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}/actions
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}/actions
An action resource is an action which has previously been applied to a rule, with that action either being the 'root action' directly associated with that rule, or it being a child action of a parent composite action associated with that rule.
Methods:
GET /api/rules/{store_type}/{store_id}/{rule_id}/action
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action
GET /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}
GET /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
GET /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action
=> ActionDetails
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action
=> ActionDetails
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action
=> ActionDetails
PUT /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}
=> ActionDetails
PUT /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
=> ActionDetails
PUT /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
=> ActionDetails
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action
DELETE /api/rules/{store_type}/{store_id}/{rule_id}/action/actions/{action_id}
DELETE /api/node/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
DELETE /api/path/{store_type}/{store_id}/{id}/rules/{rule_id}/action/actions/{action_id}
Methods:
GET /api/rules/conditiondefs
Methods:
GET /api/rules/conditiondefs/{conditionDefinitionName}
Methods:
GET /api/rules/actiondefs
GET /api/node/{store_type}/{store_id}/{id}/actiondefs
GET /api/path/{store_type}/{store_id}/{id}/actiondefs
Methods:
GET /api/rules/actiondefs/{actionDefinitionName}
GET /api/rules/actiondefs/node/{store_type}/{store_id}/{id}/{actionDefinitionName}
GET /api/rules/actiondefs/path/{store_type}/{store_id}/{id}/{actionDefinitionName}
GET /api/rules/conditiondefs/{conditionDefinitionName}/parameterdefs
GET /api/rules/actiondefs/{actionDefinitionName}/parameterdefs
GET /api/rules/parameterdefs
GET /api/rules/parameterdefs/{parameterDefinitionName}
GET /api/rules/conditiondefs/{conditionDefinitionName}/parameterDefs/{parameterDefinitionName}
GET /api/rules/actiondefs/{actionDefinitionName}/parameterDefs/{parameterDefinitionName}
TODO Some more thought is needed for implementing the async execution of actions on the queue and returning a URL in the ActionQueueItemStatusDetails to provide a way to fetch the status of an action at some later stage which has been 'flagged' for async execution.
Also make sure synchronous execution of actions is fully catered for.
Methods:
POST /api/actionqueue
=> ActionQueueItemDetails
Methods:
GET /api/actionqueue/items/{actionQueueItemId}/status
This can be the evaluation status for a single condition, or for many conditions evaluated as a single unit.
Methods:
POST /api/actions/{storeType}/{storeId}/{nodeId}
=> ActionDetails
GET /api/actions/{storeType}/{storeId}/{nodeId}
DELETE /api/actions/{storeType}/{storeId}/{nodeId}
Methods:
GET /api/actions/{actionId}/{storeType}/{storeId}/{actionbleNodeId}
PUT /api/actions/{storeType}/{storeId}/{actionbleNodeId}
=> ActionDetails
DELETE /api/actions/{actionId}/{storeType}/{storeId}/{actionbleNodeId}
Methods:
GET /api/rules/conditionstatus?node={storeType}_{storeId}_{nodeId}
GET /api/rules/conditionstatus/{conditionId}?node={storeType}_{storeId}_{nodeId}
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.