Despite its name, the enable-aps-filter operation is not diametrically opposed to disable-aps-filter. The operation enable-aps-filter just clears the list of apps offered in a service plan. Thus you are able to manage the apps list (by add-package and remove-package) without calling this operation beforehand.
A request XML packet clearing the list of apps available in a service plan includes the enable-aps-filter operation node:
<packet>
<service-plan>
<enable-aps-filter>
...
</enable-aps-filter>
</service-plan>
</packet>
The enable-aps-filter node is presented by type ServicePlanApsFilterInputType (domain_template.xsd
). Its graphical representation is as follows:
(domain_template.xsd
). See the Available Filters section for details on this node.
Important: When creating request packets, put nodes and elements in the order they follow in the packet structure.
The enable-aps-filter node of the output XML packet is of complex type (domain_template.xsd
) which has the following presentation:
common.xsd
). common.xsd
).This packet clears the list of apps available in the service plan base_plan.
<packet>
<service-plan>
<enable-aps-filter>
<filter>
<name>base_plan</name>
</filter>
</enable-aps-filter>
</service-plan>
</packet>
Response:
<packet>
<service-plan>
<enable-aps-filter>
<result>
<status>ok</status>
<filter-id>base_plan</filter-id>
</result>
</enable-aps-filter>
</service-plan>
</packet>